If an agent was installed on the same machine as a JON Server, make it clear in docs that people have to shutdown that agent before running rhqctl to upgrade. See bug #1013674 and bug #1012289 for issues where people were confused about that.
Seems that both of these referenced bug were identified by our own QA process. I am not sure documentation is the best way to "identify" bugs in our products. I have re-opened bug 1012289 to track this as a known issue for 3.2. At this point, I do not believe our install/upgrade documentation should change. Installation and upgrade of an existing agent should not be impacted by the installation/upgrade of the server outside of the standard agent auto-upgrade that is performed.
(In reply to Larry O'Leary from comment #1) > Seems that both of these referenced bug were identified by our own QA > process. I am not sure documentation is the best way to "identify" bugs in > our products. > > I have re-opened bug 1012289 to track this as a known issue for 3.2. At this > point, I do not believe our install/upgrade documentation should change. > Installation and upgrade of an existing agent should not be impacted by the > installation/upgrade of the server outside of the standard agent > auto-upgrade that is performed. For sure, our installation procedures of an agent (on a JON Server machine) is different now. We require rhqctl. If you have an agent-only machine, installation procedures are the same.
Moving to ER05 as missed the cutoff for ER04.
Mass closure of bugs modified in 2013. All of these are in the currently-published docs.