Description of problem:"rhua update" doesnt sync content on CDS if package already exist on rhua but not on CDS
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. remove package zsh on CDS
2. rhua update
[root@domU-12-31-39-13-DD-C2 os]# rm -rf zsh-
[root@domU-12-31-39-13-DD-C2 os]# rm -rf zsh-*
[root@domU-12-31-39-01-64-52 os]# rhua update
Synchronizing channel list to base [/mnt/content]
Synchronizing channel [rhel-i386-server-5] and creating repo
Synchronized channel [rhel-i386-server-5] in  seconds
Synchronizing channel [rhel-x86_64-server-5] and creating repo
Synchronized channel [rhel-x86_64-server-5] in  seconds
Synchronized  packages
No new packages, skipping synchronization to CDS instances step
pretty sure that is how its designed..
The Admin can run rhua refresh to resolve the issue.
Jason, what do you think?
Yup, Wes is right. On an update, we only synchronize the packages over to the CDS if new ones were downloaded from grinder. If grinder reports no new packages, we don't do the sync.
Running 'rhua refresh' will explicitly trigger a package sync with the CDS.
so there is basically no difference between rhua sync and rhua update ?
I thought rhua update is supposed to work like rhua start : which means it will sync missing package to rhua and CDS.
And after rhua start if i have to sync packages to both CDS and rhua i got to either run :
1) rhua sync and rhua refresh or
2) rhua start again
rhua refresh definitely fixes the problem though.
rhua refresh ONLY transfers rpms from the rhua to the cds's.
rhua sync, sync's packages from the hosted source. IF new or updated rpms are found THEN a rhua refresh is called to resync everything to the cds's.
The thought here is that under normal conditions the only time you need to sync packages to the cds is when there is new or updated content.
closing the bug.
moving to release pending
closing out, product released