MetricsService deployment fails with "must be no more than 63 characters" after upgrading to Ansible Automation Platform 2.7

Solution Verified - Updated -

Issue

  • After upgrading Red Hat Ansible Automation Platform from version 2.6 to 2.7 on OpenShift, the MetricsService instance fails to deploy.
  • The parent AnsibleAutomationPlatform CR status or the Metricsservice CR status displays a Failure state, and inspecting the namespace events or the operator logs reveals the following validation error:

    Failed to create object: b'{"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"Deployment.apps \"ansible-automation-platform-automationmetricsservice-web\" is invalid:
     [spec.template.spec.volumes[5].name: Invalid value: \"ansible-automation-platform-automationmetricsservice-bundle-cacert\": must be no more than 63 characters,
     spec.template.spec.containers[0].volumeMounts[5].name: Not found: \"ansible-automation-platform-automationmetricsservice-bundle-cacert\", spec.template.spec.initContainers[0].volumeMounts[1].name: Not found:
     \"ansible-automation-platform-automationmetricsservice-bundle-cacert\"]","reason":"Invalid", ... "code":422}'
    

Environment

  • Red Hat Ansible Automation Platform (AAP) 2.7
  • Red Hat OpenShift Container Platform (OCP) 4.x
  • Parent AnsibleAutomationPlatform Custom Resource (CR) configured with a long name (e.g., ansible-automation-platform or longer)

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content