Bug 1254859 - After rpm-ostree upgrade, new version isn't set as default
Summary: After rpm-ostree upgrade, new version isn't set as default
Keywords:
Status: CLOSED DUPLICATE of bug 1226520
Alias: None
Product: Atomic
Classification: Retired
Component: rpm-ostree
Version: unspecified
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Colin Walters
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-08-19 06:11 UTC by Takashi Matsumura
Modified: 2015-08-20 09:41 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-08-20 09:41:28 UTC
RHEL 7.3 requirements from Atomic Host:
Embargoed:

Attachments (Terms of Use)

Description Takashi Matsumura 2015-08-19 06:11:20 UTC 
Description of problem:
rpm-ostree upgrade should set a new version as the default for the next boot, but it doesn't.


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. Install Fedora Atomic Host to Oracle Virtual Box 5.0.0 r107573 using Fedora-Cloud_Atomic-x86_64-22.iso
2. Login to Atomic Host as root
3. execute "rpm-ostree upgrade" to 
4. execute "systemctl reboot"

Actual results:
After step 4, Grub boot menu shows old version(22.17) as the default

Expected results:
Grub boot menu shows new version(22.96) as eht default.

Additional info:
Comment 1 Matthew Barnes 2015-08-19 13:14:49 UTC 
Probably a duplicate of bug #1226520
Comment 2 Takashi Matsumura 2015-08-20 09:41:28 UTC 
(In reply to Matthew Barnes from comment #1)
> Probably a duplicate of bug #1226520

Thank you for your comment.
Yes. It's a duplicate of it.
I'll close this as duplicate of bug #1226520
Sorry.

*** This bug has been marked as a duplicate of bug 1226520 ***
Note You need to log in before you can comment on or make changes to this bug.