Project

General

Profile

Actions
Copy link

action #25402

closed

[sles][functional] crosscheck scenarios with proxySCC - should behave the same as textmode scenarios

Added by mgriessmeier over 6 years ago. Updated over 6 years ago.

Status:
Resolved
Priority:
High
Assignee:
-
Category:
Bugs in existing tests
Target version:
openQA Project - Milestone 11
Start date:
2017-09-19
Due date:
2017-11-08
% Done:

0%

Estimated time:
Difficulty:

Description

Observation

openQA test in scenario sle-15-Leanos-DVD-aarch64-textmode+proxy_SCC@aarch64 fails in
yast2_i

Reproducible

Fails since (at least) Build 96.4

Expected result

Last good: See the textmode tests for SLE15 which use proxy-SCC but are not the scenario "proxy-SCC", e.g. https://openqa.suse.de/tests/1174125

Problem

proxySCC specifies a custom SCC url "SCC_URL_VALID" in the test suite pointing to "Server-…" which does not apply for SLE15 -> Either provide the SCC_URL_VALID in the test code based on versions or don't trigger that scenario for SLE15. We could just specify boolean switch in the test suite and based on that construct a URL within the test code. Maybe it's more explicit after all to define a scenario with EXIT_AFTER_START_INSTALL for testing the handling of invalid/valid URLs and don't mangle that into a test suite which we rely on for other purposes.

Further details

Always latest result in this scenario: latest

Actions
Copy link
 #1

Updated by okurz over 6 years ago

  • Priority changed from Normal to High

involving more than one current jobs

Actions
Copy link
 #2

Updated by okurz over 6 years ago

not yet workable: find corresponding textmode-non-proxy-scc and SLE12 SP3 GM reference jobs

Actions
Copy link
 #3

Updated by okurz over 6 years ago

  • Description updated (diff)
  • Status changed from New to In Progress
Actions
Copy link
 #4

Updated by okurz over 6 years ago

  • Target version set to Milestone 11
Actions
Copy link
 #5

Updated by okurz over 6 years ago

  • Blocks action #25164: [sle][functional][ppc64le] test fails to type correct scc url added
Actions
Copy link
 #6

Updated by okurz over 6 years ago

As the scenarios currently don't provide useful testing results I disabled for SLE15:

  • minimal+base+proxy_SCC
  • textmode+proxy_SCC

gnome+proxy_SCC+allmodules and sles+sdk+proxy_SCC_via_YaST don't have this problem and they have a different testing goal so keeping them

Actions
Copy link
 #7

Updated by riafarov over 6 years ago

  • Blocks deleted (action #25164: [sle][functional][ppc64le] test fails to type correct scc url)
Actions
Copy link
 #8

Updated by okurz over 6 years ago

  • Due date set to 2017-11-08
Actions
Copy link
 #9

Updated by Anonymous over 6 years ago

  • Assignee set to Anonymous
Actions
Copy link
 #10

Updated by Anonymous over 6 years ago

This is what I found out with scenarios that use proxy_SCC based on build 327.1:

gnome+proxy_SCC+allmodules................."SCC_ADDONS" : "serverapp,legacy,sdk
sles+sdk+proxy_SCC_via_YaST................"SCC_ADDONS" : "sdk
we-module.................................."SCC_ADDONS" : "serverapp,we
iscsi_ibft.................................EMPTY
zfcp.......................................EMPTY

RAID0......................."SCC_ADDONS" : "serverapp",
addon-module-ftp............"SCC_ADDONS" : "serverapp",
addon-module-http..........."SCC_ADDONS" : "serverapp",
allpatterns................."SCC_ADDONS" : "serverapp",
boot_to_snapshot............"SCC_ADDONS" : "serverapp",
btrfs......................."SCC_ADDONS" : "serverapp",
USBinstall@uefi............."SCC_ADDONS" : "serverapp",
create_hdd_textmode........."SCC_ADDONS" : "serverapp",
cryptlvm...................."SCC_ADDONS" : "serverapp",
cryptlvm_minimal_x.........."SCC_ADDONS" : "serverapp",
ext4........................"SCC_ADDONS" : "serverapp",
gnome......................."SCC_ADDONS" : "serverapp",
gnome_http.................."SCC_ADDONS" : "serverapp",
lvm........................."SCC_ADDONS" : "serverapp",
lvm+RAID1..................."SCC_ADDONS" : "serverapp",
lvm+resize_root............."SCC_ADDONS" : "serverapp",
minimal+base................"SCC_ADDONS" : "serverapp",
minimal+role_minimal........"SCC_ADDONS" : "serverapp",
minimal_x..................."SCC_ADDONS" : "serverapp",
nvme........................"SCC_ADDONS" : "serverapp",
package-dependency.........."SCC_ADDONS" : "serverapp",
remote_ssh_controller......."SCC_ADDONS" : "serverapp",
select_disk................."SCC_ADDONS" : "serverapp",
textmode+role_textmode......"SCC_ADDONS" : "serverapp",
toolchain_zypper............"SCC_ADDONS" : "serverapp",
xen........................."SCC_ADDONS" : "serverapp",
xfs........................."SCC_ADDONS" : "serverapp",
yast_self_update............"SCC_ADDONS" : "serverapp",
textmode@64bit-ipmi........."SCC_ADDONS" : "serverapp",
extmode@64bit..............."SCC_ADDONS" : "serverapp",
textmode@uefi..............."SCC_ADDONS" : "serverapp",

Actions
Copy link
 #11

Updated by Anonymous over 6 years ago

The scenarios mentioned in the description for build 280, 260 or earlier:

textmode...................."SCC_ADDONS" : "base,script,desktop,serverapp",
textmode+proxy_SCC.........."SCC_ADDONS" : "base,script,desktop,serverapp",

SCC_URL_VALID was disabled for recent build.

Actions
Copy link
 #12

Updated by Anonymous over 6 years ago

From build 280 on, the scenarios wit proxy_SCC behave the same as textmode scenarios, except the following:

gnome+proxy_SCC+allmodules................."SCC_ADDONS" : "serverapp,legacy,sdk
sles+sdk+proxy_SCC_via_YaST................"SCC_ADDONS" : "sdk
we-module.................................."SCC_ADDONS" : "serverapp,we

However these differences are reasonable.

Actions
Copy link
 #13

Updated by Anonymous over 6 years ago

  • Status changed from In Progress to Resolved
Actions
Copy link

Also available in: Atom PDF