How to apply a Program Temporary Fix (PTF) to a containerized SUSE Manager 5

This document (000021531) is provided subject to the disclaimer at the end of this document.

Environment

SUSE Manager Server 5
SUSE Manager Proxy 5

Situation

A Program Temporary Fix (PTF) was received to address an issue reported for a containerized SUSE Manager 5 installation.

Resolution

Applying a containerized fix to SUSE Manager 5 is accomplished using the following command:

mgradm support ptf podman --ptf <PTFnumber> --user <accountID>

The <PTFnumber> will be provided by a SUSE Support representative.
The <accountID> can be found in the SUSE Customer Center account, either to the right of the company name or on the left hand side in the navigation frame in grey font under the company name. Please make sure to select the account the SUSE Manager installation is registered to.

NOTE: The starting letter of the "accountID" needs to be specified in lower case, similar to how it is in the provided PTF registry link.

In case the issue has not been properly identified, a tentative fix may be provided as a TEST build first. This is applied using:

mgradm support ptf podman --test <TESTnumber> --user <accountID>

Additional Information

PTFs provided via registry.suse.com are only created for the account as identified by a provided SUSE Manager supportconfig (created using "mgradm support config"). This data tar-ball is the required base information for a SUSE Manager support request. A supportconfig created directly on the SLE Micro instance running the container is not sufficient.

In case the update process exists with an exit status 125, for example:

Error: initializing source docker://registry.suse.com/a/a232408/150158/suse/manager/5.0/x86_64/server:latest-ptf-150158: reading manifest latest-ptf-150158 in registry.suse.com/a/a232408/150158/suse/manager/5.0/x86_64/server: requested access to the resource is denied
Error: exit status 125

This indicates the account used is not entitled to access this resource.
Please contact a SUSE Support representative in such a case to address this.

The SUSE Manager 5 container will be restarted as part of the update operation. Please wait until the container
is fully operational. To monitor, run "watch -n 10 podman ps":

CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
ba424348034a registry.suse.com/a/a232408/150158/suse/manager/5.0/x86_64/server:latest-ptf-150158 /usr/lib/systemd/... 55 seconds ago Up 54 seconds (starting) 0.0.0.0:80->80/tcp, 0.0.0.0:443->443/tcp,
0.0.0.0:4505-4506->4505-4506/tcp, 0.0.0.0:5432->5432/tcp, 0.0.0.0:5556-5557->5556-5557/tcp, 0.0.0.0:9100->9100/tcp, 0.0.0.0:9187->9187/tcp, 0.0.0.0:9800->9800/tcp, 0.0.0.0:25151->25151/tcp, 0.0.0.0:69->69/udp uyuni-server

and wait until the STATUS column changes from (starting) to (healthy):

CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
ba424348034a registry.suse.com/a/a232408/150158/suse/manager/5.0/x86_64/server:latest-ptf-150158 /usr/lib/systemd/... 2 minutes ago Up 2 minutes (healthy) 0.0.0.0:80->80/tcp, 0.0.0.0:443->443/tcp, 0.
0.0.0:4505-4506->4505-4506/tcp, 0.0.0.0:5432->5432/tcp, 0.0.0.0:5556-5557->5556-5557/tcp, 0.0.0.0:9100->9100/tcp, 0.0.0.0:9187->9187/tcp, 0.0.0.0:9800->9800/tcp, 0.0.0.0:25151->25151/tcp, 0.0.0.0:69->69/udp uyuni-server

Once the container is back in a "(healthy)" state, please check whether the PTF supplied addressed the issue reported and provide feedback to the SUSE Support representative assigned to the case.

To apply regular RPTFs, see: TID 000018572 - Best practice for applying Program Temporary Fixes (PTFs)

Disclaimer

This Support Knowledgebase provides a valuable tool for SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.