action #150836
closed
Add SLE-15-SP6-Module-Packagehub to proxySCC
Added by zoecao 6 months ago.
Updated 4 months ago.
Description
Motivation :
Packagehub can not be tested in migration daily job group because SLE-15-SP6-Module-Packagehub is not available in proxySCC. Now [in the proxySCC], the packagehub related Pool is SLE-15-SP6-Module-Packagehub- Subpackages -POOL instead of SLE-15-SP6-Module-Packagehub-POOL. Need to add SLE-15-SP6-Module-Packagehub to proxyscc.
Acceptance criteria
AC1 : Contact with openqa tool team and ask how to add 15-SP6-Packagehub to proxyscc
AC2 : Add SLE-15-SP6-Module-Packagehub to proxyscc
- Status changed from New to Workable
- Target version set to Current
- Priority changed from Normal to High
- Status changed from Workable to In Progress
- Assignee set to leli
Got info from Santi that 'Santiago Zarate 1 day ago, phub won't be enabled until Beta1 or later iirc'. I think we can wait and check this after BETA1 released, or consider to workaround it.
- Status changed from In Progress to Resolved
- 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: online_sles15sp5_pscc_basesys-srv-python3-desk-phub_def_full_zypp
https://openqa.suse.de/tests/13242869#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 76 days if nothing changes in this ticket.
- Status changed from Feedback to Resolved
The failure has nothing related with ticket, it looks like a random environment issue.
Also available in: Atom
PDF