Project

General

Profile

Actions

action #46613

closed

[functional][y] test fails in yast_scc for postreg with sdk - no license is shown

Added by riafarov about 5 years ago. Updated about 5 years ago.

Status:
Resolved
Priority:
High
Assignee:
Category:
Bugs in existing tests
Target version:
SUSE QA - Milestone 23
Start date:
2019-01-24
Due date:
2019-03-12
% Done:

0%

Estimated time:
5.00 h
Difficulty:

Description

Observation

We have an issue with test as we use regurl for server only, and url for sdk is not replaced by the proxy scc.

NOTE: test was moved to the YaST job group

openQA test in scenario yast_scc fails in
yast_scc

Reproducible

Fails since (at least) Build 0114

Expected result

Last good: (unknown) (or more recent)

Further details

Always latest result in this scenario: latest

Suggestions

https://bugzilla.suse.com/show_bug.cgi?id=1123057 is resolved fixed, but behavior is still the same. So we need to verify how it worked with SLE12 SP4.
In this scenario SDK is added as addon, but SUT is unregistered, it might affect expectations we set.


Related issues 1 (0 open1 closed)

Copied to openQA Tests - action #48128: [functional][y] Improve our automatic detection of "no license is shown but expected" and vice versaResolvedJERiveraMoya2019-01-242019-03-26

Actions
Actions #1

Updated by riafarov about 5 years ago

  • Assignee set to riafarov

Seems that will be enough to add correct SCC_URL to the parent test suite, generating image: https://openqa.suse.de/tests/2399557

Actions #2

Updated by riafarov about 5 years ago

I've fixed regurl part, now we expect license, but it's not shown. Again can be some broken setup as we have SDK already installed, so not sure how registration will work...

Actions #3

Updated by riafarov about 5 years ago

  • Subject changed from [functional][y] test fails in yast_scc for postreg with sdk, wrong reg url is used to [functional][y] test fails in yast_scc for postreg with sdk - no license is shown
  • Status changed from Workable to Blocked

https://bugzilla.suse.com/show_bug.cgi?id=1123057 waiting for the reply in the bug.

Actions #4

Updated by okurz about 5 years ago

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: minimal+base+sdk+proxy_SCC-postreg
https://openqa.suse.de/tests/2422494

Actions #5

Updated by riafarov about 5 years ago

  • Due date changed from 2019-02-26 to 2019-03-12
  • Status changed from Blocked to Workable
  • Assignee deleted (riafarov)

Bug is fixed, but behavior hasn't been changed, so we need to take a look and reopen if needed.

Actions #6

Updated by okurz about 5 years ago

  • Priority changed from Normal to High

bumping to "High" as linked to currently failing job.

Actions #7

Updated by riafarov about 5 years ago

  • Description updated (diff)
  • Estimated time set to 5.00 h
Actions #8

Updated by okurz about 5 years ago

  • Copied to action #48128: [functional][y] Improve our automatic detection of "no license is shown but expected" and vice versa added
Actions #9

Updated by mloviska about 5 years ago

Actions #10

Updated by mloviska about 5 years ago

  • Status changed from Workable to In Progress
  • Assignee set to mloviska
Actions #11

Updated by mloviska about 5 years ago

I have found two failed runs on s390x from sle12sp4, which are not helpful.
https://openqa.suse.de/tests/1556955#next_previous

And that should be all. There is nothing else in openqa and auditlog does not show any record related to x86_64 arch.

Actions #12

Updated by mloviska about 5 years ago

I am creating image with http://Server-0122.SDK-0089.proxy.scc.suse.de sle-12-SP5-Server-DVD-x86_64-Build0122-create_hdd_minimal_base+sdk@64bit. Later I will try to run the yast_scc test suite

Actions #14

Updated by mloviska about 5 years ago

  • Status changed from In Progress to Blocked

Reopened. eula_url is still empty
https://bugzilla.suse.com/show_bug.cgi?id=1123057

Actions #15

Updated by riafarov about 5 years ago

  • Status changed from Blocked to Resolved

Let's resolve it. We won't need test adjustment as it's a bug. So well done, thanks for your findings.

Actions #16

Updated by okurz about 5 years ago

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: sles+sdk+proxy_SCC_via_YaST
https://openqa.suse.de/tests/2450647

Actions #17

Updated by okurz about 5 years ago

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: sles+sdk+proxy_SCC_via_YaST
https://openqa.suse.de/tests/2506909

Actions

Also available in: Atom PDF