Merge pull request #59876 from michaelryanpeter/ocpbugs-12151-oc-get-packagemainfests-procedure-step

OCPBUGS#12151: oc get packagemanifests procedure step

Author: michaelryanpeter

modules/olm-installing-specific-version-cli.adoc

@@ -116,14 +116,32 @@ Kind:         PackageManifest
 +
 [TIP]
 ====
-You can format an Operator's version and channel information in the YAML format by running the following command:
+You can print an Operator's version and channel information in the YAML format by running the following command:
 
 [source,terminal]
 ----
 $ oc get packagemanifests <operator_name> -n <catalog_namespace> -o yaml
 ----
 ====
 
+** If more than one catalog is installed in a namespace, run the following command to look up the available versions and channels of an Operator from a specific catalog:
++
+[source,terminal]
+----
+$ oc get packagemanifest \
+   --selector=catalog=<catalogsource_name> \
+   --field-selector metadata.name=<operator_name> \
+   -n <catalog_namespace> -o yaml
+----
++
+[IMPORTANT]
+====
+If you do not specify the Operator's catalog, running the `oc get packagemanifest` and `oc describe packagemanifest` commands might return a package from an unexpected catalog if the following conditions are met:
+
+* Multiple catalogs are installed in the same namespace.
+* The catalogs contain the same Operators or Operators with the same name.
+====
+
 . An Operator group, defined by an `OperatorGroup` object, selects target namespaces in which to generate required role-based access control (RBAC) access for all Operators in the same namespace as the Operator group.
 +
 The namespace to which you subscribe the Operator must have an Operator group that matches the install mode of the Operator, either the `AllNamespaces` or `SingleNamespace` mode. If the Operator you intend to install uses the `AllNamespaces` mode, then the `openshift-operators` namespace already has an appropriate Operator group in place.