Red Hat Bugzilla – Bug 983243
Remove packages orphaned by the upgrade
Last modified: 2017-03-08 13:12 EST
Description of problem:
The SRT reached out to me and mentioned that they would like us to remove packages that were shipped prior to 1.2 that are orphaned by the upgrade. rubygem-rails-3.0.13-1.el6op.noarch is one example but I'm certain there are others.
Meaning provide scripts to remove them from the customers' systems?
Well, add v1 cartridges...
I got started on scripts for cleaning up a number of things after the upgrade, would be happy to provide if I don't work this bug.
Can this be done in a specfile? Will look into this.
I think the logic needs to live in ose-upgrade somewhere. We don't want a given ose-upgrade step to be interactive but we should only remove packages that are no longer supported in our channels.
Created attachment 774401 [details]
List of removed packages
Attaches is a list of binary packages that exist in 1.0/1.1 OSE channels, but not in 1.2 channels. Separate list for each OSE channel (infrastructure, node, client, jbosseap). This has not been pruned to remove any that are obsoleted properly (if any).
rubygem-crack and ruby193-rubygem-crack were shipped in 1.1 but not in 1.2. They can safely be removed if no other packages on a user's system requires them.
Moving this to the next major release as a reminder.
OpenShift Enterprise v2 has officially reached EoL. This product is no longer supported and bugs will be closed.
Please look into the replacement enterprise-grade container option, OpenShift Container Platform v3. https://www.openshift.com/container-platform/
More information can be found here: https://access.redhat.com/support/policy/updates/openshift/