Description of Problem

• When trying to collect a must-gather for openshift-gitops version 1.17 using the must-gather images for the v1.17 tags,  the must-gather produced always turns out to be empty and no details are captured.
• must-gather logs seem to indicate a problem with some `oc get resource ` command

Additional Info

$ oc adm must-gather --image=registry.redhat.io/openshift-gitops-1/must-gather-rhel8:v1.17.0
[must-gather      ] OUT 2025-08-23T09:57:10.566505595Z Using must-gather plug-in image: registry.redhat.io/openshift-gitops-1/must-gather-rhel8:v1.17.0
When opening a support case, bugzilla, or issue please include the following summary data along with any other requested information:
ClusterID: 3323f6d4-8423-41fc-bebb-33bb107fa5a0
ClientVersion: 4.16.43
ClusterVersion: Stable at "4.16.43"
ClusterOperators:
    clusteroperator/network is progressing: DaemonSet "/openshift-multus/network-metrics-daemon" is not available (awaiting 1 nodes)
DaemonSet "/openshift-network-operator/iptables-alerter" is not available (awaiting 1 nodes)
    clusteroperator/operator-lifecycle-manager is not upgradeable because ClusterServiceVersions blocking cluster upgrade: openshift-logging/cluster-logging.v5.9.15 is incompatible with OpenShift minor versions greater than 4.16

[must-gather      ] OUT 2025-08-23T09:57:10.631144473Z namespace/openshift-must-gather-rgqqd created
[must-gather      ] OUT 2025-08-23T09:57:10.639385511Z clusterrolebinding.rbac.authorization.k8s.io/must-gather-zwgm7 created
[must-gather      ] OUT 2025-08-23T09:57:10.678273546Z pod for plug-in image registry.redhat.io/openshift-gitops-1/must-gather-rhel8:v1.17.0 created
[must-gather-5hqbk] POD 2025-08-23T09:57:13.634306277Z volume percentage checker started.....
[must-gather-5hqbk] POD 2025-08-23T09:57:13.643190489Z volume usage percentage 0
[must-gather-5hqbk] POD 2025-08-23T09:57:13.960838738Z gather_gitops:12] inspecting crd, clusterversion ..
[must-gather-5hqbk] POD 2025-08-23T09:57:16.266145046Z error: resource name may not be empty
[must-gather-5hqbk] POD 2025-08-23T09:57:16.367316919Z error: there is no need to specify a resource type as a separate argument when passing arguments in resource/name form (e.g. 'oc get resource/<resource_name>' instead of 'oc get resource resource/<resource_name>'   <-------------------
[must-gather-5hqbk] OUT 2025-08-23T09:57:20.730246498Z waiting for gather to complete
[must-gather-5hqbk] OUT 2025-08-23T09:57:20.73462983Z downloading gather output
[must-gather-5hqbk] OUT 2025-08-23T09:57:21.000348366Z receiving incremental file list
[must-gather-5hqbk] OUT 2025-08-23T09:57:21.003270598Z ./
[must-gather-5hqbk] OUT 2025-08-23T09:57:21.003500569Z gather_gitops.log
[must-gather-5hqbk] OUT 2025-08-23T09:57:21.006224649Z 
[must-gather-5hqbk] OUT 2025-08-23T09:57:21.006415687Z sent 46 bytes  received 169 bytes  143.33 bytes/sec
[must-gather-5hqbk] OUT 2025-08-23T09:57:21.006510104Z total size is 52  speedup is 0.24
[must-gather      ] OUT 2025-08-23T09:57:21.037690061Z namespace/openshift-must-gather-rgqqd deleted
[must-gather      ] OUT 2025-08-23T09:57:21.047607143Z clusterrolebinding.rbac.authorization.k8s.io/must-gather-zwgm7 deleted

Problem Reproduction

• Tested using the must-gather images below for v1.17 and they generate an empty must-gather every time
• registry.redhat.io/openshift-gitops-1/must-gather-rhel8:v1.17.0-5 registry.redhat.io/openshift-gitops-1/must-gather-rhel8:v1.17.0
• The behavior is seem at the customer environment and in my environment when I tried testing it
• Using the tag `v.16.0`, must-gather collection is successful.

Reproducibility

• must-gather always comes up empty

Prerequisites/Environment

• <OpenShift, managed service (e.g., ROSA, ARO), operators, layered product, and other software versions, build details>

Steps to Reproduce

• Install openshift-gitops operator 1.17
• Deploy ArgoCD instance
• Collect must-gather using `oc adm must-gather --image=registry.redhat.io/openshift-gitops-1/must-gather-rhel8:v1.17.0`

Expected Results

• Must-gather collection should complete successfully and must-gather should not be empty

Actual Results

• An empty must-gather is generated

Problem Analysis

• <Completed by engineering team as part of the triage/refinement process>

Root Cause

• <What is the root cause of the problem? Or, why is it not a bug?>

Workaround (If Possible)

• <Are there any workarounds we can provide to the customers?>

Fix Approaches

• <If we decide to fix this bug, how will we do it?>

Acceptance Criteria

• ...

Definition of Done

• Code Complete:
  • All code has been written, reviewed, and approved.
• Tested:
  • Unit tests have been written and passed.
  • Ensure code coverage is not reduced with the changes.
  • Integration tests have been automated.
  • System tests have been conducted, and all critical bugs have been fixed.
  • Tested and merged on OpenShift either upstream or downstream on a local build.
• Documentation:
  • User documentation or release notes have been written (if applicable).
• Build:
  • Code has been successfully built and integrated into the main repository / project.
  • Midstream changes (if applicable) are done, reviewed, approved and merged.
• Review:
  • Code has been peer-reviewed and meets coding standards.
  • All acceptance criteria defined in the user story have been met.
  • Tested by reviewer on OpenShift.
• Deployment:
  • The feature has been deployed on OpenShift cluster for testing.