Project

General

Profile

Actions

action #167060

closed

coordination #163919: [epic] Create automation setup for testing Agama

Create agama auto-installation selecting gnome pattern

Added by JERiveraMoya 6 months ago. Updated 5 months ago.

Status:
Resolved
Priority:
High
Assignee:
Target version:
-
Start date:
2024-09-19
Due date:
% Done:

0%

Estimated time:

Description

Motivation

Similar to #166586 but running everything (including the selection of patterns) from the profile in a unattended instalation.

Acceptance criteria

  • AC1: Create profile that install the system (Tumbleweed for now) with gnome.
  • AC2: Enable automation in devel job group.
  • AC3: Add exactly the same validation that we will use in the interactive installation.
Actions #1

Updated by hjluo 6 months ago

  • Status changed from Workable to In Progress
  • Assignee set to hjluo
Actions #2

Updated by JERiveraMoya 6 months ago

@zoecao mentioned that she has already been created the profile (due to some confusion on the goal of here ticket) with gnome include. Please contact her.

Actions #4

Updated by JERiveraMoya 6 months ago

  • Tags changed from qe-yam-sep-sprint to qe-yam-oct-sprint

hjluo wrote in #note-3:

Let's try manually, check the result with the team for our job group which install packages from factory and consider to do the same for Leap to compare.

Actions #5

Updated by hjluo 6 months ago

  • Now confirmed it's a disk space issue and after make it with 20G root it passed https://openqa.opensuse.org/tests/4510877 but still can't boot.
  • Now mannually install with 20GB root and export the profile to confirm.
Actions #6

Updated by JERiveraMoya 6 months ago

hjluo wrote in #note-5:

  • Now confirmed it's a disk space issue and after make it with 20G root it passed https://openqa.opensuse.org/tests/4510877 but still can't boot.
  • Now mannually install with 20GB root and export the profile to confirm.

we use always 40GB, I don't get your point.

Actions #7

Updated by hjluo 6 months ago · Edited

For today's manual(09/26/2024) and profile gnome testing.

  • For manual testing it passed with default disk size and custorm size and can boot into gnome desktop after installation.

  • I've run tests with specific disk size and default disk(40GB disk and 4G RAM) strategy all hang when it nearly finished. like this screen

  • I and Lemon checked the log and found the installation was actually finished for all failed cases. in the log we can see

    agama-logs.JIYUN4/agama.out.log
    51:Sep 26 09:30:20 agama agamactl[2081]: [INFO]: manager: Config phase done
    52:Sep 26 09:30:20 agama agamactl[2081]: [INFO]: manager: Startup phase done
    69:Sep 26 09:30:24 agama agamactl[2081]: [INFO]: manager: Config phase done
    2164:Sep 26 09:44:19 agama agamactl[2081]: [INFO]: manager: Install phase done
    2155:Sep 26 09:43:46 agama agamactl[2709]: [INFO]: software: Installing patterns-gnome-gnome (2069/2069)
    
  • so I think this is maybe caused by openQA can't refresh the agama screen to show the congratulations screen.

Actions #8

Updated by JERiveraMoya 6 months ago

hjluo wrote in #note-7:

For today's manual(09/26/2024) and profile gnome testing.

  • For manual testing it passed with default disk size and custorm size and can boot into gnome desktop after installation.

  • I've run tests with specific disk size and default disk(40GB disk and 4G RAM) strategy all hang when it nearly finished. like this screen

  • I and Lemon checked the log and found the installation was actually finished for all failed cases. in the log we can see

    agama-logs.JIYUN4/agama.out.log
    51:Sep 26 09:30:20 agama agamactl[2081]: [INFO]: manager: Config phase done
    52:Sep 26 09:30:20 agama agamactl[2081]: [INFO]: manager: Startup phase done
    69:Sep 26 09:30:24 agama agamactl[2081]: [INFO]: manager: Config phase done
    2164:Sep 26 09:44:19 agama agamactl[2081]: [INFO]: manager: Install phase done
    2155:Sep 26 09:43:46 agama agamactl[2709]: [INFO]: software: Installing patterns-gnome-gnome (2069/2069)
    
  • so I think this is maybe caused by openQA can't refresh the agama screen to show the congratulations screen.

Let's do two things:

  • Setup the job to run with 40GB and 4GB of RAM in devel job group.
  • Setup the job with similar resources in Leap where you will not find this issues due to it will install less packages.
Actions #9

Updated by hjluo 5 months ago

  1. Setup the job to run with 40GB and 4GB of RAM in devel job group.
  • please help me review the PR_#20240 for this.
Actions #11

Updated by hjluo 5 months ago

  • PR_20350 to move the cursor during installation
Actions #12

Updated by JERiveraMoya 5 months ago

We need to enable the test suite for all the architectures and solve the problems with first boot as follow-up steps in this ticket.

Actions #13

Updated by hjluo 5 months ago · Edited

JERiveraMoya wrote in #note-12:

We need to enable the test suite for all the architectures and solve the problems with first boot as follow-up steps in this ticket.

OK, thanks! now it's works now

Actions #14

Updated by JERiveraMoya 5 months ago

hjluo wrote in #note-13:

JERiveraMoya wrote in #note-12:

We need to enable the test suite for all the architectures and solve the problems with first boot as follow-up steps in this ticket.

OK, thanks! now it's works now

HDDSIZEGB=40 should be enough.

Actions #15

Updated by JERiveraMoya 5 months ago

Merged, please enable this test suite for all the architectures.
Also file a ticket to enable this test suite in the other two job groups we are working on, Leap 16 and SLES 16.

Actions #16

Updated by hjluo 5 months ago

  • Copied to action #168070: Enable agama_auto_gnome in OSD Leap 16 group added
Actions #17

Updated by hjluo 5 months ago

  • Subtask #168070 added
Actions #18

Updated by hjluo 5 months ago

hjluo wrote in #note-18:

JERiveraMoya wrote in #note-15:
Merged, please enable this test suite for all the architectures.

Added.

Also file a ticket to enable this test suite in the other two job groups we are working on, Leap 16 and SLES 16.

Created #168070

Actions #19

Updated by JERiveraMoya 5 months ago

  • Subtask deleted (#168070)
Actions #20

Updated by JERiveraMoya 5 months ago

  • Copied to deleted (action #168070: Enable agama_auto_gnome in OSD Leap 16 group)
Actions #21

Updated by hjluo 5 months ago · Edited

  • Now we are trying to install Tumbleweed on ppc64le and set product id=Tumbleweed but after installation it's shows we've installed MicroOS, and shows we've installed 2009 packages.

  • But If we set product id=MicroOS and it installed 2033 packages

  • Now Ask in #proj-agama for more information.

Actions #22

Updated by hjluo 5 months ago

  • The dev asked for the profile and replied and now wait for their findings.
Actions #23

Updated by JERiveraMoya 5 months ago

hjluo wrote in #note-22:

  • The dev asked for the profile and replied and now wait for their findings.

Please reference the links of the conversation in slack:
https://suse.slack.com/archives/C02TLF25571/p1728631758462519
we are not installing MicroOS, I don't know why you provided a profile for it, it might confuse them (MicroOS with gnome might require more work, it is not in our scope now).

Actions #24

Updated by hjluo 5 months ago

JERiveraMoya wrote in #note-23:

hjluo wrote in #note-22:

  • The dev asked for the profile and replied and now wait for their findings.

Please reference the links of the conversation in slack:
https://suse.slack.com/archives/C02TLF25571/p1728631758462519
we are not installing MicroOS, I don't know why you provided a profile for it, it might confuse them (MicroOS with gnome might require more work, it is not in our scope now).

Changed and thank you.

Actions #25

Updated by hjluo 5 months ago

Actions #26

Updated by JERiveraMoya 5 months ago

  • Status changed from In Progress to Resolved
Actions

Also available in: Atom PDF