Project

General

Profile

Actions

action #155305

closed

Ensure our commonly used openQA installation autoyast profile covers chronyd size:M

Added by okurz 2 months ago. Updated about 2 months ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Feature requests
Target version:
Start date:
2024-02-27
Due date:
% Done:

0%

Estimated time:

Description

Acceptance criteria

  • AC1: The commonly used openQA installation autoyast profile covers chronyd.

Motivation

https://suse.slack.com/archives/C02CANHLANP/p1707375395562249?thread_ts=1707375395.562249&cid=C02CANHLANP
o3 workers clock was running out of sync, chronyd was not running. Possibly never enabled as we use autoyast.

Suggestions


Related issues 1 (1 open0 closed)

Related to openQA Project - action #156169: Automatically validate ay-openqa-worker.xml.erbNew2024-02-27

Actions
Actions #1

Updated by mkittler 2 months ago

  • Subject changed from Ensure our commonly used openQA installation autoyast profile covers chronyd to Ensure our commonly used openQA installation autoyast profile covers chronyd size:M
  • Description updated (diff)
  • Status changed from New to Workable
Actions #2

Updated by okurz 2 months ago

  • Priority changed from Normal to Low
Actions #3

Updated by ybonatakis about 2 months ago

  • Status changed from Workable to In Progress
  • Assignee set to ybonatakis
Actions #4

Updated by ybonatakis about 2 months ago

The easy part is done here https://github.com/os-autoinst/openQA/pull/5488.
Looking for a way to actual test it and verify it

Actions #5

Updated by okurz about 2 months ago

I think the .erb profile is not really used. Please see the short linke mentioned in https://progress.opensuse.org/projects/openqav3/wiki/#Network-legacy-boot-via-PXE-and-OSworker-setup . Also http://open.qa/docs/#_automatic_installation_of_the_operating_systems_for_openqa_machines mentions a file that is not there anymore.

Actions #6

Updated by livdywan about 2 months ago ยท Edited

okurz wrote in #note-5:

I think the .erb profile is not really used. Please see the short linke mentioned in https://progress.opensuse.org/projects/openqav3/wiki/#Network-legacy-boot-via-PXE-and-OSworker-setup . Also http://open.qa/docs/#_automatic_installation_of_the_operating_systems_for_openqa_machines mentions a file that is not there anymore.

What file is not there anymore? Ah. Indeed. ay-openqa-worker.xml no longer exists. I guess we have no link validation.

@ybonatakis Why is there both ay-openqa-worker-leap.xml and ay-openqa-worker.xml.erb mentioned here? I would assume you tested at least the new file you referenced? Can we get rid of one or clarify the difference, please?

https://github.com/os-autoinst/openQA/commit/ca56e5b38a118bcd866698cbc79e6e937a853184 seems relevant

Actions #7

Updated by ybonatakis about 2 months ago

I just managed to try the xml.
the installation failed but for completely different reason.
The steps to took:

  1. sudo yast2 autoyast check-profile filename=ay-openqa-worker.xml.erb output=result.xml run-scripts=true run-erb=true
  2. Upload it and run an installation on a VM using autoyast=

So I wonder if this is actually used somewhere and if it was ever worked.
do we want another ticket for fix this?

Actions #8

Updated by ybonatakis about 2 months ago

So the steps and the generated xml seems to work on Leap. But not with TW.

Actions #9

Updated by okurz about 2 months ago

I guess it wasn't clear that the .xml.erb file needs to be transformed into an .xml file using an existing openSUSE system with yast. Can you reference the according official documentation where that transformation step is described?

Actions #10

Updated by ybonatakis about 2 months ago

okurz wrote in #note-9:

I guess it wasn't clear that the .xml.erb file needs to be transformed into an .xml file using an existing openSUSE system with yast. Can you reference the according official documentation where that transformation step is described?

you mean here or at the wiki?

Actions #11

Updated by ybonatakis about 2 months ago

As i said installation is performed with errors/warnings and i think the installation is not fully successful, ending in a install console with a prompt to login which i dont know how.
Should i consider this part of this ticket?

Actions #12

Updated by livdywan about 2 months ago

ybonatakis wrote in #note-11:

As i said installation is performed with errors/warnings and i think the installation is not fully successful, ending in a install console with a prompt to login which i dont know how.
Should i consider this part of this ticket?

If the existing steps are not working, and I count 3 problems here now, it feels like we need a new ticket like Ensure openQA autoyast profile is known to work

Actions #13

Updated by ybonatakis about 2 months ago

So the xml has been updated and the main requirement is fullfilled. There is the AC2 which is not clear at this point. I see that that section needs to be updated but IIUC not with the .erb file. It should also include the steps to generate the xml from .erb if nothing change.

Anyone have suggestions or should I resolve it and follow what https://progress.opensuse.org/issues/155305#note-12 says?

Actions #14

Updated by okurz about 2 months ago

ybonatakis wrote in #note-13:

So the xml has been updated and the main requirement is fullfilled

Actually it's not fulfilled. As it turned out the file you changed is not "The commonly used openQA installation autoyast profile". I suggest you crosscheck with the people that did the recent installation of machines which profiles they actually used.

There is the AC2 which is not clear at this point. I see that that section needs to be updated but IIUC not with the .erb file. It should also include the steps to generate the xml from .erb if nothing change.

The ticket description does not mention an "AC2" but I guess you mean that our wiki instructions should actually be usable.

Anyone have suggestions or should I resolve it and follow what https://progress.opensuse.org/issues/155305#note-12 says?

All issues you consider feasible to fix as part of this ticket please fix as part of this ticket. For the rest please report separate specific tickets

Actions #15

Updated by ybonatakis about 2 months ago

  • Status changed from In Progress to Feedback

okurz wrote in #note-14:

ybonatakis wrote in #note-13:

So the xml has been updated and the main requirement is fullfilled

Actually it's not fulfilled. As it turned out the file you changed is not "The commonly used openQA installation autoyast profile". I suggest you crosscheck with the people that did the recent installation of machines which profiles they actually used.

As i understood, they used to use the shortlink which was pointing to a specific commit. However the ay-openqa-worker.xml.erb is the corresponding updated version and seems to work just fine.

There is the AC2 which is not clear at this point. I see that that section needs to be updated but IIUC not with the .erb file. It should also include the steps to generate the xml from .erb if nothing change.

The ticket description does not mention an "AC2" but I guess you mean that our wiki instructions should actually be usable.

Yup not a AC but the second suggestion. LInks have been updated.
I created a new short link to ay-openqa-worker.xml.erb of the master branch. Named: ay.xml.erb

Anyone have suggestions or should I resolve it and follow what https://progress.opensuse.org/issues/155305#note-12 says?

All issues you consider feasible to fix as part of this ticket please fix as part of this ticket. For the rest please report separate specific tickets

Finally tested in VM. chrony is installed and service is running.

I will file tickets for:

  • some warnings in the generation of the file.
Actions #17

Updated by ybonatakis about 2 months ago

  • Subtask #156169 added
Actions #18

Updated by okurz about 2 months ago

  • Subtask deleted (#156169)
Actions #19

Updated by okurz about 2 months ago

  • Related to action #156169: Automatically validate ay-openqa-worker.xml.erb added
Actions #20

Updated by okurz about 2 months ago

ybonatakis wrote in #note-16:

Q: should i also edit https://github.com/os-autoinst/openQA/blob/master/contrib/ay-openqa-worker-leap-3-nvme.xml?

yes please.

And thank you for creating #156169. With that after the above change please resolve here. Adding automatic validation of all autoyast profiles is out-of-scope for here :)

Actions #22

Updated by ybonatakis about 2 months ago

  • Status changed from Feedback to Resolved
Actions

Also available in: Atom PDF