Satellite 6.2.11 is released
Satellite 6.2.11 has been released today. 6.2.11 introduces many fixes in the messaging infrastructure of Satellite 6. There is one erratum for the server [1] and one for the hosts [2]. The install ISOs will be updated next week at the earliest.
Customers who have already upgraded to 6.2 should follow the instructions in the errata. Customers who are on 6.1.x should follow the upgrade instructions at [3].
PLEASE NOTE: Customers who have received hotfixes should verify the list below to ensure their hotfix is contained in the release before upgrading. Their hotfixes may be overwritten if they upgrade. Please reach out to the Satellite team if you are unsure.
The list of bugs resolved in 6.2.11 include:
-
Updated QPID packages have been included to address performance and memory issues. (BZ#1367735, BZ#1443470, BZ#1431783, BZ#1449743, BZ#1468450, BZ#1368718)
-
Users can now manage a system without the use of gofer. (BZ#1445403)
-
Several search bugs have been resolved. (BZ#1392422, BZ#1462350)
-
The RBAC system has been updated to unlock behaviors for non-admin users and to suppress database errors. (BZ#1246865, BZ#1427282)
-
Manifest refreshes were not respecting proxy settings on the host. These settings are now respected. (BZ#1464881)
-
A batch job has been introduced to clean up repository metadata on Capsules. (BZ#1425691)
-
An error message from foreman-rake was causing confusion. The message has now been cleaned up. (BZ#1429418)
-
Deleting an interface was deleting the entire host record. The code will now correctly only delete the interface. (BZ#1285669)
-
Bulk Capsule syncs were causing a race condition which resulted in failed syncs. This case is now handled correctly. (BZ#1391298, BZ#1443213)
-
This release contains various memory and performance improvements. (BZ#1434040, BZ#1458857, BZ#1437150)
-
Users can now browse to /pub on Capsule Servers over HTTPS. (BZ#1432580)
-
Certain trends would show a database error. The query behind this trend has been resolved. (BZ#1375000)
Please reach out with any questions or concerns.
[1] https://access.redhat.com/errata/RHBA-2017:2466
[2] https://access.redhat.com/errata/RHBA-2017:2467
[3] https://access.redhat.com/documentation/en/red-hat-satellite/6.2/paged/installation-guide/chapter-6-upgrading-satellite-server-and-capsule-server

Comments
Thanks, the performance and memory fixes are most welcome! What about running satellite on 7.4? There seems to be a couple of conflicts between packages in the satellite repo and the server repos. When will satellite be "7.4 ready"?
Would you be so kind as to list the conflicts if the list is not too long ? Thanks.
Sure, here they are. It's only two packages that have problems:
I've given the satellite repo higher priority (through the yum priorities plugin) than the other rhel repos. With the priorities plugin disabled, yum would run without issues.
Another method I found for a similar problem is to create a filter in the content view for your Satellite that excludes those RPM's from the offending repo. I am not certain that Satellite would not overwrite priority options as they are not an available option in the repository setup
@Trond, are you on a disconnetced server? We tested on 7.4 and did not see that error.
Requirement "libtasn1 >= 3.9" should be met by a fully synchronised 7.4 repository. libtasn1-4.10-1.el7.X86_64 is provided by RHEL 7.4.
Same for libdb-cxx-5.3.21-19.el7.x86_64. RHEL 7.4 provides libdb-cxx-5.3.21-20.el7.x86_64 and libdb-5.3.21-20.el7.x86_64.
Ok, seems to me that my extra security measure by using priorities to give the satellite repo a higher priority is causing this. My fault for being too careful :) I'll give the satellite repo the same priority as the other rhel repos, and upgrading shouldn't be a problem. Thanks for clearing this up.
FYI: https://bugzilla.redhat.com/show_bug.cgi?id=1480560
Bug 1480560 - Satellite upgrade to 6.2.11 fails (yadda yadda yadda)
Thanks for that link, Daniel White. Is RedHat working on packaging the fix? I have two satellites dead in the water due to qpidd issues.
Is RedHat working on packaging the fix? - Check the BugZilla
I was able to fix my setup last night with this: https://access.redhat.com/solutions/2780041
Not ideal but it worked. Had to rebuild for all content hosts and restart goferd.
Hi,
Here is the actual workaround https://access.redhat.com/node/3148641
Thanks
-Christian
Hey,
When should the install ISO be released ? Will new content ISOs for RHEL 6 & 7 be released too ?
Thanks !
is it recommended to disable goferd now? After satellite 6.2.11 update all of our satellite clients started having swap or memory issues. restarting goferd resolved temporarily. I then updated goferd to gofer-2.7.7-2.el6sat.noarch and so far haven't seen swap.
But, if I can manage my host without goferd, i think i would like to. Do i just disable it? Is it required to update all the 'tools' packages on the client listed here https://access.redhat.com/errata/RHBA-2017:2467 ?
We only use remote execution to perform updates.
This article covers how to manage clients without goferd: https://access.redhat.com/articles/3154811
How would you recommend to upgrade satellite 6.2.6 in a disconnected mode ? the installation ISO is not yet available.
We really need this new version, sadly at the download URL https://access.redhat.com/downloads/content/250/ver=6.2/rhel---7/6.2.10/x86_64/product-software , only 6.2.10 is available (as I type this on 8/28/2017) - is there some way we can obtain the 6.2.11 iso download (just the program), because the iso file at the URL I gave here only has 6.2.10. This is for a number of disconnected satellite servers.
My upgrade on 2017-08-30 from 6.2.9 to 6.2.11 was partially successful. The master upgraded successfully. The capsule failed with qpidd errors. The fix from RH support was:
cp -arv /var/lib/qpidd/.qpidd /var/lib/qpidd/.qpidd.bak
rm -rf /var/lib/qpidd/.qpidd/qls/dat2
satellite-installer --scenario capsule --upgrade
It sounds like there are still qpidd issues to work out after the initial 6.2.11 problems.