Bug ID 1105992
Summary Transactional-Update broken in snapshot 20180824
Classification openSUSE
Product openSUSE Tumbleweed
Version Current
Hardware Other
OS Other
Status NEW
Severity Major
Priority P5 - None
Component Kubic
Assignee iforster@suse.com
Reporter rbrown@suse.com
QA Contact qa-bugs@suse.de
CC kubic-bugs@opensuse.org
Found By ---
Blocker ---

0824 introduced transactional-update 2.6

https://build.opensuse.org/package/rdiff/openSUSE:Factory/transactional-update?linkrev=base&rev=32

It's failing all tests and appears to be displaying incorrect behaviour

https://openqa.opensuse.org/tests/742638#step/transactional_update/57

Compared to 0822 I'm noticing the following differences:

https://openqa.opensuse.org/tests/741289#step/transactional_update/57

(note: the code for the test does not appear to have changed:
https://github.com/os-autoinst/os-autoinst-distri-opensuse/blob/master/tests/caasp/transactional_update.pm
)

Update test #2 is meant to be a no-op, because it should be updating when there
is nothing to do

In 0822 the pointless `cleanup up` test produced the following logs:

> # Result:
> Checking for newer version.
> transactional-update 2.6 started
> Options: cleanup up
> Separate /var detected.
> Adding cleanup algorithm to snapshot #6
> Adding "important=yes" to snapshot #6
> zypper: nothing to update
> transactional-update finished
> trup-0-

In 0824 the exact same test produces the following logs:

> # Result:
> Checking for newer version.
> transactional-update 2.6 started
> Options: cleanup up
> Separate /var detected.
> Adding cleanup algorithm to snapshot #6
> Adding "important=yes" to snapshot #6
> /usr/sbin/transactional-update: line 760: [: too many arguments
> Creating read-only snapshot of current system state (#8)
> Copying /etc state into snapshot /.snapshots/9/snapshot
> Copying /etc state into snapshot /.snapshots/10/snapshot
> Calling zypper up
> Loading repository data...
> Reading installed packages...
> 
> Nothing to do.
> Trying to rebuild kdump initrd
> Please reboot your machine to activate the changes and avoid data loss.
> transactional-update finished
> trup-0-

I find the following lines in 0824 suspicious, leading me to the questions
below:

> /usr/sbin/transactional-update: line 760: [: too many arguments

Why does txl-upd now complain about too many arguments?

> Creating read-only snapshot of current system state (#8)
> Copying /etc state into snapshot /.snapshots/9/snapshot
> Copying /etc state into snapshot /.snapshots/10/snapshot

Why does txl-upd make 3 snapshots (8, 9, 10) even when there is nothing to do?

Why does txl-upd make 2 snapshots for /etc? (This is less suspicious, I'm just
curious)

Bug marked as Major because it makes all of Kubics tests red ;)


You are receiving this mail because: