Bug 1075077 - [Build 1548.11] openQA test fails in upgrade_select_opensuse
[Build 1548.11] openQA test fails in upgrade_select_opensuse
Status: RESOLVED WORKSFORME
Classification: openSUSE
Product: openSUSE Tumbleweed
Classification: openSUSE
Component: YaST2
Current
Other Other
: P5 - None : Normal (vote)
: ---
Assigned To: E-mail List
Jiri Srain
http://openqa.opensuse.org/tests/5771...
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2018-01-08 18:47 UTC by Dominique Leuenberger
Modified: 2018-01-09 12:08 UTC (History)
0 users

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Dominique Leuenberger 2018-01-08 18:47:40 UTC
## Observation

openQA test in scenario opensuse-Staging:E-Staging2-DVD-x86_64-update_staging@64bit fails in
[upgrade_select_opensuse](http://openqa.opensuse.org/tests/577173/modules/upgrade_select_opensuse/steps/7)


## Reproducible

Fails since (at least) Build [1548.9](http://openqa.opensuse.org/tests/576822)


## Expected result

Last good: [1548.7](http://openqa.opensuse.org/tests/575407) (or more recent)


## Further details

Always latest result in this scenario: [latest](http://openqa.opensuse.org/tests/latest?machine=64bit&version=Staging%3AE&distri=opensuse&flavor=Staging2-DVD&test=update_staging&arch=x86_64)

## More information

Update options used to list much more information than the product being updated, namely 'update based on pattern <list of patterns>'

https://openqa.opensuse.org/tests/575407#step/upgrade_select_opensuse/6 is how it looked before

I suspect the latest changes of yast2-update to be responsible here
Comment 1 Ladislav Slezák 2018-01-09 08:42:05 UTC
The change was intentional, see https://bugzilla.suse.com/show_bug.cgi?id=1071708
Comment 2 Dominique Leuenberger 2018-01-09 08:44:52 UTC
The change was further discussed on IRC and the fact that the pattern list no longer shows is an intentional side effect of switching to 'zypper dup' mode for yast2-update.

I created a new needle

A positive side effect of this change should be that yast2-update would now be able to update between TW snapshots as well (as zypper dup was/is the only valid way, with yast2-update now also using zypper dup, it becomes valid)

Closing the bug as 'worksforme'
Comment 3 Lukas Ocilka 2018-01-09 10:11:21 UTC
We are sorry for not informing you/openQA, which we actually usually do,
but this was a special case: Bug #1071708 has been implemented without
planning (out of a Scrum sprint) and, in fact, by the PjM.
Comment 4 Dominique Leuenberger 2018-01-09 10:16:05 UTC
No problem at all Lukas - we all work together on towards the same goal.
Comment 5 Jiri Srain 2018-01-09 12:08:04 UTC
Dominique, sorry for not telling you - I informed the SLE QA which I expected to be affected, but did not expect openSUSE to be affected too.

There will be be a small visual change in the future - if this change does not cause problems, I will update the control file so that the Update header in the proposal is not click-able (there are no options to edit).