Bug 2069554 - kubernetes-nmstate resources and logs not included in must-gathers
Summary: kubernetes-nmstate resources and logs not included in must-gathers
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 4.10
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.10.z
Assignee: Christoph Stäbler
QA Contact: Aleksandra Malykhin
: 2068183 (view as bug list)
Depends On: 2062355
Blocks: 2068183
TreeView+ depends on / blocked
Reported: 2022-03-29 07:15 UTC by OpenShift BugZilla Robot
Modified: 2022-05-11 10:32 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2022-05-11 10:31:46 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift must-gather pull 294 0 None open [release-4.10] Bug 2069554: Collect NMState resources when operator is installed 2022-03-29 07:15:44 UTC
Red Hat Product Errata RHBA-2022:1690 0 None None None 2022-05-11 10:32:20 UTC

Comment 1 Christoph Stäbler 2022-03-29 07:16:14 UTC
*** Bug 2068183 has been marked as a duplicate of this bug. ***

Comment 6 Aleksandra Malykhin 2022-05-01 05:55:29 UTC

[kni@provisionhost-0-0 ~]$ oc get clusterversion
NAME      VERSION                              AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.10.0-0.nightly-2022-04-28-030337   True        False         2d20h   Cluster version is 4.10.0-0.nightly-2022-04-28-030337

[kni@provisionhost-0-0 ~]$ oc get csv -A
NAMESPACE                              NAME                                              DISPLAY                       VERSION               REPLACES   PHASE
openshift-nmstate                      kubernetes-nmstate-operator.4.10.0-202204211158   Kubernetes NMState Operator   4.10.0-202204211158              Succeeded

# Collect must-gather
oc adm must-gather 

# Install omg
pip3 install o-must-gather --user

# Check the nmstate data
[kni@provisionhost-0-0 ~]$omg use must-gather.local.5448190498349624412
[kni@provisionhost-0-0 ~]$ omg get all -n openshift-nmstate
NAME                                       READY  STATUS   RESTARTS  AGE
pod/nmstate-cert-manager-7f6f95fb49-45rrk  1/1    Running  0         2d
pod/nmstate-handler-6cnqc                  1/1    Running  0         2d
pod/nmstate-handler-8g7hm                  1/1    Running  0         2d
pod/nmstate-handler-9r54k                  1/1    Running  0         2d
pod/nmstate-handler-9r7vq                  1/1    Running  0         2d
pod/nmstate-handler-btp4p                  1/1    Running  0         2d
pod/nmstate-operator-ccfdf56fd-k7q7p       1/1    Running  0         2d
pod/nmstate-webhook-7cc4ffc5bc-6wdlw       1/1    Running  0         2d
pod/nmstate-webhook-7cc4ffc5bc-l9b6b       1/1    Running  0         2d

NAME                     TYPE       CLUSTER-IP     EXTERNAL-IP  PORT(S)  AGE
service/nmstate-webhook  ClusterIP  <none>       443/TCP  2d

daemonset/nmstate-handler  5        5        5      5           5          beta.kubernetes.io/arch=amd64  kubernetes.io/os=linux  2d

NAME                             READY  UP-TO-DATE  AVAILABLE  AGE
deployment/nmstate-cert-manager  1/1    1           1          2d
deployment/nmstate-operator      1/1    1           1          2d
deployment/nmstate-webhook       2/2    2           2          2d

NAME                                        DESIRED  CURRENT  READY  AGE
replicaset/nmstate-cert-manager-7f6f95fb49  1        1        1      2d
replicaset/nmstate-operator-ccfdf56fd       1        1        1      2d
replicaset/nmstate-webhook-7cc4ffc5bc       2        2        2      2d

Comment 9 errata-xmlrpc 2022-05-11 10:31:46 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (OpenShift Container Platform 4.10.13 bug fix update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


Note You need to log in before you can comment on or make changes to this bug.