Common issues with Satellite 6.2 upgrade or installation

Updated -

This article highlights some of the common issues faced while installing or upgrading to Satellite 6.2.

README

Please note that many of the below issues as well as other bugs have been resolved Red Hat Satellite 6.2 errata listed in these Articles: Red Hat Satellite Release Dates and Satellite 6 Component Versions
Customers who have already upgraded to 6.2 should follow the instructions in the latest errata.
Customers who are on 6.1.x should follow the upgrade instructions at https://access.redhat.com/documentation/en/red-hat-satellite/6.2/paged/installation-guide/chapter-6-upgrading-satellite-server-and-capsule-server.

How to Install or Upgrade Red Hat Satellite 6 server to latest 6.2 version?

Follow Red Hat Satellite 6 Installation Guide which contains pre-requisites, installation and upgrade steps for both Satellite and Capsule.

How to setup Red Hat Satellite 6 with custom SSL certificates

https://access.redhat.com/solutions/1273623

When and how to upgrade or update Red Hat Satellite 6

https://access.redhat.com/solutions/2146501

How to upgrade self registered Red Hat Satellite v 6.1.9 to Red Hat Satellite v 6.2?

https://access.redhat.com/solutions/2486631

Common Issues

Red Hat Satellite upgrade from 6.1.11 to 6.2.x fails with error "Could not start Service[qpidd]: Execution of '/usr/share/katello-installer-base/modules/service_wait/bin/service-wait start qpidd' returned 6"

https://access.redhat.com/solutions/3031811

[Satellite6.2.11] qpidd fails to start with "Queue ..: recoverQueues() failed: jexception 0x0000 (Journal file .. has fid=0x1 which already exists for this journal." error

https://access.redhat.com/solutions/3157651

After upgrading to Satellite-6.2.10 manifest refresh is failing with "password component depends user component"

https://access.redhat.com/solutions/3093191
Resolved with Satellite 6.2 errata (see top of page)

Upgrade to 6.2.11 fails on "mv: cannot move ‘/var/lib/qpidd/.qpidd/qls/jrnl/resource_manager/.’ .." or similar

https://access.redhat.com/solutions/3148641
Resolved with Satellite 6.2 errata (see top of page)

Candlepin Failure when updating Red Hat Satellite 6.2 to RHEL 7.4

https://access.redhat.com/solutions/3136351
Resolved with Satellite 6.2 errata (see top of page)

High memory usage and unresponded hosts search query after upgrade to 6.2.9

https://access.redhat.com/solutions/3023131
Resolved with Satellite 6.2 errata (see top of page)

Satellite 6 : Content Hosts selection under Hosts empty "You currently don't have any Content Hosts" or keeps loading endlessly after Satellite upgrade.

https://access.redhat.com/solutions/1758323
Resolved in Satellite 6.2

Cannot enable Red Hat Satellite Tools Repo on Satellite 6.2

Selecting Red Hat Satellite Tools 6.2 inside Red Hat Repositories for:
- RHEL 5 (Workstation/Server)
- RHEL 6 (Workstation/Server)
- RHEL 7 (Workstation/Server)
- All result in CDN forbidden errors like "CDN loading error: access forbidden to https://cdn.redhat.com:443/content/dist/rhel/server/6/6Server/x86_64/sat-tools/6.2/os/repodata/repomd.xml"

https://access.redhat.com/solutions/2475941
Resolved with Satellite 6.2 errata (see top of page)

Unable to enable Red Hat Satellite 6.2 repositories using subscription-manager, fails with "Error: rhel-7-server-satellite-6.2-rpms is not a valid repository ID. Use --list option to see valid repositories."

Users are unable to access the newly released Red Hat Satellite 6.2 repositories that are part of their subscription:
- rhel-6-server-satellite-6.2-rpms
- rhel-7-server-satellite-6.2-rpms

Attempts to enable these repositories are met with errors that the repository does not exist:

# subscription-manager repos --enable rhel-7-server-satellite-6.2-rpms
Error: rhel-7-server-satellite-6.2-rpms is not a valid repository ID. Use --list option to see valid repositories.

https://access.redhat.com/solutions/2472261
Resolved with errata RHSA-2016:2592

Red Hat Satellite 6.1.9 to 6.2 upgrade causes duplicate Hosts and Content Hosts

After Red Hat Satellite 6.1.9 to 6.2.0 upgrade, registering a system with short hostname configured on it causes duplicate profiles created in Hosts and Content Hosts
https://access.redhat.com/solutions/2482641
Resolved with Satellite 6.2 errata (see top of page)

Red Hat Satellite 6.2 manifest import fails

https://access.redhat.com/solutions/2488481
Resolved with Satellite 6.2 errata (see top of page)

Satellite 6.2 Virtual Datacenter (VDC) subscription does not show any product content, guest subscriptions show as null in activation key

https://access.redhat.com/solutions/2594971
Resolved with Satellite 6.2 errata (see top of page)

Upgraded Satellite 6.2 Server Cannot Sync "Katello::Resources::Candlepin::Owner: 500 Internal Server Error"

https://access.redhat.com/solutions/2525481
Resolved with Satellite 6.2 errata (see top of page)

Receiving PLP0034: distributor errors while attempting to publish new version of Content Views / sync repositories on Red Hat Satellite Capsule 6.2

https://access.redhat.com/solutions/2600231
Resolved with Satellite 6.2 errata (see top of page)

Satellite 6.1.9 upgrade to 6.2 GA is taking significant amount of time

https://access.redhat.com/solutions/2484641
Resolved with Satellite 6.2 errata (see top of page)

[Satellite 6.2] Error while trying to evaluate the upgrade process using '--noop' option

Getting below error in satellite.logs while trying to evaluate the upgrade process using --noop option:

Processing report from satellite.example.com with processor Puppet::Reports::Store
Puppet has finished, bye!
Executing hooks in group post
Hook /usr/share/katello-installer-base/hooks/post/10-post_install.rb returned nil
Upgrade failed during the installation phase. Fix the error and re-run the upgrade.
Hook /usr/share/katello-installer-base/hooks/post/30-upgrade.rb returned [<Logging::Logger:0x19f4150 name="main">, <Logging::Logger:0x19fa924 name="fatal">, <Logging::Logger:0x1b690a8 name="verbose">]
All hooks in group post finished
Exit with status code: 4 (signal was 4)

https://access.redhat.com/solutions/2477571
Resolved - Satellite 6.2 documentation has been added to clarify this and avoid error.

Upgrade from satellite 6.1 to 6.2 fails with Could not evaluate: Proxy cannot be registered (Connection refused - connect(2)): N/A"

Related to above "[Satellite 6.2] Error while trying to evaluate the upgrade process using '--noop' option"
https://access.redhat.com/solutions/2479161
Satellite 6.2 documentation has been added to clarify this and avoid error.

DHCP configuration in Capsule gets overridden during 6.2 upgrade

Manual edits to DNS or DHCP configuration files are overwritten during upgrade.

https://access.redhat.com/solutions/2482981

Satellite 6.2 upgrade fails with Upgrade step start_tomcat failed despite tomcat starting promptly

https://access.redhat.com/solutions/2476551
Resolved with Satellite 6.2 errata (see top of page)

Upgrade to Satellite 6.2 fails with "tomcat fails to start" ; getting "401 Unauthorized" errors

https://access.redhat.com/solutions/2487971
Resolved not a bug, see Solution for details.

Upgrade to Red Hat Satellite 6.2 Fails at Update_Subscription_Facet_Backend_Data Step

https://access.redhat.com/solutions/2485931
Resolved with Satellite 6.2 errata (see top of page)

Various performance issues after upgrade from 6.1

Manual removal of some gutterball bits is required.

https://access.redhat.com/solutions/2608341

Error: "Access to was denied . You don't have authorization to view this page after upgrade. HTTP ERROR 403"

https://access.redhat.com/solutions/3200562

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.
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.