You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What happened:
I created an nncp policy that configures a bond on the openshift provisioning network, with 2 static ipv6 addresses. Adding bonding interface , with set of ipv6 static ips, conflicts with openshift extra VIP it configures on the bond on one of the master nodes, making the nncp policy fail. What you expected to happen:
nncp policy to successfully configure, even if not the desired list of ips is not the full list. I need the policy to ensure the set of ips to be present, but not exclusive. If there is an extra ip, it is ok. How to reproduce it (as minimally and precisely as possible):
Create the following nncp on openshift cluster with bonding is configured on the provisioning network
Anything else we need to know?:
Wondering if there is a supported way to just add ips, and not make sure the list of IPs are the only IPs present. Environment:
NodeNetworkState on affected nodes (use kubectl get nodenetworkstate <node_name> -o yaml): Not necessary, i can provide if neeeded
Problematic NodeNetworkConfigurationPolicy: see above
At newer kubernetes-nmstate (OCP 4.10) we have a capture feature to copy stuff from current state, if the number of "extra" ips is know we can use capture to copy them as part of the NNCP
What happened:
I created an nncp policy that configures a bond on the openshift provisioning network, with 2 static ipv6 addresses. Adding bonding interface , with set of ipv6 static ips, conflicts with openshift extra VIP it configures on the bond on one of the master nodes, making the nncp policy fail.
What you expected to happen:
nncp policy to successfully configure, even if not the desired list of ips is not the full list. I need the policy to ensure the set of ips to be present, but not exclusive. If there is an extra ip, it is ok.
How to reproduce it (as minimally and precisely as possible):
Create the following nncp on openshift cluster with bonding is configured on the provisioning network
Anything else we need to know?:
Wondering if there is a supported way to just add ips, and not make sure the list of IPs are the only IPs present.
Environment:
NodeNetworkState
on affected nodes (usekubectl get nodenetworkstate <node_name> -o yaml
): Not necessary, i can provide if neeededNodeNetworkConfigurationPolicy
: see abovekubectl get pods --all-namespaces -l app=kubernetes-nmstate -o jsonpath='{.items[0].spec.containers[0].image}'
): registry.redhat.io/container-native-virtualization/kubernetes-nmstate-handler-rhel8@sha256:8853dc6495d723c582a52a519d13bc188883797a900240586fac442492431d08nmcli --version
) nmcli tool, version 1.30.0-10.el8_4kubectl version
):Client Version: 4.7.16
Server Version: 4.8.19
Kubernetes Version: v1.21.4+6438632
NAME="Red Hat Enterprise Linux CoreOS"
VERSION="48.84.202110270303-0"
ID="rhcos"
ID_LIKE="rhel fedora"
VERSION_ID="4.8"
PLATFORM_ID="platform:el8"
PRETTY_NAME="Red Hat Enterprise Linux CoreOS 48.84.202110270303-0 (Ootpa)"
ANSI_COLOR="0;31"
CPE_NAME="cpe:/o:redhat:enterprise_linux:8::coreos"
HOME_URL="https://www.redhat.com/"
DOCUMENTATION_URL="https://docs.openshift.com/container-platform/4.8/"
BUG_REPORT_URL="https://bugzilla.redhat.com/"
REDHAT_BUGZILLA_PRODUCT="OpenShift Container Platform"
REDHAT_BUGZILLA_PRODUCT_VERSION="4.8"
REDHAT_SUPPORT_PRODUCT="OpenShift Container Platform"
REDHAT_SUPPORT_PRODUCT_VERSION="4.8"
OPENSHIFT_VERSION="4.8"
RHEL_VERSION="8.4"
OSTREE_VERSION='48.84.202110270303-0'
The text was updated successfully, but these errors were encountered: