Bug 1322545

This will not work.  rhn-channel was used to change the repos enabled, but that requires user/password.

Dan we need to document this before the upgrade init step in the doc.  Do you want a separate doc bug? or is this sufficient?

The user will need to provide a new activation key and possibly the server url depending on how they configured their overcloud at deployment.

If they provided cli options for satellite 5, they will need to add an environment file like this using a new activation key with OSP8 keys:

parameter_defaults:
  rhel_reg_sat_url: https://<satellite hostname>
  rhel_reg_activation_key: <OSP8_activation_key>

They could also provide something like this:

parameter_defaults:
  UpgradeInitCommand: |
    rhn-channel --remove --channel=rhel-x86_64-server-7-ost-7 --channel=rhel-x86_64-server-7-ost-7-director --username=<> --password=<>
    rhn-channel --add --channel=rhel-x86_64-server-7-ost-8 --channel=rhel-x86_64-server-7-ost-8-director --username=<> --password=<>

I neglected the "if they passed and env file with sat5 information" possibility:

If that's the case, they need to update that file to provide an OSP8 activation key instead of the OSP 7 on used previously.

Verified:
Environment:
openstack-tripleo-heat-templates-0.8.14-9.el7ost.noarch

The repos on the overcloud nodes switched to 8.0

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2016-0653.html

Hi Mike,

I've added a note in the pre-upgrade notes:
https://access.redhat.com/documentation/en/red-hat-openstack-platform/8/director-installation-and-usage/chapter-10-upgrading-the-environment


The text reads:

If using an environment file for Satellite registration (see Section 6.12, “Registering the Overcloud”), make sure to update the following parameters in the environment file:

* rhel_reg_repos - Repositories to enable for your Overcloud, including the new Red Hat OpenStack Platform 8 repositories.

* rhel_reg_activation_key - The new activation key for your Red Hat OpenStack Platform 8 repositories.

* rhel_reg_sat_repo - A new parameter that defines the repository containing Red Hat Satellite 6's management tools, such as katello-agent. Make sure to add this parameter.

How does that sound?

> 
> If using an environment file for Satellite registration (see Section 6.12,
> “Registering the Overcloud”), make sure to update the following parameters
> in the environment file:
> 
> * rhel_reg_repos - Repositories to enable for your Overcloud, including the
> new Red Hat OpenStack Platform 8 repositories.

I don't think this is used on upgrade, though I could be wrong.  We do manually change things for CDN/Sat6.  Sat 5 should change automatically with the right activation key.

> 
> * rhel_reg_activation_key - The new activation key for your Red Hat
> OpenStack Platform 8 repositories.

this should only be needed with Sat5, not sat6.

> 
> * rhel_reg_sat_repo - A new parameter that defines the repository containing
> Red Hat Satellite 6's management tools, such as katello-agent. Make sure to
> add this parameter.

This should only matter for Sat6, not Sat5

> 
> How does that sound?

(In reply to Mike Burns from comment #14)
> > 
> > If using an environment file for Satellite registration (see Section 6.12,
> > “Registering the Overcloud”), make sure to update the following parameters
> > in the environment file:
> > 
> > * rhel_reg_repos - Repositories to enable for your Overcloud, including the
> > new Red Hat OpenStack Platform 8 repositories.
> 
> I don't think this is used on upgrade, though I could be wrong.  We do
> manually change things for CDN/Sat6.  Sat 5 should change automatically with
> the right activation key.

I think I included this in case they still had the old repos for Sat 6/CDN. Would this not make a difference? Would the upgrade script or these params take precedence?

> > 
> > * rhel_reg_activation_key - The new activation key for your Red Hat
> > OpenStack Platform 8 repositories.
> 
> this should only be needed with Sat5, not sat6.

Systems can use activation keys to register to both Satellite 5 and 6. If using a Satellite 6 activation key when initially registering their OSP 7 Overcloud, wouldn't they also need to include a new activation key?

> > 
> > * rhel_reg_sat_repo - A new parameter that defines the repository containing
> > Red Hat Satellite 6's management tools, such as katello-agent. Make sure to
> > add this parameter.
> 
> This should only matter for Sat6, not Sat5
> 

I'll update the last sentence to "Make sure to add this parameter if registering to Red Hat Satellite 6."

Just to note, I added this for another BZ: https://bugzilla.redhat.com/show_bug.cgi?id=1329242


> > 
> > How does that sound?

(In reply to Dan Macpherson from comment #15)
> (In reply to Mike Burns from comment #14)
> > > 
> > > If using an environment file for Satellite registration (see Section 6.12,
> > > “Registering the Overcloud”), make sure to update the following parameters
> > > in the environment file:
> > > 
> > > * rhel_reg_repos - Repositories to enable for your Overcloud, including the
> > > new Red Hat OpenStack Platform 8 repositories.
> > 
> > I don't think this is used on upgrade, though I could be wrong.  We do
> > manually change things for CDN/Sat6.  Sat 5 should change automatically with
> > the right activation key.
> 
> I think I included this in case they still had the old repos for Sat 6/CDN.
> Would this not make a difference? Would the upgrade script or these params
> take precedence?

I don't actually know.  If they actually explicitly stated which repos to enable, then they should change it appropriately.  If they relied on their activation key to enable only the right repos, then they don't need it


> 
> > > 
> > > * rhel_reg_activation_key - The new activation key for your Red Hat
> > > OpenStack Platform 8 repositories.
> > 
> > this should only be needed with Sat5, not sat6.
> 
> Systems can use activation keys to register to both Satellite 5 and 6. If
> using a Satellite 6 activation key when initially registering their OSP 7
> Overcloud, wouldn't they also need to include a new activation key?

With Sat 6, we don't remove and re-register like we have to do with Sat 5 (hence the need for a new key).  With Sat 6, they should update their key to allow osp8 repositories.  As long as they've done that, the code should switch their repos appropriately.
> 
> > > 
> > > * rhel_reg_sat_repo - A new parameter that defines the repository containing
> > > Red Hat Satellite 6's management tools, such as katello-agent. Make sure to
> > > add this parameter.
> > 
> > This should only matter for Sat6, not Sat5
> > 
> 
> I'll update the last sentence to "Make sure to add this parameter if
> registering to Red Hat Satellite 6."
> 
> Just to note, I added this for another BZ:
> https://bugzilla.redhat.com/show_bug.cgi?id=1329242

ACK, thanks
> 
> 
> > > 
> > > How does that sound?