Project

General

Profile

Actions
Copy link

action #150836

closed

Add SLE-15-SP6-Module-Packagehub to proxySCC

Added by zoecao 6 months ago. Updated 4 months ago.

Status:
Resolved
Priority:
High
Assignee:
leli
Target version:
Current
Start date:
2023-11-14
Due date:
% Done:

0%

Estimated time:

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

Actions
Copy link
 #1

Updated by leli 6 months ago

  • Status changed from New to Workable
  • Target version set to Current
Actions
Copy link
 #2

Updated by leli 6 months ago

  • Priority changed from Normal to High
Actions
Copy link
 #3

Updated by leli 6 months ago

  • Status changed from Workable to In Progress
  • Assignee set to leli
Actions
Copy link
 #4

Updated by leli 6 months ago

I need contact RM of SLES15SP6 to know the reason why packageHub doesn't exist in ProxySCC repo https://openqa.suse.de/assets/repo/.

Actions
Copy link
 #5

Updated by leli 6 months ago

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.

Actions
Copy link
 #6

Updated by leli 5 months ago

  • Status changed from In Progress to Resolved
Actions
Copy link
 #7

Updated by openqa_review 4 months 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: 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:

  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" or "EOL" (End-of-Life)
  3. 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.

Actions
Copy link
 #8

Updated by leli 4 months ago

  • Status changed from Feedback to Resolved

The failure has nothing related with ticket, it looks like a random environment issue.

Actions
Copy link

Also available in: Atom PDF