Red Hat Bugzilla – Bug 838669
Document how to update to CloudForms-1.0.1 ... if $releasever is set
Last modified: 2013-09-02 03:02:55 EDT
Description of problem: With the method in which we are publishing CloudForms to the CDN, if a custom has chosen to lock-in a specific release of RHEL using the $releasever variable (/etc/yum/vars/releasever), they will not see any CloudForms package updates. CloudForms-1.0 shipped to * /content/dist/rhel/server/6/6.2/x86_64/cf-ce/ * /content/dist/rhel/server/6/6.2/x86_64/cf-se/ CloudForms-1.0.1 is shipping to * /content/dist/rhel/server/6/6.3/x86_64/cf-ce/ * /content/dist/rhel/server/6/6.3/x86_64/cf-se/ If a customer has set $releasever == 6.2 ... they will not be able to update to CloudForms-1.0.1 We should add a release note (or kbase) describing how to detect whether $releasever is set, and how clear the $releasever value.
Let's get a summary of this in Technical Notes.
The more I think about this, I'm not so certain it's CloudForms responsibility to document how to unset $releasever. Perhaps this should live alongside the documentation guiding customers in setting releasever=$something. https://access.redhat.com/knowledge/docs/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/sec-Using_Yum_Variables.html Feel free to correct me, but I'm now leaning towards CLOSED WONTFIX. Bkearney: you're familiar with the usage of $releasever, what do you think?
I'm leaning towards CLOSED WONTFIX until we have a firm course of action.
I propose we add a note to users in the existing upgrade sections. For example... System Engine - https://access.redhat.com/knowledge/docs/en-US/CloudForms/1.0/html/Release_Notes/chap-Release_Notes-Updates.html#chap-Release_Notes-Updates-System_Engine Cloud Engine - https://access.redhat.com/knowledge/docs/en-US/CloudForms/1.0/html/Release_Notes/chap-Release_Notes-Updates-Cloud_Engine.html I would like to request help from the Docs team in adding a new section similar in form to the following. > == Update Repository Definitions (optional) == > > For customers that choose to bind their systems to a particular Red Hat Enterprise repository using the 'yum' $releasever variable [1], additional steps may be required to properly update your system. > > First, determine the currently installed Red Hat Enterprise Linux release using the following command: > $ rpm -q --whatprovides --qf "%{version}\n" system-release > > Next, using the following command, determine what the 'yum' command will use when updating the your installed Red Hat Enterprise Linux system. > > $ python -c "import yum; yb=yum.YumBase() ; yb.conf ; print yb.yumvar['releasever']" > > If the two values differ, your system may not properly receive CloudForms package updates. In order to properly update your CloudForms installation, you must clear, or reset, and custom values for the yum '$releasever' variable. For more information on setting, or removing, yum variables refer to [1]. > > [1] https://access.redhat.com/knowledge/docs/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/sec-Using_Yum_Variables.html