[Pulp-list] RHEL repo version lock using pulp

Fri Jan 11 20:26:04 UTC 2019

Fair enough but you have to already be using EUS to take advantage of that.  What I described is the Red Hat "approved" method of version pinning when EUS is not in use.  Even Kodiak's suggestion will result in a repo that stopped receiving updates on 04/09/2018 unless you're using EUS and syncing the RHEL 7.4 EUS repo.
Happy to be 100% wrong here but I have yet to see to it otherwise or suggested otherwise when I spoke with Red Hat about the exact subject.
-------- Original message --------From: Ben Stanley <ben.stanley at gmail.com> Date: 1/11/19  2:47 PM  (GMT-05:00) To: "aaron.t.wyllie" <aaron.t.wyllie at gmail.com>, Kodiak Firesmith <kfiresmith at gmail.com>, Venkataramana Bora <venkbora at in.ibm.com> Cc: Donal Keane <donal.keane at ie.ibm.com>, pulp-list <pulp-list at redhat.com> Subject: Re: [Pulp-list] RHEL repo version lock using pulp 

This approach of locking the repo before the new release will fail to get updates for the old version. 
I advise to use Kodiak's method of examining the entitlements and finding the proper version locked repo names. Then you will receive the proper updates for each version. 

On 12 January 2019 4:09:49 am "aaron.t.wyllie" <aaron.t.wyllie at gmail.com> wrote:

Replied earlier from my work address but I think it may be blocked.  Anyways ...
You could do what Kodiak suggests but that will involve syncing another set of repositories.
An alternative would be to create a content view pinned to the day before RHEL 7.5 was released; 04/09/2018 as RHEL 7.5 was released 04/10/2018.  Do that for all required RHEL 7 repositories and add them to a CCV and call it done.
You could also look at subscription-manager on the managed client-side and configure the pin-to-release to 7.4 and see how that works.  I've never done that but mainly because I always worry someone might come behind me and unset it ...
Aaron Wyllieaaron.t.wyllie at gmail.com+1.904.422.1545 (M)
-------- Original message --------From: Kodiak Firesmith <kfiresmith at gmail.com> Date: 1/11/19  11:41 AM  (GMT-05:00) To: Venkataramana Bora <venkbora at in.ibm.com> Cc: Donal Keane <donal.keane at ie.ibm.com>, pulp-list <pulp-list at redhat.com> Subject: Re: [Pulp-list] RHEL repo version lock using pulp 
To lock to 7.4, you'd want to sync 7.4 CDN channels to dedicated 7.4 Pulp repos.  Use 'rct cat-cert' to look for 7.4 specific channels to mirror. - Kodiak
On Fri, Jan 11, 2019 at 11:02 AM Venkataramana Bora <venkbora at in.ibm.com> wrote:
Hi Team, would like to know, on Pulp servers is there any possibility to create  a specific version (say RHEL 7.4) only repository  using  cdn.redhat.com feed? Right now  we are using below Redhat 7 feeds our pulp servers , but that is updating to latest RHEL7.6 from 7.4  We have a requirement now where we need to have RHEL7.4 repo that should not be updated to latest RHEL7.x  but we like to have latest RHEL7.4 security updates only using a that Pulp repo. Kindly please let us know if there is any possibility of specific version lock pulp repo or not. Thanks a lot in advance !

Pulp_repo rhel-7-server-rpms-x86_64 feed: 'https://cdn.redhat.com/content/dist/rhel/server/7/7Server/x86_64/os'.
pulp_repo rhel-7-server-extras-rpms-x86_64 feed: 'https://cdn.redhat.com/content/dist/rhel/server/7/7Server/x86_64/extras/os'
pulp_repo rhel-7-server-optional-rpms-x86_64 feed:'https://cdn.redhat.com/content/dist/rhel/server/7/7Server/x86_64/optional/os'

Our Pulp slave servers are with version pulp-server-2.11.2-1.el6 and  master Pulp server is 2.16.

Sincerely,
Venkataramana Bora
IBM Visakha Hills
Visakhapatnam – 530 045, India

_______________________________________________

Pulp-list mailing list

Pulp-list at redhat.com

https://www.redhat.com/mailman/listinfo/pulp-list

_______________________________________________
Pulp-list mailing list
Pulp-list at redhat.com
https://www.redhat.com/mailman/listinfo/pulp-list

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/pulp-list/attachments/20190111/89af8e14/attachment.htm>