Uploaded image for project: 'OpenShift API for Data Protection'
  1. OpenShift API for Data Protection
  2. OADP-749

[Docs] The output of `oc get all -n openshift-adp` command is misleading

XMLWordPrintable

    • False
    • Hide

      None

      Show
      None
    • False
    • QE - Ack
    • ToDo
    • 0
    • 0
    • Very Likely
    • 0
    • None
    • Unset
    • Unknown
    • No

      Description of problem: The output of the `oc get all -n openshift-adp` command in the offical documentation is showing the old output from 1.0.z:

       

      NAME                                                     READY   STATUS    RESTARTS   AGE
      pod/oadp-operator-controller-manager-67d9494d47-6l8z8    2/2     Running   0          2m8s
      pod/oadp-velero-sample-1-aws-registry-5d6968cbdd-d5w9k   1/1     Running   0          95s
      pod/restic-9cq4q                                         1/1     Running   0          94s
      pod/restic-m4lts                                         1/1     Running   0          94s
      pod/restic-pv4kr                                         1/1     Running   0          95s
      pod/velero-588db7f655-n842v                              1/1     Running   0          95s
      
      NAME                                                       TYPE        CLUSTER-IP       EXTERNAL-IP   PORT(S)    AGE
      service/oadp-operator-controller-manager-metrics-service   ClusterIP   172.30.70.140    <none>        8443/TCP   2m8s
      service/oadp-velero-sample-1-aws-registry-svc              ClusterIP   172.30.130.230   <none>        5000/TCP   95s
      
      NAME                    DESIRED   CURRENT   READY   UP-TO-DATE   AVAILABLE   NODE SELECTOR   AGE
      daemonset.apps/restic   3         3         3       3            3           <none>          96s
      
      NAME                                                READY   UP-TO-DATE   AVAILABLE   AGE
      deployment.apps/oadp-operator-controller-manager    1/1     1            1           2m9s
      deployment.apps/oadp-velero-sample-1-aws-registry   1/1     1            1           96s
      deployment.apps/velero                              1/1     1            1           96s
      
      NAME                                                           DESIRED   CURRENT   READY   AGE
      replicaset.apps/oadp-operator-controller-manager-67d9494d47    1         1         1       2m9s
      replicaset.apps/oadp-velero-sample-1-aws-registry-5d6968cbdd   1         1         1       96s
      replicaset.apps/velero-588db7f655                              1         1         1       96s 

      we need to remove everything that is related to registry, e.g:

       

       

      NAME                                                     READY   STATUS    RESTARTS   AGE
      pod/oadp-operator-controller-manager-67d9494d47-6l8z8    2/2     Running   0          2m8s
      pod/restic-9cq4q                                         1/1     Running   0          94s
      pod/restic-m4lts                                         1/1     Running   0          94s
      pod/restic-pv4kr                                         1/1     Running   0          95s
      pod/velero-588db7f655-n842v                              1/1     Running   0          95s
      
      NAME                                                       TYPE        CLUSTER-IP       EXTERNAL-IP   PORT(S)    AGE
      service/oadp-operator-controller-manager-metrics-service   ClusterIP   172.30.70.140    <none>        8443/TCP   2m8s
      
      NAME                    DESIRED   CURRENT   READY   UP-TO-DATE   AVAILABLE   NODE SELECTOR   AGE
      daemonset.apps/restic   3         3         3       3            3           <none>          96s
      
      NAME                                                READY   UP-TO-DATE   AVAILABLE   AGE
      deployment.apps/oadp-operator-controller-manager    1/1     1            1           2m9s
      deployment.apps/velero                              1/1     1            1           96s
      
      NAME                                                           DESIRED   CURRENT   READY   AGE
      replicaset.apps/oadp-operator-controller-manager-67d9494d47    1         1         1       2m9s
      replicaset.apps/velero-588db7f655                              1         1         1       96s 

      see step 5 here:

      https://docs.openshift.com/container-platform/4.11/backup_and_restore/application_backup_and_restore/installing/installing-oadp-aws.html#oadp-installing-dpa_installing-oadp-aws

      relevant to all types of installation (Azure,GCP,MCG

       

              rhn-support-cwisemon Carmi Wisemon
              mperetz@redhat.com Maya Peretz
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: