With the re20141114 compose on RHEL6-x86_64 with @Base, installation complained about the following: === /media/cdrom $ ./install.pl * Starting Red Hat Satellite installer. * Performing pre-install checks. * Pre-install checks complete. Beginning installation. * RHN Registration. ** Registration: System is already registered with RHN. Not re-registering. * Checking for uninstalled prerequisites. ** Checking if yum is available ... There are some packages from Red Hat Enterprise Linux that are not part of the @base group that Satellite will require to be installed on this system. The installer will try resolve the dependencies automatically. However, you may want to install these prerequisites manually. Do you want the installer to resolve dependencies [y/N]? y * Installing RHN packages. Warning: more packages were installed by yum than expected: OpenIPMI OpenIPMI-libs db4-cxx db4-devel gdbm-devel glibc-devel glibc-headers ipmitool kernel-headers lm_sensors-libs net-snmp-libs syslinux-nonlinux Warning: yum did not install the following packages: postgresql-contrib postgresql-pltcl postgresql-server * Now running spacewalk-setup. ... === Note that the postgresql packages should now be postgresql92-postgresql-contrib postgresql92-postgresql-pltcl postgresql92-postgresql-server
*** Bug 1158695 has been marked as a duplicate of this bug. ***
*** Bug 1133922 has been marked as a duplicate of this bug. ***
Verified, this doesn't happen with: rhn-upgrade-5.7.0.13-1 Satellite-5.7.0-RHEL6-re20141205.0-x86_64
With the release of Red Hat Satellite 5.7 on January 12th 2015 this bug is being moved to a Closed Current Release state. The Satellite 5.7 GA Errata: - https://rhn.redhat.com/errata/RHSA-2015-0033.html Satellite 5.7 Release Notes: - https://access.redhat.com/documentation/en-US/Red_Hat_Satellite/5.7/html-single/Release_Notes/index.html Satellite Customer Portal Blog announcement for release: - https://access.redhat.com/blogs/1169563/posts/1315743 Cliff NOTE: This bug has not been re-verified (moved to RELEASE_PENDING) prior to release. We assume that the bug has indeed been fixed and not regressed since we initially verified it. Please re-open in the future if needed.