Bug ID 1181763
Summary transactional-update clobbering itself
Classification openSUSE
Product openSUSE Tumbleweed
Version Current
Hardware Other
OS Other
Status NEW
Severity Normal
Priority P5 - None
Component MicroOS
Assignee kubic-bugs@opensuse.org
Reporter amajer@suse.com
QA Contact qa-bugs@suse.de
Found By ---
Blocker ---

After first boot, I noticed that update is running. Great. Then, I try to run
transactional-update again. Expectation is this would abort unless user
specifies some special flag. Reality is that it just proceeds after a WARNING
that seems to be disregarded.


    localhost:~ # transactional-update
    Checking for newer version.
    transactional-update 2.28.3 started
    Options:
    Separate /var detected.
    /etc on overlayfs detected.
    WARNING: You are creating a snapshot from a different base (1) than the
             current default snapshot (2).
             If you want to continue a previous snapshot use the --continue
             option, otherwise the previous changes will be discarded.
    Calling zypper up
    Loading repository data...
    Reading installed packages...

    The following NEW package is going to be installed:
      libinih0

    The following 25 packages are going to be upgraded:
      MicroOS-release MicroOS-release-dvd combustion gettext-runtime
libapparmor1 libfido2-1 libfido2-udev libncurses6 libtextstyle0 ncurses-utils
openssh openssh-clients openssh-common openssh-server raspberrypi-firmware
raspberrypi-firmware-config raspberrypi-firmware-dt rpm sudo
system-group-hardware system-group-kvm system-user-nobody sysuser-shadow
terminfo-base xfsprogs

    The following product is going to be upgraded:
    openSUSE MicroOS
      20210122-0 -> 20210128-0
        Product 'openSUSE MicroOS' requires to be updated by calling 'zypper
dup'!
    ....

    Warning: The following files were changed in the snapshot, but are shadowed
by
    other mounts and will not be visible to the system:
    /.snapshots/3/snapshot/var/lib/sshd/is-enabled.rpmtmp

    Please reboot your machine to activate the changes and avoid data loss.
    New default snapshot is #3 (/.snapshots/3/snapshot).
    transactional-update finished




    localhost:~ #
    localhost:~ # transactional-update
    Checking for newer version.
    transactional-update 2.28.3 started
    Options:
    Separate /var detected.
    /etc on overlayfs detected.
    WARNING: You are creating a snapshot from a different base (1) than the
             current default snapshot (3).
             If you want to continue a previous snapshot use the --continue
             option, otherwise the previous changes will be discarded.
    Calling zypper up

    ...


You are receiving this mail because: