I have a situation where rpm-ostree gets confused on which remote it should be
using. If register a system using subscription manager and then rebase it onto
some other tree, then perform an upgrade the system is totally confused about
what remote it should be using. The version of rpm-ostree I was using was
rpm-ostree-client-2015.5-3.atomic.el7.x86_64 which was composed into my test
tree. Here is the worked out example:
*Initial Setup*
===============
-bash-4.2# rpm-ostree status
TIMESTAMP (UTC) VERSION ID OSNAME
REFSPEC
* 2015-04-02 20:14:06 7.1.1-1 21bd99f9f3 rhel-atomic-host
rhel-atomic-host:rhel-atomic-host/7/x86_64/standard
-bash-4.2#
-bash-4.2#
-bash-4.2# ls /etc/ostree/remotes.d/
-bash-4.2# subscription-manager register --auto-attach
Username: rhn-gps-dmabe
Password:
The system has been registered with ID: 8e26062d-c1e7-42d1-b0a7-10da70f88a6c
Installed Product Current Status:
Product Name: Red Hat Enterprise Linux Atomic Host
Status: Subscribed
Product Name: Red Hat Enterprise Linux Server
Status: Subscribed
-bash-4.2# ls /etc/ostree/remotes.d/
redhat.conf
*Rebasing*
==========
-bash-4.2# ostree remote add lab --set=gpg-verify=false
http://192.168.122.121:8000/repo
-bash-4.2# rpm-ostree rebase lab:goodtree
568 metadata, 2724 content objects fetched; 173996 KiB transferred in 82
secondsCopying /etc changes: 25 modified, 4 removed, 58 added
Transaction complete; bootconfig swap: yes deployment count change: 1
Deleting ref 'rhel-atomic-host-ostree:rhel-atomic-host/7/x86_64/standard'
Changed:
...
...
-bash-4.2# reboot
*Upgrading*
==============
-bash-4.2# rpm-ostree status
TIMESTAMP (UTC) VERSION ID OSNAME
REFSPEC
* 2015-05-25 02:27:05 7e4135eeb5 rhel-atomic-host
lab:goodtree
2015-04-02 20:14:06 7.1.1-1 21bd99f9f3 rhel-atomic-host
rhel-atomic-host-ostree:rhel-atomic-host/7/x86_64/standard
-bash-4.2# rpm-ostree upgrade
Updating from: lab:goodtree
51 metadata, 60 content objects fetched; 112700 KiB transferred in 9 seconds
Copying /etc changes: 25 modified, 4 removed, 60 added
Transaction complete; bootconfig swap: yes deployment count change: 0
Changed:
...
...
Upgrade prepared for next boot; run "systemctl reboot" to start a reboot
-bash-4.2#
-bash-4.2# rpm-ostree status
TIMESTAMP (UTC) ID OSNAME REFSPEC
2015-05-27 01:42:42 559d5f3d7b rhel-atomic-host lab:goodtree
* 2015-05-25 02:27:05 7e4135eeb5 rhel-atomic-host
rhel-atomic-host-ostree:goodtree
-bash-4.2# reboot
*After Reboot*
==============
-bash-4.2# rpm-ostree status
TIMESTAMP (UTC) ID OSNAME REFSPEC
* 2015-05-27 01:42:42 559d5f3d7b rhel-atomic-host
rhel-atomic-host-ostree:goodtree
2015-05-25 02:27:05 7e4135eeb5 rhel-atomic-host
rhel-atomic-host-ostree:goodtree
Basically the problem is that the remote should be *lab*, but is
*rhel-atomic-host-ostree*.
-Dusty
