Uploaded image for project: 'Red Hat OpenStack Services on OpenShift'
  1. Red Hat OpenStack Services on OpenShift
  2. OSPRH-26243

Section 1.3 of the deployment documentation failed to set update to manual

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • rhos-18.0.z
    • rhos-18.0.z
    • documentation
    • None
    • False
    • Hide

      None

      Show
      None
    • False
    • ?
    • rhos-conplat-core-operators
    • None
    • Bug Delivery Tracker
    • 1
    • Moderate

      Discrepancy between Web Console and CLI deployment instructions

      In 1.2. Installing the OpenStack Operator by using the web console we have:

      7. On the Install Operator page, select "Manual" from the Update approval list. For information about how to manually approve a pending Operator update, see Manually approving a pending Operator update in the RHOCP Operators guide.			 

      but then in 1.3. Installing the OpenStack Operator by using the CLI we have

      $ cat << EOF| oc apply -f -
      apiVersion: operators.coreos.com/v1alpha1
      kind: Subscription
      metadata:
        name: openstack-operator
        namespace: openstack-operators
      spec:
        name: openstack-operator
        channel: stable-v1.0
        source: redhat-operators
        sourceNamespace: openshift-marketplace
      EOF 

      which will create an Operator with the Update approval set to Automatic by default.

      In the spec section we need   installPlanApproval: Manual so that the final file looks like this:

      $ cat << EOF| oc apply -f -
      apiVersion: operators.coreos.com/v1alpha1
      kind: Subscription
      metadata:
        name: openstack-operator
        namespace: openstack-operators
      spec:
        name: openstack-operator
        channel: stable-v1.0
        source: redhat-operators
        sourceNamespace: openshift-marketplace
        installPlanApproval: Manual
      EOF

       

      Note that this will require the user to manually accept the install_plan created by OLM.

      Something like:

      # install plan name are "random" and look like this "install-fzpw4"
      # So we need to find the rigth one
      install_plan_name=$(oc get installplan -n openstack-operators -o json | jq -r '.items[] | select(.spec.approval=="Manual" and .spec.approved==false) | .metadata.name' | head -n1)
      
      # Then, when 'install_plan_name' is not empty (it might take some time for OLM to create the install_plan after the subscription has been created) we patch the resource to accept it:
      oc patch installplan $install_plan_name -n openstack-operators --type merge -p '{"spec":{"approved":true}}'

      before "4. Verify that the OpenStack Operator is installed: " in the documentation using the CLI.

       

              igallagh@redhat.com Irina Gallagher
              sathlang@redhat.com Sofer Athlan Guyot
              rhos-conplat-core-operators
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: