action #115751
open[qe-sap] test fails in zypper_migration
0%
Description
Observation¶
zypper migration fails with metadata not found for 15-SP5 migration. probably not setup yet in SCC.
openQA test in scenario sle-15-SP5-Online-s390x-migration_online_sle15sp3_ha_alpha_node02@s390x-kvm-sle12 fails in
zypper_migration
Test suite description¶
The base test suite is used for job templates defined in YAML documents. It has no settings of its own.
Reproducible¶
Fails since (at least) Build 9.1
Expected result¶
Last good: (unknown) (or more recent)
Further details¶
Always latest result in this scenario: latest
Updated by maritawerner almost 2 years ago
- Subject changed from test fails in zypper_migration to [qe-sap] test fails in zypper_migration
Updated by zoecao almost 2 years ago
Hi, kindly fyi pls, this issue is caused by lacking of a setting: SCC_PROXY_URL=http://all-%BUILD%.proxy.scc.suse.de in the migration_online scc cases. For these migration online cases, if without the setting of SCC_PROXY_URL, when doing migration, it gets the migration target product repo from SCC, while SCC only mirror milestone build, then the daily builds are not tested.
I suppose for the migration online cases in this group, you also tend to test the daily builds, right? If yes, need to add the setting for the migration online cases.
BTW, the difference between with and without the setting is that with the setting, it echo the proxy_scc_url to /etc/SUSEConnect, to make the system getting the target product repo from proxySCC, an example here: https://openqa.suse.de/tests/9377867#step/pre_migration/13
If any questions about it, please feel free to contact me.
Updated by acarvajal almost 2 years ago
Confirmed with: http://mango.qa.suse.de/tests/4898
Updated by openqa_review almost 2 years ago
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: ha_rolling_upgrade_migration_node01
https://openqa.suse.de/tests/9518887#step/zypper_migration/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 openqa_review over 1 year ago
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: migration_online_sle15sp1_ltss_ha_alpha_node01
https://openqa.suse.de/tests/9678801#step/zypper_migration/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 56 days if nothing changes in this ticket.
Updated by slo-gin 4 months ago
This ticket was set to Normal priority but was not updated within the SLO period. Please consider picking up this ticket or just set the ticket to the next lower priority.