I use rollbacks fairly extensively both via the provisioning events
rollback and via package profiles. Also use the profiles to sync
machines. At least on RHEL5 and so far RHEL6 it has been by in large
successful.
Suspect there is some issue with your channel setup and/or package
availability. Normally when they are not available it will tell you as
such but I have seen some oddities when the client doesnt see this but
SW does.
Below I attempted to duplicate what you did and at least on my end it
was successful. This does not help you much but I can confirm it can
work so I dont think the sync to package profiles are broken in this way
though they do have some issues. Might be worth making sure your
metadata caches are all cleaned up etc.
Server:SW 1.5 on RHEL 5.6
Client:RHEL 5.4
1)Created profile of system.
2)Upgrade the following on left to that on right(this was listed by SW):
vim-common-7.0.109-7.el5:2.x86_64
vim-common-7.0.109-6.el5:2.x86_64
vim-enhanced-7.0.109-7.el5:2.x86_64
vim-enhanced-7.0.109-6.el5:2.x86_64
vim-minimal-7.0.109-7.el5:2.x86_64
vim-minimal-7.0.109-6.el5:2.x86_64
3)Went back to software and "sync'd" the server back to the profile
created in step #1.
SW indicated it would do the following:
vim-common x86_64 Downgrade to 7.0.109-6.el5:2
vim-enhanced x86_64 Downgrade to 7.0.109-6.el5:2
vim-minimal x86_64 Downgrade to 7.0.109-6.el5:2
During the process I watched the installed rpms:
root@beholder:~# rpm -qa | grep -i vim
vim-minimal-7.0.109-6.el5
vim-common-7.0.109-6.el5
vim-enhanced-7.0.109-6.el5
root@beholder:~# rpm -qa | grep -i vim
vim-common-7.0.109-7.el5
vim-minimal-7.0.109-7.el5
vim-enhanced-7.0.109-7.el5
root@beholder:~# rpm -qa | grep -i vim
vim-enhanced-7.0.109-6.el5
vim-common-7.0.109-6.el5
vim-minimal-7.0.109-6.el5
On 01/25/2012 10:22 AM, uri van creveld wrote:
Hi,
I'm running spacewalk 1.5 on RHEL 5 server/clients.
I want to use it mainly for installing erratas.
Today I tried applying a security patch for example - something that
updates 3 packages - vim-common vim-enhanced, vim-minimal
Before applying it I saved a system profile, so I can roll back to a
previous known and good configuration.
I applied the errata, it went fine.
Then I tried to compare the system to the stored profile and revert the change.
At first, the old packages were not in the channel so I could not
revert them. So I put them in a repository and synced the channel.
Afterwards, I tried reverting the packages again. The action was
scheduled, picked up, and successfull. BUT -
upon checking in the server, I found out that all 3 packages were
removed only! spacewalk did not install the previous versions, and did
not say anything!
This is bad... I want to be ably to rely on this feature when I find a
problem in a new package.
please help...
_______________________________________________
Spacewalk-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/spacewalk-list
_______________________________________________
Spacewalk-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/spacewalk-list
