Bug 743101

As this is a doc bug, I feel like I need to point out that I meant invasive instead of evasive above.  That is all :).

Here's a draft of the update instructions:

RHUI can be updated by configuring it to use a repository that the RHUI itself
is providing.  rhui-manager can be used to create the repository for the RHUI
product, then generate an entitlement certificate and client configuration
rpm.  That client configuration rpm can then be installed on the RHUA and CDS
instances which will make it so that they can "yum update" and pull down the
latest updates.

1.  First, you need to make sure that the RHUI repositories have been added to
your RHUA using rhui-manager.  The RHUI repository is a Red Hat provided
repository, and the procedure for Adding Red Hat Repositories is covered in
section 5.3.  If you used the "All in Certificate" method, the repository
should already be added.  If not, use the "By Product" method and add the
product called "Red Hat Update Infrastructure 2.0 (RPMs)" and optionally "Red
Hat Update Infrastructure 2.0 (SRPMs)".  Once these product(s) are deployed on
the RHUA, you should have the following repos defined, which you can verify by
listing the repositories using rhui-manager:

  Red Hat Update Infrastructure 2.0 (RPMs) (6Server-x86_64)
  Red Hat Update Infrastructure 2.0 (RPMs) (6.0-i386)
  Red Hat Update Infrastructure 2.0 (RPMs) (6.1-i386)
  Red Hat Update Infrastructure 2.0 (RPMs) (6.1-x86_64)
  Red Hat Update Infrastructure 2.0 (RPMs) (6Server-i386)
  Red Hat Update Infrastructure 2.0 (RPMs) (6.0-x86_64)
  Red Hat Update Infrastructure 2.0 (SRPMS) (6.1-i386)
  Red Hat Update Infrastructure 2.0 (SRPMS) (6.0-i386)
  Red Hat Update Infrastructure 2.0 (SRPMS) (6.0-x86_64)
  Red Hat Update Infrastructure 2.0 (SRPMS) (6Server-x86_64)
  Red Hat Update Infrastructure 2.0 (SRPMS) (6Server-i386)
  Red Hat Update Infrastructure 2.0 (SRPMS) (6.1-x86_64)

2.  Make sure that these repositories have all been synchronized successfully.
Refer to section 9.4 on how to trigger a repository synchronization.

3.  Generate an entitlement certificate for these repositories.  You can create
just a single entitlement certificate that is used for all the RHUI
repositories.  Refer to section 7.2 on generating entitlement certificates.

4.  Create a client configuration rpm that that uses the entitlement
certificate created in the previous step.  Refer to section 7.2 on creating
client configuration rpm's.   When you name the client configuration rpm, use
a name that will let you know it's for providing rhui updates, such as
rhui-update.

5.  Once the client configuration rpm has been generated, install it on the
RHUA and each CDS that needs to be updated.  The rpm will provide a yum
repository configuration for a repository called rhui-rhui-2.0.  You can then
run "yum update" to pull down updates for all enabled repositories on the
system, or "yum --disablerepo=* --enablerepo=rhui-rhui-2.0 update" to update
only the RHUI software on the system.

6.  Once the update has completed, restart the necessary service.
On the RHUA run:
service pulp-server restart
On each CDS run:
service pulp-cds restart

forgot you can't edit bugzilla comments...

Step 2 should also say:

You need to do a CDS synchronization once the repository synchronizations have completed successfully.  Refer to section 9.5 on triggering a CDS synchronization.

Added a new chapter in the Operations part, and included a link to the new chapter in the Installation part. Please review on the stage.

Revision 2-9

LKB

Verified in stage, a new chapter has been added:

Chapter 4. Updating Red Hat Update Infrastructure at

http://documentation-stage.bne.redhat.com/docs/en-US/Red_Hat_Update_Infrastructure/2.0/html/Installation_Guide/chap-Installation_Guide-Updating_RHUI.html

Everything looks good except statement at step4:

>>Synchronize the CDS instances. Use the procedure in Procedure 10.5, “Trigger a >>CDS Synchronization”. 

I think this statement should be like "Synchronize the CDS instances once the repository synchronizations have completed successfully"

or we can add a note like "Trigger the CDS sync once the repo sync have finished successfully"

(In reply to comment #6)
> Verified in stage, a new chapter has been added:
> 
> Chapter 4. Updating Red Hat Update Infrastructure at
> 
> http://documentation-stage.bne.redhat.com/docs/en-US/Red_Hat_Update_Infrastructure/2.0/html/Installation_Guide/chap-Installation_Guide-Updating_RHUI.html
> 
> Everything looks good except statement at step4:
> 
> >>Synchronize the CDS instances. Use the procedure in Procedure 10.5, “Trigger a >>CDS Synchronization”. 
> 
> I think this statement should be like "Synchronize the CDS instances once the
> repository synchronizations have completed successfully"
> 
> or we can add a note like "Trigger the CDS sync once the repo sync have
> finished successfully"

<step>
	<para>
		Wait for the repository synchronization to complete, and then synchronize the CDS instances. Use the procedure in <xref linkend="proc-Installation_Guide-Status_and_Scheduling-Trigger_a_CDS_Synchronization" />.
	</para>
</step>

Revision 2-10

LKB

Revision 2-12 of this document is now publicly available at:
http://docs.redhat.com/docs/en-US/Red_Hat_Update_Infrastructure/2.0/html/Installation_Guide/index.html

Please raise a new bug for any further issues.

LKB