Disable OperatorHub manifest not applied while performing disconnected SNO installation

Solution In Progress - Updated -

Issue

  • When try to install the RHOCP (SNO) with a completely offline installation with assisted-installer (AI) applied 'disable-operatorhub.yaml' manifest during deployment time, some errors while applying it, and then it failed with the error
Nov 10 14:27:34 localhost.localdomain cluster-bootstrap[11793]: Skipped "disable-operatorhub.yaml" operatorhubs.v1.config.openshift.io/cluster -n  as it already exists
Nov 10 14:27:34 localhost.localdomain bootkube.sh[11739]: Skipped "disable-operatorhub.yaml" operatorhubs.v1.config.openshift.io/cluster -n  as it already exists

Environment

  • Red Hat OpenShift Container Platform
    • 4.10
    • 4.11
  • SNO
  • Disconnected
  • Assisted installer (AI)

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