IBM Support

Maximo Application Suite CLI failure during DRO installation on ROSA

Troubleshooting


Problem

During a Maximo Application Suite installation using the MAS CLI on a ROSA cluster, the installation fails during the DRO step. This error can be seen in the DRO task logs:
TASK [ibm.mas_devops.dro : Create OperatorGroup in redhat-marketplace namespace if not exist] *** fatal: [localhost]: FAILED! => changed=false error: 403 msg: 'Namespace redhat-marketplace: Failed to create object: b''{"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"admission webhook \\"namespace-validation.managed.openshift.io\\" denied the request: Prevented from accessing Red Hat managed namespaces. Customer workloads should be placed in customer namespaces, and should not match an entry in this list of regular expressions: [^kube.* ^default$ ^redhat.* ^dedicated-admin$ ^openshift-addon-operator$ ^openshift-aqua$ ^openshift-aws-vpce-operator$ ^openshift-backplane$ ^openshift-backplane-cee$ ^openshift-backplane-csa$ ^openshift-backplane-cse$ ^openshift-backplane-csm$ ^openshift-backplane-managed-scripts$ ^openshift-backplane-mobb$ ^openshift-backplane-srep$ ^openshift-backplane-tam$ ^openshift-cloud-ingress-operator$ ^openshift-codeready-workspaces$ ^openshift-compliance$ ^openshift-compliance-monkey$ ^openshift-container-security$ ^openshift-custom-domains-operator$ ^openshift-customer-monitoring$ ^openshift-deployment-validation-operator$

Cause

This is due to security limitations with ROSA preventing access to RedHat managed namespaces. The MAS CLI attempts to install DRO in the redhat-marketplace namespace, which is not allowed with default ROSA security configurations.

Resolving The Problem

With the release of MAS CLI 9.4.0, users will now be prompted by the MAS CLI interactive installer to specify the namespace they would like to install DRO in. On a ROSA cluster, a non-default namespace should be specified to ensure this error does not arise.
For non-interactive installs or when using the ansible playbook, the DRO_NAMESPACE environment variable can be used to specify the DRO installation namespace as well.

Related Information

Document Location

Worldwide

[{"Type":"MASTER","Line of Business":{"code":"LOB59","label":"Sustainability Software"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSRHPA","label":"IBM Maximo Application Suite"},"ARM Category":[{"code":"a8m3p000000GoLBAA0","label":"Maximo Application Suite-\u003EInstallation"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Versions"}]

Document Information

Modified date:
24 June 2024

UID

ibm17158194