Red Hat Satellite Upgrade Helper

Updated -

This app is designed to help you upgrade your Red Hat Satellite 6 to a newer version. All you need to provide is information about your upgrade path. We will not only present you the steps to upgrade Red Hat Satellite 6, but we'll also give you some extra steps that will prevent known issues specific to your upgrade scenario.

It supports the following upgrade paths:

  • 6.0 to 6.1
  • 6.1 to 6.2
  • 6.2 to 6.3
  • 6.3 to 6.4
  • 6.4 to 6.5
  • 6.5 to 6.6

Was this helpful?

We appreciate your feedback. Leave a comment if you would like to provide more detail.
It looks like we have some work to do. Leave a comment to let us know how we could improve.

Get notified when this content is updated

Follow

22 Comments

Subscriber exclusive content

An active Red Hat subscription is required to participate.

Log In

Is there an ETA when this helper will be updated to support going from Satellite 6.3 to 6.4?

Hi Tomas, Thank you for reaching out us. The app is updated for Satellite 6.4 today. You can use it for Satellite 6.4 now.

Need help upgrading from Satellite 5.6 to 6.4.

Hi Paul,

Advise: setup a new server running RH Satellite 6.4, once it is up and running migrate your clients.

RH Satellite 5.x and 6.y are completely different products.

Regards,

Jan Gerrit Kootstra

> This article worked for me.

The total upgrade from 6.4 to 6.5 only added 10GB to /var/lib/pulp. 

>

Hi Mike, What does you mean? Are you reporting a bug? Thanks.

All bugs are submitted to: https://bugzilla.redhat.com - My post was a comment that the process worked from 6.4 to 6.5 with additional note that the upgrade process added 10gb to my /var/lib/pulp filesystem.

Thanks for your explanation, Mike.

I ran into issues with DNS not starting with several issues related to proxy (this still isn't solved) so I used the addition of --foreman-proxy-dns false and it seemed to finish without trying to start that. I then had issues with getting the 6.4 repository to show, and after a case thread and phone call, it turns out that we need to add a new content view with the new 6.x repository, publish to an environment and then do a subscription-manager refresh before it will show up.

Hi Christopher,

Thank you for your comment, I found the support case you opened for the upgrade to Sat6.4.

After checking the support case, we need to confirm whether you are using DNS/DHCP feature on the satellite server or not. If we are not using the DNS feature then it is fine to use --foreman-proxy-dns false option to disable it.

Also, regarding the content view related issue, we do not need to create a new content view to add Satellite 6.4 tools repo, we can remove 6.3 tools repo from existing content view and add 6.4 tools repo then publish/promote the CV to the required environment so the repo will be accessible to the clients.

For further clarification, Suraj ( case owner) and I will work with you on the support case.

Thank you!

FYI - The link to the application "Red Hat Satellite Upgrade Helper" gives this response: 502 Bad Gateway The server returned an invalid or incomplete response.

Hi Andrew,

Thank you for reaching out us.

Can you try it again?

I can not reproduce it. Maybe you met a temporary network issue.

Thanks.

the ugo to application link is broken

Hi Ben,

Thank you for reaching out us.

I can not reproduce it.

Can you provide these information?

  • Which geo are you in?
  • Which language did you use to access the app?

Thanks.

Yunfeng

Thanks for the quick response, I'm getting the "502 Bad GatewayThe server returned an invalid or incomplete response." error in my Chrome browser when I click "go to Application"

When I pull it up in MS Edge, I'm able to get into the tool. So this seems browser-specific.

I am in the United States, I did not see any selection for language, but I would be using en_us

Dear colleagues, could you please add Satellite 6.6 upgrade paths? Thank you

Jiri,

Thanks for reaching out us.

I'm working on the update for Satellite 6.6 and hope can release it as soon as possible.

Thanks.

Clicking on the "Go to Application" link does not work. I get the error: This page isn’t workingIf the problem continues, contact the site owner. HTTP ERROR 400

Does not work in Chrome. Does work in Firefox.

I get same error in chrome, but when I open it in the Chrome Incognito window, it works properly. It seems some caching issue.

is there a direct upgrade from 6.3 to 6.6?

No, you must follow this upgrade path:

6.3 --> 6.4 --> 6.5 --> 6.6