Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

NNCP status not updated after cluster scale down #1098

Open
qinqon opened this issue Jun 8, 2022 · 0 comments
Open

NNCP status not updated after cluster scale down #1098

qinqon opened this issue Jun 8, 2022 · 0 comments

Comments

@qinqon
Copy link
Member

qinqon commented Jun 8, 2022

What happened:
When a node from a cluster is removed the NNCP status is still showing the same number of nodes

  status:
    conditions:
    - lastHeartbeatTime: "2022-06-08T13:35:03Z"
      lastTransitionTime: "2022-06-08T13:35:03Z"
      message: 2/2 nodes successfully configured
      reason: SuccessfullyConfigured
      status: "True"
      type: Available

What you expected to happen:

NNCP status has to be updated with current number of nodes

  status:
    conditions:
    - lastHeartbeatTime: "2022-06-08T13:35:03Z"
      lastTransitionTime: "2022-06-08T13:35:03Z"
      message: 1/1 nodes successfully configured
      reason: SuccessfullyConfigured
      status: "True"
      type: Available

How to reproduce it (as minimally and precisely as possible):

  • Apply an NNCP
  • Remove a node from the cluster

Anything else we need to know?:

Environment:

  • NodeNetworkState on affected nodes (use kubectl get nodenetworkstate <node_name> -o yaml):
  • Problematic NodeNetworkConfigurationPolicy:
  • kubernetes-nmstate image (use kubectl get pods --all-namespaces -l app=kubernetes-nmstate -o jsonpath='{.items[0].spec.containers[0].image}'):
  • NetworkManager version (use nmcli --version)
  • Kubernetes version (use kubectl version):
  • OS (e.g. from /etc/os-release):
  • Others:
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant