action #120246
closed[security][15sp4][QU1] test fails in hostname_inst on ppc64le
0%
Description
Observation¶
openQA test in scenario sle-15-SP4-Online-QR-ppc64le-fips_install_lvm_encrypt_separate_boot@ppc64le-hmc-single-disk fails in
hostname_inst
Test suite description¶
Testsuite maintained at https://gitlab.suse.de/qe-security/osd-sle15-security.
Reproducible¶
Fails since (at least) Build 170.2
Expected result¶
Last good: (unknown) (or more recent)
Further details¶
Always latest result in this scenario: latest
Updated by pstivanin over 1 year ago
- Subject changed from [security][15sp4][QU1] test fails in hostname_inst on s390x to [security][15sp4][QU1] test fails in hostname_inst on ppc64le
Updated by amanzini over 1 year ago
first observation, the SUT gets an hostname which is associated to the IP:
$ host redcurrant-4.qa.suse.de
redcurrant-4.qa.suse.de has address 10.162.8.4
$ host 10.162.8.4
4.8.162.10.in-addr.arpa domain name pointer redcurrant-4.qa.suse.de.
Updated by amanzini over 1 year ago
- Related to action #117424: [qe-core][sle15sp5][functional]test fails in network_hostname added
Updated by rfan1 over 1 year ago
amanzini wrote:
first observation, the SUT gets an hostname which is associated to the IP:
$ host redcurrant-4.qa.suse.de redcurrant-4.qa.suse.de has address 10.162.8.4 $ host 10.162.8.4 4.8.162.10.in-addr.arpa domain name pointer redcurrant-4.qa.suse.de.
For powerVM machine, the ip addr and hostname are defined in dhcp server:
https://gitlab.suse.de/qa-sle/qanet-configs/-/blob/master/etc/dhcpd.conf
Updated by amanzini over 1 year ago
- Status changed from In Progress to Feedback
Updated by openqa_review over 1 year ago
- Status changed from Resolved to Feedback
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: fips_install_lvm_full_encrypt
https://openqa.suse.de/tests/10019763#step/hostname_inst/1
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released" or "EOL" (End-of-Life)
- The bugref in the openQA scenario is removed or replaced, e.g.
label:wontfix:boo1234
Expect the next reminder at the earliest in 28 days if nothing changes in this ticket.
Updated by amanzini over 1 year ago
- Status changed from Feedback to In Progress
update schedule
schedule/security/encryption/fips_lvm_full_encrypt_maint.yaml
as done in https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/15954
Updated by amanzini over 1 year ago
https://openqa.suse.de/tests/10092603#step/perform_installation/2
Seems on 390x the reboot_timeout=0 is not being used, so when the installation is complete there is a count-down timer on the popup "The system will reboot" and after 10 seconds it reboots; leaving the module logs_from_installation_system in a unstable state.
Same test on other arch does not have this automatic reboot https://openqa.suse.de/tests/10092616#step/perform_installation/2
Updated by amanzini over 1 year ago
- Status changed from In Progress to Resolved
Updated by openqa_review over 1 year ago
- Status changed from Resolved to Feedback
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: fips_install_lvm_full_encrypt
https://openqa.suse.de/tests/10019763#step/hostname_inst/1
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released" or "EOL" (End-of-Life)
- The bugref in the openQA scenario is removed or replaced, e.g.
label:wontfix:boo1234
Expect the next reminder at the earliest in 44 days if nothing changes in this ticket.
Updated by amanzini over 1 year ago
- Status changed from Feedback to In Progress
Updated by amanzini over 1 year ago
- Status changed from In Progress to Resolved
hostname_inst test has been unscheduled since it is redundant. Hostname check is done after the installation