Satellite 6.3.4 has just been released.

John Spinks published on 2018-10-10T21:58:58+00:00, last updated 2018-10-30T15:36:11+00:00

The main driver for the 6.3.4 release is ongoing performance and stability improvements.
There are 17 bugs squashed in this release - the complete list is below.

There is one erratum for the server [1] and one for the hosts [2]. The install ISOs will be updated next week.

Customers who have already upgraded to Satellite 6.3 should follow the instructions in the errata.
Customers who are on older versions of Satellite should refer to the Upgrading and Updating Red Hat Satellite Guide.

You may also want to consider using the Satellite Upgrade Helper if moving from Satellite 6.x to Satellite 6.3

Customers who have received hotfixes should verify the list below to ensure their hotfix is contained in the release before upgrading. Please reach out to Red Hat Support in these cases.

This update fixes the following bugs:

Candlepin throws 500 Internal Server Error for more than 40+ guests
(BZ#1633252)
Deprecate katello-backup, and katello-restore in Satellite 6.3
(BZ#1569672)
Sat 6.3 does not update repositories with modified data from
RCM/Entitlement Service (BZ#1570792)
upgraded foreman-selinux has no label for 2375/tcp (BZ#1624026)
Do not prevent host discovery for existing MAC/IP addresses (BZ#1624034)
Cannot delete host when missing from the candlepin database (BZ#1624019)
Content View is not updated on Content Host when change is made via
Hosts / All Hosts (BZ#1624020)
Re-add livecd-tools back to satellite repos (BZ#1624027)
Capsule overview page errors unable to fetch logs "ï¼¼xE1" from
ASCII-8BIT to UTF-8 (BZ#1624035)
Improve MonitorEventQueue performance for large workloads (BZ#1624038)
Satellite installation fails on rhel 7.6 Beta with
/Stage[main]/Candlepin::Service/Exec[cpinit]/returns: change from notrun
to 0 failed (BZ#1624022)
clean_backend_objects does not verify managed host status prior to
action (BZ#1624028)
processing virt-who report blocks RHSM certs checks what can lead to
503 errors (BZ#1624045)
On using UUID for content-host registration name, unexpected behavior
in entitlement status (BZ#1624033)
org_environment content access mode - authentication error while an
environment is updated on the client (BZ#1624036)
Unable to override hostgroup parameters from All hosts => edit host on
WebUI (BZ#1624025)
[RFE]Disable directory listing for /pub directory on satellite 6 using
custom-hiera. (BZ#1624021)

[1]https://access.redhat.com/errata/RHBA-2018:2915

[2] https://access.redhat.com/errata/RHBA-2018:2914

Satellite Migration from RHEL 6 to RHEL 7

As a reminder, Red Hat continues to strongly recommend your Satellite and Capsule Servers only be run on RHEL 7. There are several reasons why you should move your Satellite environment from RHEL 6 to RHEL 7 including enhanced performance and long-term supportability.

Future releases of Satellite (6.3 and above) will only support RHEL 7 and above. In preparation for newer versions of Satellite, you need to start thinking about how to move from older versions of RHEL to RHEL 7.
While RHEL 6 does support an in-place migration from RHEL 6 to RHEL 7, this migration mechanism is not supported when running Satellite on the RHEL host. Instead, you will need to clone your Satellite environment from a host running RHEL 6 to another host running RHEL 7.

Review the Satellite 6.2.13 release blog for more detailed information about moving your Satellite environment from RHEL 6 to RHEL 7. 6.2.13 includes some important features for capsule backup and recovery which helps to ease the movement from RHEL 6 to RHEL 7.

Language English

About The Author

Red Hat

John Spinks

John Spinks is a Principal Technical Marketing Manager for Red Hat. He acts as a subject matter expert for Red Hat Satellite and works with Red Hat partners and customers to build and share relevant information about managing patching, provisioning, subscription, and configuration management for Re...

Comments

FL Community Member 30 points

Unable to access BZ#1624021 ([RFE]Disable directory listing for /pub directory on satellite 6 using custom-hiera), would be nice to know how to enable directory listing again.

2018-11-01T09:56:54+00:00

Red Hat Guru 3070 points

Add the following line to /etc/foreman-installer/custom-hiera.yaml:

katello::pub_dir_options: "+FollowSymLinks"

Then rerun the installer

# satellite-installer --scenario satellite

After that, the /pub/ directory will be forbidden on both ports 80 and 443.

2018-11-01T12:54:45+00:00

Guru 12802 points

Hi John,

Can the announcement of this blog be blocked in the community message box of Satellite 6.4?

Regards,

Jan Gerrit Kootstra

2018-11-01T10:09:49+00:00

Red Hat Guru 3070 points

Satellite 6.4 only has a single URL which can be used as part of the RSS feature. And we use the Satellite blog for all announcements. So unfortunately no.

2018-11-01T13:01:38+00:00

Red Hat

While you can't block individual posts, you can turn the RSS feed off entirely or point towards a different RSS feed.

Log into Satellite and go to: Administration > Settings > Notifications

From here you can disable the RSS feed or change it.

Note that this will not immediately remove posts from your view - it will stop new posts from appearing.

You can go to the notification drawer and choose the clear all option to remove the existing posts from your view.

Hope this helps, John

2018-11-02T01:22:56+00:00

PG Newbie 12 points

update takes us to 6.3.5. already? satellite-6.3.5-1.el7sat.noarch satellite-cli-6.3.5-1.el7sat.noarch satellite-common-6.3.5-1.el7sat.noarch satellite-installer-6.3.0.12-1.el7sat.noarch * Fri Oct 19 2018 Evgeni Golov - 6.3.5-1 - Satellite 6.3.5

2018-11-02T12:36:08+00:00

Red Hat Community Member 57 points

There has been 6.3.5 already released this Tuesday https://access.redhat.com/errata/RHBA-2018:3411. I guess the blog post is't not ready yet for it.

2018-11-02T17:02:09+00:00

Red Hat

Blogs are being moved from the customer portal over to the main Red Hat page with the rest of the blogs.

Link to 6.3.5 post: https://www.redhat.com/en/blog/red-hat-satellite-635-now-generally-available

I plan to put a blog up about this on the customer portal once the blog team confirms the new URL and RSS feeds.

John

2018-11-02T20:57:16+00:00

Community Member 90 points

We experienced an strange behavior during the update to 6.3.5:

foreman-maintain upgrade run --target-version 6.3.z
....
The pre-upgrade checks indicate that the system is ready for upgrade.
It's recommended to perform a backup at this stage.
Confirm to continue with the modification part of the upgrade, [y(yes), n(no), q(quit)] y
Running Procedures before migrating to Satellite 6.3.z                          
================================================================================
Turn on maintenance mode:                                             [OK]
--------------------------------------------------------------------------------
disable active sync plans: 
- disabling sync plans

That step "disabling sync plans" is never ended even that the syncs were not active. As a consequence that command started to do strange things asking few times the hammer admin password (even that the password was also present in the foreman file).

...
Running Checks before upgrading to Satellite 6.3.z
================================================================================
Skipping pre_upgrade_checks phase as it was already run before.
To enforce to run the phase, use `upgrade run --phase pre_upgrade_checks`

Running preparation steps required to run the next scenarios
================================================================================
Setup hammer: 
Configuring Hammer CLI...
Hammer admin password: 
                                                                      [FAIL]
Hammer configuration failed: Is the admin password correct? (it was stored in /etc/foreman-maintain/foreman-maintain-hammer.yml)Is the server down?
--------------------------------------------------------------------------------
Scenario [preparation steps required to run the next scenarios] failed.

The following steps ended up in failing state:

  [hammer-setup]

Resolve the failed steps and rerun
the command. In case the failures are false positives,
use --whitelist="hammer-setup"



Running preparation steps required to run the next scenarios
================================================================================
Setup hammer: 
Configuring Hammer CLI...
Hammer admin password: 
                                                                      [FAIL]
Hammer configuration failed: Is the admin password correct? (it was stored in /etc/foreman-maintain/foreman-maintain-hammer.yml)Is the server down?
--------------------------------------------------------------------------------
Scenario [preparation steps required to run the next scenarios] failed.

The following steps ended up in failing state:

  [hammer-setup]

Resolve the failed steps and rerun
the command. In case the failures are false positives,
use --whitelist="hammer-setup"
...

As workaround just stop all sync plans manually using the GUI. Afterwards, run the foreman-maintain upgrade again:

...
The pre-upgrade checks indicate that the system is ready for upgrade.
It's recommended to perform a backup at this stage.
Confirm to continue with the modification part of the upgrade, [y(yes), n(no), q(quit)] y
Running Procedures before migrating to Satellite 6.3.z                          
================================================================================
Turn on maintenance mode:                                             [OK]
--------------------------------------------------------------------------------
disable active sync plans: 
- Total 0 sync plans are now disabled.                                [OK]      
--------------------------------------------------------------------------------
Stop applicable services: 
Stopping the following service(s):
...

2018-11-05T14:43:00+00:00 - Edited

Community Member 89 points

Why does this link keep showing up in my Satellite 6.4.1 server

2019-02-12T14:46:39+00:00

Red Hat

You may need to point your RSS feed to the new blog if you haven't already done so. This will read in the new posts vs the older blog location.

Follow the instructions at this blog: https://access.redhat.com/blogs/1169563/posts/3682541 .

Hope this helps, John

2019-02-12T15:19:40+00:00

LW Community Member 89 points

I'm currently running 6.4.1., to upgrade do I need to just do a "yum update" and reboot?? or is there more to it?

2019-02-13T19:35:25+00:00

BH Red Hat Pro 724 points

Hi, Leroy. This blog posting was about 6.3.4 being released. You will want to wait for news about 6.4.2. (That news should be coming, as it was just released today!)

When you are ready to update your Satellite (i.e. take it from 6.4.1 to 6.4.2 -- as opposed to "upgrade", which would take a 6.3 version of Satellite to 6.4) you'll want to refer to chapter 6 of the Upgrading and Updating Red Hat Satellite guide. That document explains how to use foreman-maintain to update your Satellite; yum is used by it, behind the scenes.

2019-02-13T19:55:00+00:00 - Edited

Red Hat

Also note that the blog has been moved, so new blog posts will appear at https://satelliteblog.redhat.com.

2019-02-14T01:57:37+00:00

Select Your Language

Infrastructure and Management

Cloud Computing

Storage

Runtimes

Integration and Automation

Warning message

Satellite 6.3.4 has just been released.

Satellite Migration from RHEL 6 to RHEL 7

About The Author

John Spinks

Comments