<div dir="ltr">Hrm - I may be insulated from the worst of Red Hat's volume licensing due to being at an EDU, but I thought all paid customers could pin to a minor release for the first 24 months after release of the minor version...<div><br></div></div><br><div class="gmail_quote"><div dir="ltr">On Fri, Jan 11, 2019 at 3:26 PM aaron.t.wyllie <<a href="mailto:aaron.t.wyllie@gmail.com">aaron.t.wyllie@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div><div>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.</div><div><br></div><div>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.</div><div><br></div><div style="font-size:100%;color:rgb(0,0,0)"><div>-------- Original message --------</div><div>From: Ben Stanley <<a href="mailto:ben.stanley@gmail.com" target="_blank">ben.stanley@gmail.com</a>> </div><div>Date: 1/11/19 2:47 PM (GMT-05:00) </div><div>To: "aaron.t.wyllie" <<a href="mailto:aaron.t.wyllie@gmail.com" target="_blank">aaron.t.wyllie@gmail.com</a>>, Kodiak Firesmith <<a href="mailto:kfiresmith@gmail.com" target="_blank">kfiresmith@gmail.com</a>>, Venkataramana Bora <<a href="mailto:venkbora@in.ibm.com" target="_blank">venkbora@in.ibm.com</a>> </div><div>Cc: Donal Keane <<a href="mailto:donal.keane@ie.ibm.com" target="_blank">donal.keane@ie.ibm.com</a>>, pulp-list <<a href="mailto:pulp-list@redhat.com" target="_blank">pulp-list@redhat.com</a>> </div><div>Subject: Re: [Pulp-list] RHEL repo version lock using pulp </div><div><br></div></div>
<div>
<div dir="auto"><div dir="auto" style="font-family:sans-serif">This approach of locking the repo before the new release will fail to get updates for the old version. </div><div dir="auto" style="font-family:sans-serif"><br></div><div dir="auto" style="font-family:sans-serif">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. </div></div><div dir="auto"><br></div>
<div id="gmail-m_-5545956188545548002aqm-original" style="color:black">
<div class="gmail-m_-5545956188545548002aqm-original-body"><div style="color:black">
<p style="color:black;font-size:10pt;font-family:sans-serif;margin:8pt 0px">On 12 January 2019 4:09:49 am "aaron.t.wyllie" <<a href="mailto:aaron.t.wyllie@gmail.com" target="_blank">aaron.t.wyllie@gmail.com</a>> wrote:</p>
<blockquote type="cite" class="gmail_quote" style="margin:0px 0px 0px 0.75ex;border-left:1px solid rgb(128,128,128);padding-left:0.75ex">
<div>Replied earlier from my work address but I think it may be blocked. Anyways ...</div><div><br></div><div>You could do what Kodiak suggests but that will involve syncing another set of repositories.</div><div><br></div><div>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.</div><div><br></div><div>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 ...</div><div><br></div><div id="gmail-m_-5545956188545548002composer_signature"><div style="font-size:85%;color:rgb(87,87,87)">Aaron Wyllie</div><div style="font-size:85%;color:rgb(87,87,87)"><a href="mailto:aaron.t.wyllie@gmail.com" target="_blank">aaron.t.wyllie@gmail.com</a></div><div style="font-size:85%;color:rgb(87,87,87)">+1.904.422.1545 (M)</div></div><div><br></div><div style="font-size:100%;color:rgb(0,0,0)"><div>-------- Original message --------</div><div>From: Kodiak Firesmith <<a href="mailto:kfiresmith@gmail.com" target="_blank">kfiresmith@gmail.com</a>> </div><div>Date: 1/11/19 11:41 AM (GMT-05:00) </div><div>To: Venkataramana Bora <<a href="mailto:venkbora@in.ibm.com" target="_blank">venkbora@in.ibm.com</a>> </div><div>Cc: Donal Keane <<a href="mailto:donal.keane@ie.ibm.com" target="_blank">donal.keane@ie.ibm.com</a>>, pulp-list <<a href="mailto:pulp-list@redhat.com" target="_blank">pulp-list@redhat.com</a>> </div><div>Subject: Re: [Pulp-list] RHEL repo version lock using pulp </div><div><br></div></div><div dir="ltr">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.<div> - Kodiak</div></div><br><div class="gmail_quote"><div dir="ltr">On Fri, Jan 11, 2019 at 11:02 AM Venkataramana Bora <<a href="mailto:venkbora@in.ibm.com" target="_blank">venkbora@in.ibm.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div><p>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 <a href="http://cdn.redhat.com" target="_blank">cdn.redhat.com</a> 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 !<br><br>Pulp_repo rhel-7-server-rpms-x86_64 feed: '<a href="https://cdn.redhat.com/content/dist/rhel/server/7/7Server/x86_64/os" target="_blank">https://cdn.redhat.com/content/dist/rhel/server/7/7Server/x86_64/os</a>'.<br>pulp_repo rhel-7-server-extras-rpms-x86_64 feed: <a href="https://cdn.redhat.com/content/dist/rhel/server/7/7Server/x86_64/extras/os'" target="_blank">'https://cdn.redhat.com/content/dist/rhel/server/7/7Server/x86_64/extras/os'</a><br>pulp_repo rhel-7-server-optional-rpms-x86_64 feed:'<a href="https://cdn.redhat.com/content/dist/rhel/server/7/7Server/x86_64/optional/os" target="_blank">https://cdn.redhat.com/content/dist/rhel/server/7/7Server/x86_64/optional/os</a>'<br><br><br>Our Pulp slave servers are with version pulp-server-2.11.2-1.el6 and master Pulp server is 2.16.<br><br><br><br><br><span style="font-size:10pt">Sincerely,</span><br><span style="font-size:10pt">Venkataramana Bora</span><br><span style="font-size:10pt">IBM Visakha Hills</span><br><span style="font-size:10pt">Visakhapatnam – 530 045, India</span><br><br>
</p></div>
_______________________________________________<br>
Pulp-list mailing list<br>
<a href="mailto:Pulp-list@redhat.com" target="_blank">Pulp-list@redhat.com</a><br>
<a href="https://www.redhat.com/mailman/listinfo/pulp-list" rel="noreferrer" target="_blank">https://www.redhat.com/mailman/listinfo/pulp-list</a></blockquote></div>
<div>_______________________________________________</div>
<div>Pulp-list mailing list</div>
<div><a class="gmail-m_-5545956188545548002aqm-autolink gmail-m_-5545956188545548002aqm-autowrap" href="mailto:Pulp-list%40redhat.com" target="_blank">Pulp-list@redhat.com</a></div>
<div><a class="gmail-m_-5545956188545548002aqm-autolink gmail-m_-5545956188545548002aqm-autowrap" href="https://www.redhat.com/mailman/listinfo/pulp-list" target="_blank">https://www.redhat.com/mailman/listinfo/pulp-list</a></div></blockquote>
</div>
</div>
</div><div dir="auto"><br></div>
</div></div></blockquote></div>