QA » openQA Project » openQA Tests

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: mau-extratests-publiccloud@ec2_t2.large
https://openqa.suse.de/tests/3913288

To prevent further reminder comments one of the following options should be followed:

1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
2. The openQA job group is moved to "Released"
3. The label in the openQA scenario is removed

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: mau-extratests-publiccloud@ec2_t2.large
https://openqa.suse.de/tests/3913288

To prevent further reminder comments one of the following options should be followed:

1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
2. The openQA job group is moved to "Released"
3. The label in the openQA scenario is removed

The problem is the testcase I think.

tests/publiccloud/transfer_repos.pm

does
$args->{my_instance}->run_ssh_command(cmd => "sudo find /tmp/repos/ -name *.repo -exec zypper ar '{}' \;");

however, all *.repo files from SUSE:Maintenance:13632 have:
[SUSE_Maintenance_13632]
...

So the basesystem, public cloud module, python2 etc ... all have the same repository alias "SUSE_Maintenance_13632"

Only the first module will be added, likely alphabetically this will be Basesystem, the other zypper ar will just report error as the alias is taken already.