Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot rollback after boot to alternate release #955

Open
jberkus opened this issue Aug 25, 2017 · 5 comments
Open

Cannot rollback after boot to alternate release #955

jberkus opened this issue Aug 25, 2017 · 5 comments

Comments

@jberkus
Copy link

@jberkus jberkus commented Aug 25, 2017

Fedora 26 Atomic, tree 26.101

  1. rpm-ostree upgrade to 26.110

  2. reboot

  3. reboot again, this time select the old tree to boot into (26.101)

  4. At this point, we're running 26.101. However, 26.110 is still first in the boot order.

  5. Try to rollback to remove 26.110 from the boot order:

-bash-4.4# rpm-ostree rollback
error: No rollback deployment found
-bash-4.4# rpm-ostree rollback f6331bcd14577e0ee43db3ba5a44e0f63f74a86e3955604c20542df0b7ad8ad6
error: No rollback deployment found

There doesn't seem to be any way to be on the prior release after an alternate boot without a deploy or rebase, which is wrong.

@jberkus

This comment has been minimized.

Copy link
Author

@jberkus jberkus commented Aug 25, 2017

Really, it seems like "boot to alternate tree" leaves you in an undefined state that there's no clear way to get out of.

@jasonbrooks

This comment has been minimized.

Copy link
Contributor

@jasonbrooks jasonbrooks commented Aug 26, 2017

I did it like this:

  1. start at 26.102
  2. rpm-ostree upgrade to 26.114
  3. reboot, and choose 26.102 in grub
  4. rpm-ostree deploy 26.102
  5. reboot, and both grub entries are 26.102
@cgwalters

This comment has been minimized.

Copy link
Member

@cgwalters cgwalters commented Aug 26, 2017

I only briefly glanced at this, but probably fixed by #907 ?

@cgwalters

This comment has been minimized.

Copy link
Member

@cgwalters cgwalters commented Aug 26, 2017

If this is about "removing/cleaning", see rpm-ostree cleanup -p or -r.

@jlebon

This comment has been minimized.

Copy link
Member

@jlebon jlebon commented Aug 29, 2017

Right, the rollback bug specifically is a dupe of #906, albeit, reached through different means. The next TWR should have the fix for it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
4 participants
You can’t perform that action at this time.