Duh. I forgot to clean the yum cache on the consumer. That took care of it. Now... off to get some coffee to kickstart the brain. Thanks again.
Joel ________________________________ From: Pradeep Kilambi [mailto:[email protected]] Sent: Friday, January 20, 2012 9:24 AM To: Golden, Joel Cc: [email protected] Subject: Re: [Pulp-list] package filer question hmm i would have expected the metadata to refresh any filtered packages. Try these, * Clear your yum cache on the consumer and try yum check-update? * Also check your /var/lib/pulp/repos/rh5-prd/*.rpm and make sure there is no mysql pkg symlinked here. If there is, then probably blacklist filter is not working as expected to being with. ~ Prad ________________________________ From: "Joel Golden" <[email protected]> To: "Pradeep Kilambi" <[email protected]> Cc: [email protected] Sent: Friday, January 20, 2012 11:15:45 AM Subject: RE: [Pulp-list] package filer question By "metadata update" do you mean execute the generate_metadata on the cloned repo after the clone process is complete? If so, that isn't clearing the package from the cloned repo's package set. Joel ________________________________ From: Pradeep Kilambi [mailto:[email protected]] Sent: Friday, January 20, 2012 9:05 AM To: Golden, Joel Cc: [email protected] Subject: Re: [Pulp-list] package filer question I agree Joel. For now we'll go ahead and do the metadata update until we figure out an efficient way of updating package metadata for a subset of packages. The side effect of this change would be your clones might run a bit longer. I opened a bug for this issue here https://bugzilla.redhat.com/show_bug.cgi?id=783485 . i'll try to look into it soon. ~ Prad ________________________________ From: "Joel Golden" <[email protected]> To: "Pradeep Kilambi" <[email protected]> Cc: [email protected] Sent: Friday, January 20, 2012 11:01:28 AM Subject: RE: [Pulp-list] package filer question Prad, After I deleted the master and clone repos and recreated them, that is the result I get. I think I had some corruption earlier. It would be nice to see a repo generation for clones. One, I'm very apprehensive to schedule a full package set update in production when yum update shows it's going to update packages we want locked. Two, it can be time consuming to parse through a package update log for a few hundred machines when it contains false positives. Thoughts? Thank you, Joel ________________________________ From: Pradeep Kilambi [mailto:[email protected]] Sent: Friday, January 20, 2012 8:14 AM To: Golden, Joel Cc: [email protected] Subject: Re: [Pulp-list] package filer question Hey Joel: This is what I think is happening, Your original repo has no filter, it still has a reference to the package. A clone operation does not regenerate the metadata and it reuses the parents metadata and that probably why you still see that via yum check-update. The package is still blacklisted, and will not be served. Try installing the update and see if pulp is serving the package. You should get a 404. We could trigger a repo generation in case a clone operation uses filters. May be thats the solution to keep the filesystem + db in sync with metadata in case of filters. The reason we dont currently generate metadata is to keep the clone as close to the parent as possible and also to make the clone fast(as reop generation can be expensive) ~ Prad ________________________________ From: "Joel Golden" <[email protected]> To: [email protected] Sent: Thursday, January 19, 2012 4:45:59 PM Subject: [Pulp-list] package filer question I'm having an issue with a repo filter carrying over to the consumer. This repo is a clone of rh5-live, without the filter. I've verified the packages have been removed but they still show up under yum check-update and are available via yumdownloader from a client bound to the rh5-prd repo. And the consumer shows the number of packages available higher than the number of packages in the rh5-prd repo. Any ideas? Id rh5-prd Name rh5-prd Repo URL https://uxspulpplv1/pulp/repos/rh5-prd/ Feed URL file:///var/lib/pulp//repos/redhat/updates/rhel-5.2-server-x86_64/latest/rhel-x86_64-server-5 Feed Type local Content Type yum Feed Certs CA:No Cert:No Consumer Certs CA:No Cert:No Architecture x86_64 Sync Schedule None Packages 4854 Files 0 Distributions None Publish True Clones [] Groups [u'prd'] Filters ['mysql-blacklist'] Notes {} Preserve Metadata False Checksum Type sha256 Id rh5-live Name rh5-live Repo URL https://uxspulpplv1/pulp/repos/redhat/updates/rhel-5.2-server-x86_64/latest/rhel-x86_64-server-5/ Feed URL http://rhelrepo.twtelecom.com/redhat/updates/rhel-5.2-server-x86_64/latest/rhel-x86_64-server-5/ Feed Type remote Content Type yum Feed Certs CA:No Cert:No Consumer Certs CA:No Cert:No Architecture x86_64 Sync Schedule None Packages 4904 Files 0 Distributions None Publish True Clones [u'rh5-tst', u'rh5-prd', u'rh5-dev'] Groups None Filters [] Notes {} Preserve Metadata False Checksum Type sha256 pulp-admin repo content --id rh5-prd |gawk '/^mysql|^MySQL/' reports nothing. pulp-admin filter create --id mysql-blacklist --type blacklist --description "mysql and MySQL package filter" -p "mysql-*" -p "MySQL-*" pulp-admin filter info --id mysql-blacklist Id : mysql-blacklist Description : mysql and MySQL package filter Type : blacklist Package List : ['mysql-*', 'MySQL-*'] pulp-admin repo generate_metadata --id rh5-prd from the consumer: repo id repo name status repos-pulp-pulp-5Server-x86_64 repos-pulp-pulp-5Server-x86_64 enabled: 17 rh5-prd rh5-prd enabled: 4,905 repolist: 4,922 Best Regards, Joel Golden, RHCE TW Telecom Unix Support / Senior Systems Administrator ------------- The content contained in this electronic message is not intended to constitute formation of a contract binding tw telecom. tw telecom will be contractually bound only upon execution, by an authorized officer, of a contract including agreed terms and conditions or by express application of its tariffs. This message is intended only for the use of the individual or entity to which it is addressed. If the reader of this message is not the intended recipient, or the employee or agent responsible for delivering the message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the sender of this E-Mail or by telephone. _______________________________________________ Pulp-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/pulp-list
_______________________________________________ Pulp-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/pulp-list
