Project

General

Profile

Actions
Copy link

action #158760

closed

[qe-core][qem][sle12sp3] Fix autoyast config file to use different 'EXTRA_CUSTOMER_REPOS' for different Flavors

Added by rfan1 22 days ago. Updated 22 days ago.

Status:
Resolved
Priority:
Normal
Assignee:
dzedro
Category:
Bugs in existing tests
Target version:
QA - QE-Core: Ready
Start date:
Due date:
% Done:

100%

Estimated time:
Difficulty:
Sprint:
QE-Core: April Sprint 24 (Apr 10 - May 08)
Tags:
qe-core-april-sprint, bugbusters

Description

Description

For sle12 autoyast configuration files, like https://github.com/os-autoinst/os-autoinst-distri-opensuse/blob/master/data/autoyast_qam/12-common_base_installation.xml.ep

We have below repo defined:

      <listentry>
        <media_url>http://dist.suse.de/ibs/SUSE/Updates/SLE-SERVER/12-SP3-LTSS-TERADATA/x86_64/update/</media_url>
        <name>12-SP3-LTSS-TERADATA-Updates</name>
        <alias>12-SP3-LTSS-TERADATA-Updates</alias>
      </listentry>

However, we may need to use the below link for flavor sle-12-SP3-Server-DVD-Updates-TERADATA:

http://dist.suse.de/ibs/SUSE/Updates/SLE-SERVER/12-SP3-TERADATA/x86_64/update/

Action items

  1. Add new logic to use different repo for different flavor
Server-DVD-Updates:
      <listentry>
        <media_url>http://dist.suse.de/ibs/SUSE/Updates/SLE-SERVER/12-SP3-LTSS-TERADATA/x86_64/update/</media_url>
        <name>12-SP3-LTSS-TERADATA-Updates</name>
        <alias>12-SP3-LTSS-TERADATA-Updates</alias>
      </listentry>

or 

Server-DVD-Updates-TERADATA
      <listentry>
        <media_url>http://dist.suse.de/ibs/SUSE/Updates/SLE-SERVER/12-SP3-TERADATA/x86_64/update/</media_url>
        <name>12-SP3-TERADATA-Updates</name>
        <alias>12-SP3-TERADATA-Updates</alias>
      </listentry>
Actions
Copy link
 #1

Updated by szarate 22 days ago

  • Sprint set to QE-Core: April Sprint 24 (Apr 10 - May 08)
  • Tags changed from bugbusters to bugbusters, qe-core-april-sprint
  • Status changed from New to Workable
Actions
Copy link
 #2

Updated by dzedro 22 days ago

  • Status changed from Workable to In Progress
Actions
Copy link
 #3

Updated by dzedro 22 days ago

  • Status changed from In Progress to Resolved
  • % Done changed from 0 to 100
Actions
Copy link

Also available in: Atom PDF