<div dir="ltr"><div><div><div><div>Hi Matthew, good morning<br><br></div>Thanks for your reply, in fact this is what I normally recommend and do, but not automatically, in my point of view the manager have to check if there are new packages in base channel (erratas), but accessing by cloned channel and adding erratas (first in dev channels, tests and after that, homolog and production channel).<br>
<br></div>The idea of this post is really hear our friends about what normally they do when talking about freezed channel and erratas sync. We have different kind of clients with different scenarios, so we have clients where they don't do update, still in the same version without erratas, other apply only security packages, other only fix packages when there are know bugs ..., so I would like to share this knowledge.<br>
<br></div>Thanks for your contribution.<br><br></div>B' Regards<br>Waldirio<br></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, Jul 25, 2014 at 2:31 PM, Matthew Madey <span dir="ltr"><<a href="mailto:mattmadey@gmail.com" target="_blank">mattmadey@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">In a previous job, we had a requirement to keep all clients at RHEL5.8. To do this we created a static RHEL5 channel with nothing subscribed to it, and it was sync'd nightly. Then we created clone channels using spacewalk-clone-by-date. Once the clone channel was created.. we refreshed it daily with only security errata using the -o option for spacewalk-clone-by-date. You can also use --blacklist to exclude particular packages. I think that might be your best option, as I assume you want to continue getting new security Errata's, but prevent upgrading to the next minor version. </div>
<div class="gmail_extra"><br><br><div class="gmail_quote"><div><div class="h5">On Wed, Jul 23, 2014 at 9:55 PM, Waldirio Manhães Pinheiro <span dir="ltr"><<a href="mailto:waldirio@gmail.com" target="_blank">waldirio@gmail.com</a>></span> wrote:<br>
</div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="h5"><div dir="ltr"><div><div><div><div><div>Hello friends, good morning<br><br></div>I've one doubt and would like to share with you to get feedback about what should be a best practice about it. For any reasons, in different environments we have to create a freeze channel, for example RHEL or CentOS 6.2.<br>
<br></div>What do you recommend !?, Create a freezed channel using a release date from specific version or use a date before the next release ?! Let'me explain with example, the version of RHEL 6.2 was delivered in 2011-12-06 (OS without erratas) and the version 6.2 complete with all erratas was in 2012-06-19 (one day before next version).<br>
<br><br><table><thead><tr><th>Release/Update</th>
<th>General Availability Date</th>
<th>redhat-release Errata Date*</th>
<th>Kernel Version</th>
</tr>
</thead>
<tbody>
<tr>
<td>RHEL 6 Update 6</td>
<td>TBA</td>
<td>TBA<br></td>
<td>TBA</td>
</tr>
<tr>
<td>RHEL 6 Update 5</td>
<td>2013-11-21</td>
<td>2013-11-20 <a href="https://rhn.redhat.com/errata/RHSA-2013-1645.html" target="_blank">RHSA-2013:1645-2</a></td>
<td>2.6.32-431</td>
</tr>
<tr>
<td>RHEL 6 Update 4</td>
<td>2013-02-21</td>
<td>2013-02-21 <a href="https://rhn.redhat.com/errata/RHSA-2013-0496.html" target="_blank">RHSA-2013-0496</a></td>
<td>2.6.32-358</td>
</tr>
<tr>
<td>RHEL 6 Update 3</td>
<td>2012-06-20</td>
<td>2012-06-19 <a href="http://rhn.redhat.com/errata/RHSA-2012-0862.html" target="_blank">RHSA-2012-0862</a></td>
<td>2.6.32-279</td>
</tr>
<tr>
<td>RHEL 6 Update 2</td>
<td>2011-12-06</td>
<td>2011-12-06 <a href="http://rhn.redhat.com/errata/RHEA-2011-1743.html" target="_blank">RHEA-2011:1743</a></td>
<td>2.6.32-220</td>
</tr>
<tr>
<td>RHEL 6 Update 1</td>
<td>2011-05-19</td>
<td>2011-05-19 <a href="http://rhn.redhat.com/errata/RHEA-2011-0540.html" target="_blank">RHEA-2011:0540</a></td>
<td>2.6.32-131.0.15</td>
</tr>
<tr>
<td>RHEL 6 GA</td>
<td>2010-11-09</td>
<td>-</td>
<td>2.6.32-71</td></tr></tbody></table><br></div><div></div>Link to check dates - <a href="https://access.redhat.com/articles/3078" target="_blank">https://access.redhat.com/articles/3078</a><br><br></div>What do you recommend about this procedure ?!<br>
<br></div>Appreciate your comments.<span><font color="#888888"><br><div><div><div><br clear="all"><div><div><div><div><br>-- <br><div>______________<br>B'Regards<br>Waldirio<br>msn: <a href="mailto:waldirio@gmail.com" target="_blank">waldirio@gmail.com</a><br>
Skype: waldirio<br>Site: <a href="http://www.waldirio.com.br" target="_blank">www.waldirio.com.br</a><br>Blog: <a href="http://blog.waldirio.com.br" target="_blank">blog.waldirio.com.br</a></div>
<div>LinkedIn: <a href="http://br.linkedin.com/pub/waldirio-pinheiro/22/b21/646" target="_blank">http://br.linkedin.com/pub/waldirio-pinheiro/22/b21/646</a><br>PGP: <a href="http://www.waldirio.com.br/public.html" target="_blank">www.waldirio.com.br/public.html</a></div>
</div></div></div></div></div></div></div></font></span></div>
<br></div></div>_______________________________________________<br>
Spacewalk-list mailing list<br>
<a href="mailto:Spacewalk-list@redhat.com" target="_blank">Spacewalk-list@redhat.com</a><br>
<a href="https://www.redhat.com/mailman/listinfo/spacewalk-list" target="_blank">https://www.redhat.com/mailman/listinfo/spacewalk-list</a><br></blockquote></div><br></div>
<br>_______________________________________________<br>
Spacewalk-list mailing list<br>
<a href="mailto:Spacewalk-list@redhat.com">Spacewalk-list@redhat.com</a><br>
<a href="https://www.redhat.com/mailman/listinfo/spacewalk-list" target="_blank">https://www.redhat.com/mailman/listinfo/spacewalk-list</a><br></blockquote></div><br><br clear="all"><br>-- <br><div>______________<br>Atenciosamente<br>
Waldirio<br>msn: <a href="mailto:waldirio@gmail.com" target="_blank">waldirio@gmail.com</a><br>Skype: waldirio<br>Site: <a href="http://www.waldirio.com.br" target="_blank">www.waldirio.com.br</a><br>Blog: <a href="http://blog.waldirio.com.br" target="_blank">blog.waldirio.com.br</a></div>
<div>LinkedIn: <a href="http://br.linkedin.com/pub/waldirio-pinheiro/22/b21/646" target="_blank">http://br.linkedin.com/pub/waldirio-pinheiro/22/b21/646</a><br>PGP: <a href="http://www.waldirio.com.br/public.html" target="_blank">www.waldirio.com.br/public.html</a></div>
</div>