action #25542
closed[sle][sles4sap][sle15] initial setup
0%
Updated by okurz over 6 years ago
- Copied from coordination #23886: [sle][functional][desktop][sle15][epic] initial setup added
Updated by okurz over 6 years ago
- Status changed from New to In Progress
- Assignee deleted (
okurz)
I added a new testsuite "create_hdd_sles4sap_gnome" and scheduled it in the Test Development: SLE15 job group. QA engineers for SLES4SAP, please review starting with next build and accomodate in a validation job group.
Updated by okurz over 6 years ago
- Copied to action #25544: [sle][hpc][sle15] initial setup added
Updated by acarvajal over 6 years ago
Merge request to include in rsync.pl SAP Applications Module sync to openQA repos: https://gitlab.suse.de/openqa/scripts/merge_requests/156
Updated by okurz over 6 years ago
- Assignee set to acarvajal
Hi acarvajal, your MR is active since three weeks but the according openQA job to create a sles4sap installation fails in an earlier step since a long time, e.g. the latest run: https://openqa.suse.de/tests/1283412#
Can you take care?
Updated by acarvajal over 6 years ago
- Assignee deleted (
acarvajal)
The problem was due to the SCC code being used in the test. Updated "create_hdd_sles4sap_gnome" with a working code and now the test passes the scc_registration test:
https://openqa.suse.de/tests/1320239#
(It's stopping at the system_role test due to bsc#1072592. Still investigating if that's a bug though)
Also, the SCC code for x86_64 is different than the one for ppc64le, so I guess I will need to create a "create_hdd_sles4sap_gnome_ppc" with the PPC code and schedule that one instead of "create_hdd_sles4sap_gnome" in the job group. Will do that on Monday unless there are objections
Updated by okurz over 6 years ago
acarvajal wrote:
Also, the SCC code for x86_64 is different than the one for ppc64le, so I guess I will need to create a "create_hdd_sles4sap_gnome_ppc" with the PPC code and schedule that one instead of "create_hdd_sles4sap_gnome" in the job group. Will do that on Monday unless there are objections
Yes, I object :) Please don't create architecture specific testsuites. They are messy and also painful when trying to create downstream jobs. We invested quite some effort to get rid of these and I don't see a necessity. regcode are commonly set on the media, e.g. in https://openqa.suse.de/admin/products . For SLE12 we just put the according code on the according media, e.g. the sles4sap code on the sles4sap DVD. With the SLE15 Installer-DVD that is not feasible anymore of course. I suggest to change the test code to support product specific regcodes. We already have the test variable "SLE_PRODUCT" in tests and I think this one could be used. E.g. in lib/registration.pm where SCC_REGCODE is used one could use get_var('SCC_REGCODE_' . get_var('SLE_PRODUCT')).
Updated by acarvajal over 6 years ago
okurz wrote:
Yes, I object :) Please don't create architecture specific testsuites. They are messy and also painful when trying to create downstream jobs. We invested quite some effort to get rid of these and I don't see a necessity.
Figured there could be something like that due to the lack of architecture-specific test suites on openqa.suse.de.
regcode are commonly set on the media, e.g. in https://openqa.suse.de/admin/products . For SLE12 we just put the according code on the according media, e.g. the sles4sap code on the sles4sap DVD. With the SLE15 Installer-DVD that is not feasible anymore of course. I suggest to change the test code to support product specific regcodes. We already have the test variable "SLE_PRODUCT" in tests and I think this one could be used. E.g. in
lib/registration.pmwhere SCC_REGCODE is used one could useget_var('SCC_REGCODE_' . get_var('SLE_PRODUCT')).
Will not create a ppc64le specific test and instead work on this.
Updated by acarvajal over 6 years ago
PR for product specific registration codes (SCC_REGCODE_ . getvar('SLE_PRODUCT'))
https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/4088
Updated by acarvajal over 6 years ago
okurz wrote:
I added a new testsuite "create_hdd_sles4sap_gnome" and scheduled it in the Test Development: SLE15 job group. QA engineers for SLES4SAP, please review starting with next build and accomodate in a validation job group.
Moved the "create_hdd_sles4sap_gnome" tests to the SLES for SAP Applications job group.
Updated by acarvajal about 6 years ago
- Status changed from In Progress to Resolved
Closing this since SLES4SAP tests are already scheduled in openqa.suse.de and are in use during build validation.
Job Group: https://openqa.suse.de/group_overview/146
Also a test was configured in Staging:S as requested by the RM:
https://openqa.suse.de/tests/overview?distri=sle&version=15&build=S.361.1&groupid=125