Bad experience with current RHEL 6 incremental set, Disconnected Satellite, for incremental channel set -> RHEL 6 (x86_64) + EUS + AUS + RHN Proxy/Tools + Supplementary (Incremental 2015-10-10:2016-05-11)

Latest response

We have noted a severe issue several environments we have with incremental channel RHEL 6 (x86_64) + EUS + AUS + RHN Proxy/Tools + Supplementary (Incremental 2015-10-10:2016-05-11) , which interestingly was issued the same day the new RHEL 6 base channels were concurrently were updated. All the systems we have applied this incremental channel (on numerous satellite servers) are now rendered unbootable and we are diagnosing them. I'd recommend anyone with a disconnected satellite server use caution with patching and use a small subset of systems before wide dispersal. Hopefully it is just us, and not widespread.

The Base channel set of RHEL 6 (x86_64) + EUS + AUS + RHN Proxy/Tools + Supplementary (Base 2016-05-11) is of course separate/apart from the above, we plan on testing with a small subset of servers.

Responses

Oddly, I can't change the original post I made that started this thread.

UPDATE: This specific incremental channel is built upon base channel set 2015-10-10, and this incremental channel takes you to RHEL 6.8 which an incremental channel should ===never=== do.

This occurred previously with the release of RHEL 6.7 when incremental channels erroneously took client systems from RHEL 6.6 to RHEL 6.7, and I documented this this linked discussion https://access.redhat.com/discussions/1597433 and a case with Red Hat.

IMPORTANT --> No incremental channel should take a client system past the minor release of it's parent base channel.

This has occurred twice now, see the discussion in the last paragraph.

Thank you for the heads up.

Ryan Holt

Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.