Red Hat Bugzilla – Bug 130884
Snapshots not created if using up2date
Last modified: 2007-07-31 10:35:19 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040303
Description of problem:
We have a system registered to a 3.4 satellite via a RHN proxy.
This machine was inadvertantly updated using 'up2date -u' on the
We wanted to rollback this machine, but the only packages profile
change snapshot that was saved was a kernel update, even though about
30 packages were updated with this up2date.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. up2date -u
2. Go to snapshots->rollback on RHN satellite
3. Check snapshot profiles
Actual Results: could not find a snapshot that matched the package
changes in the update
Expected Results: a snapshot corresponding to the up2date should exist
Eventually saved the system by doing a profile sync to an identical
server that had not been updated.
Can someone pick this up? British Airways are waiting on this.
I believe this is related to
Todd, can you help with reproducing this?
Works fine with
Against RHN Sat 3.4. The RHEL 3 box (up2date-4.2.14) was going
through an RHN Proxy 3.2 even.
I.e., works for me.
Cliff, you have anything to comment about this?
Comments? I would like to close this if it's old/resolved
- RHN Satellite 3.4 with schema 3.4-48 & rhns-3.4.0-53
- RHN Proxy 3.2.2 - rhns-proxy-3.2.2-28
- ES 3 Update 3 with up2date-4.2.38-1
I had the client registered to the satellite, going through the proxy
with a provisioning entitlement.
Ran up2date -uf and downloaded
kernel 2.4.21 20.0.1.EL
kernel-source 2.4.21 20.0.1.EL
libxml2 2.5.10 7
libxml2-python 2.5.10 7
Within the Satellite Web UI for this system I went to snapshots ->
Package profile -> packages and noted that it had listed :
kernel 2.4.21-20.0.1.EL 2.4.21-4.EL Current profile newer
kernel-source 2.4.21-20.0.1.EL Current profile only
libxml2 2.5.10-7 Current profile only
libxml2-python 2.5.10-7 Current profile only
So, as such, everything from my own test worked correctly and as
closing as CURRENTRELEASE then.