Skip to content

Conversation

alvarocarvajald
Copy link
Contributor

@alvarocarvajald alvarocarvajald commented Sep 2, 2025

The default 8s timeout can cause some tests on pvm_hmc backend to fail as lib/sles4sap::reboot() would call 2 times lib/opensusebasetests::wait_grub(), and 8s could be not enough time to assert the grub screen twice.

This commit disables the grub timeout on SLES for SAP 16.0 installations by adding stopOnBootMenu in
data/sles4sap/agama/sles_sap_default_ppc64le.jsonnet and also adds on the related schedules the module installation/grub_test to handle the grub screen before first boot.

@okurz
Copy link
Member

okurz commented Sep 2, 2025

The default 8s timeout can cause some tests on pvm_hmc backend to fail as lib/sles4sap::reboot() would call 2 times lib/opensusebasetests::wait_grub(), and 8s could be not enough time to assert the grub screen twice.

This commit disables the grub timeout on SLES for SAP 16.0 installations by adding stopOnBootMenu in data/sles4sap/agama/sles_sap_default_ppc64le.jsonnet

Why do that only for SLES4SAP and only for ppc64le? IMHO the timeout should be disabled everywhere consistently

@alvarocarvajald
Copy link
Contributor Author

alvarocarvajald commented Sep 2, 2025

The default 8s timeout can cause some tests on pvm_hmc backend to fail as lib/sles4sap::reboot() would call 2 times lib/opensusebasetests::wait_grub(), and 8s could be not enough time to assert the grub screen twice.
This commit disables the grub timeout on SLES for SAP 16.0 installations by adding stopOnBootMenu in data/sles4sap/agama/sles_sap_default_ppc64le.jsonnet

Why do that only for SLES4SAP and only for ppc64le? IMHO the timeout should be disabled everywhere consistently

I agree. We already did on qemu in fact, but left it as it was on the other architecturesbackends as it was working.

@okurz
Copy link
Member

okurz commented Sep 2, 2025

The default 8s timeout can cause some tests on pvm_hmc backend to fail as lib/sles4sap::reboot() would call 2 times lib/opensusebasetests::wait_grub(), and 8s could be not enough time to assert the grub screen twice.
This commit disables the grub timeout on SLES for SAP 16.0 installations by adding stopOnBootMenu in data/sles4sap/agama/sles_sap_default_ppc64le.jsonnet

Why do that only for SLES4SAP and only for ppc64le? IMHO the timeout should be disabled everywhere consistently

I agree. We already did on qemu in fact, but left it as it was on the other architecturesbackends as it was working.

But why keep it different then? I assume that sooner or later this will make problems and IMHO all those little differences make the analysis harder

Copy link
Contributor

@mpagot mpagot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Copy link
Contributor

@lpalovsky lpalovsky left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

The default 8s timeout can cause some tests on pvm_hmc backend
to fail as `lib/sles4sap::reboot()` would call 2 times
`lib/opensusebasetests::wait_grub()`, and 8s could be not enough time to
assert the grub screen twice.

This commit disables the grub timeout on SLES for SAP 16.0 installations
by adding `stopOnBootMenu: true` in
`data/sles4sap/agama/sles_sap_default_ppc64le.jsonnet` and also adds in
the related schedules the module `installation/grub_test` to handle the
grub screen before first boot.

Related Ticket: https://jira.suse.com/browse/TEAM-10611
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants