Project

General

Profile

Actions
Copy link

action #42908

closed

coordination #42128: [functional][y][epic] Adjust partitioning tests to changes in storage-ng

[functional][y][fast] Fix openSUSE Factory :H staging project after recent storage-ng changes

Added by okurz over 5 years ago. Updated over 5 years ago.

Status:
Resolved
Priority:
High
Assignee:
riafarov
Category:
Bugs in existing tests
Target version:
SUSE QA - Milestone 20
Start date:
2018-10-01
Due date:
2018-11-06
% Done:

0%

Estimated time:
Difficulty:

Description

After #41849 it was missed to look into the openSUSE Factory :H staging project which is failing in openQA tests and was never enabled for the new product+test behaviour. Making sure the project can be accepted so that the corresponding changes end up in openSUSE Tumbleweed should also help us to keep test code cleaner and not need to handle TW as an "old" product.

Acceptance criteria

  • AC1: RAID test in openSUSE Factory :H pass so that the project can be accepted with recent storage-ng changes into openSUSE Tumbleweed
  • AC2: Other staging projects and the openSUSE Tumbleweed build validation tests are not negatively impacted

Suggestions

  • At best handle the detection of "new behaviour" dynamically
  • Or check for the specific staging project
Actions
Copy link
 #1

Updated by okurz over 5 years ago

  • Copied from action #42902: [functional][y] Re-enable RAID tests in Leap 15.1 staging added
Actions
Copy link
 #2

Updated by okurz over 5 years ago

  • Copied from deleted (action #42902: [functional][y] Re-enable RAID tests in Leap 15.1 staging)
Actions
Copy link
 #3

Updated by okurz over 5 years ago

  • Status changed from New to In Progress
  • Parent task set to #42128
Actions
Copy link
 #4

Updated by riafarov over 5 years ago

  • Status changed from In Progress to Feedback
Actions
Copy link
 #5

Updated by riafarov over 5 years ago

  • Status changed from Feedback to Resolved
Actions
Copy link
 #6

Updated by okurz over 5 years ago

  • Status changed from Resolved to Feedback

And now the scenario fails in https://openqa.opensuse.org/tests/782828#step/partitioning_raid/12 with a popup about "No device selected". Any ideas?

Actions
Copy link
 #7

Updated by riafarov over 5 years ago

@okurz, that seems like a bug, I will validate manually.

Actions
Copy link
 #8

Updated by riafarov over 5 years ago

Ok, it's previous state of the partitioner again, so I would ignore it, as we expect new behavior. https://build.opensuse.org/project/monitor/openSUSE:Factory:Staging:H?arch_x86_64=1&defaults=0&repo_standard=1&unresolvable=1

I will keep it open, but I don't think any additional action is required from our side atm.

Actions
Copy link
 #9

Updated by riafarov over 5 years ago

  • Status changed from Feedback to Resolved
Actions
Copy link
 #10

Updated by okurz over 5 years ago

\o/ Unfortunately :H is still not accepted. I guess we would help the YaST team to track that staging project because, you know, they assume they are kinda "done" but we never get the changes into openSUSE Tumbleweed and then SLE15SP1 becomes a mess … and history repeats …

Actions
Copy link
 #11

Updated by riafarov over 5 years ago

@okurz, I've put this topic to discuss with Lukas and Jiri during our next trip to Prague.

Actions
Copy link
 #12

Updated by okurz over 5 years ago

Cool. Where did you note this? We could use http://gitlab.suse.de/suse/rfc/issues/ for that, e.g. same as https://gitlab.suse.de/suse/rfc/issues/2

Actions
Copy link
 #13

Updated by riafarov over 5 years ago

@okurz, it's a good idea to raise this problem there as well, as it's relevant for other teams as well. I will try to phrase it there. As of now I have a document with points we got after YaST workshop, and put it there.

Actions
Copy link

Also available in: Atom PDF