-
Bug
-
Resolution: Done
-
Undefined
-
None
-
None
-
None
-
5
-
False
-
-
False
-
?
-
rhos-product-tooling
-
None
-
-
-
Sprint 114, Sprint 115
-
2
-
Important
To Reproduce Steps to reproduce the behavior:
- Create a devsetup crc with the default 'CRC_VERSION=latest'
- 'make input openstack'
- 'make openstack_init'
- the 'nncp' target times out, then connectivity with the control plane fails:
oc apply -f /home/steveb/dev/localstack/install_yamls/out/openstack/nncp/cr/ nodenetworkconfigurationpolicy.nmstate.io/eth0-98-fa-9b-b6-2e-cb created timeout 240s bash -c "while ! (oc wait nncp -l osp/interface=eth0 --for jsonpath='{.status.conditions[0].reason}'=SuccessfullyConfigured); do sleep 10; done" error: reason is not found error: timed out waiting for the condition on nodenetworkconfigurationpolicies/eth0-98-fa-9b-b6-2e-cb error: You must be logged in to the server (Unauthorized) error: You must be logged in to the server (Unauthorized) error: You must be logged in to the server (Unauthorized) error: You must be logged in to the server (Unauthorized) make: *** [Makefile:2393: nncp] Error 124
Expected behavior
- nncp target completes successfully
Device Info (please complete the following information):
- VM running latest CRC
- also seen on SNO running on bare metal
Bug impact
- This is affecting developers who want to run install_yamls with defaults and OCP 4.18. Considering this has been seen on SNO there is a high chance this will affect customers deploying RHOSO on OCP 4.18 so we should give this some attention
Known workaround
- Downgrade to CRC_VERSION=2.41.0 which installs OCP 4.16. 'make nncp' sometimes fails with this version but less frequently.
Additional context
Here is an example of the nncp that gets applied
apiVersion: nmstate.io/v1 kind: NodeNetworkConfigurationPolicy metadata: labels: osp/interface: eth0 name: eth0-98-fa-9b-b6-2e-cb spec: desiredState: dns-resolver: config: search: [] server: - 192.168.88.1 interfaces: - description: internalapi vlan interface name: eth0.20 state: up type: vlan vlan: base-iface: eth0 id: 20 reorder-headers: true ipv4: address: - ip: 172.17.0.5 prefix-length: 24 enabled: true dhcp: false ipv6: enabled: false - description: storage vlan interface name: eth0.21 state: up type: vlan vlan: base-iface: eth0 id: 21 reorder-headers: true ipv4: address: - ip: 172.18.0.5 prefix-length: 24 enabled: true dhcp: false ipv6: enabled: false - description: tenant vlan interface name: eth0.22 state: up type: vlan vlan: base-iface: eth0 id: 22 reorder-headers: true ipv4: address: - ip: 172.19.0.5 prefix-length: 24 enabled: true dhcp: false ipv6: enabled: false - description: storagemgmt vlan interface name: eth0.23 state: up type: vlan vlan: base-iface: eth0 id: 23 reorder-headers: true ipv4: address: - ip: 172.20.0.5 prefix-length: 24 enabled: true dhcp: false ipv6: enabled: false - description: Octavia vlan host interface name: eth0.24 state: up type: vlan vlan: base-iface: eth0 id: 24 - bridge: options: stp: enabled: false port: - name: eth0.24 description: Configuring bridge octbr mtu: 1500 name: octbr state: up type: linux-bridge - description: designate vlan interface name: eth0.25 state: up type: vlan vlan: base-iface: eth0 id: 25 reorder-headers: true ipv4: address: - ip: 172.28.0.5 prefix-length: 24 enabled: true dhcp: false ipv6: enabled: false - description: designate external vlan interface name: eth0.26 state: up type: vlan vlan: base-iface: eth0 id: 26 reorder-headers: true ipv4: address: - ip: 172.50.0.5 prefix-length: 24 enabled: true dhcp: false ipv6: enabled: false - description: Configuring Bridge ospbr with interface eth0 name: ospbr mtu: 1500 type: linux-bridge state: up bridge: options: stp: enabled: false port: - name: eth0 vlan: {} ipv4: address: - ip: 192.168.122.10 prefix-length: 24 enabled: true dhcp: false ipv6: enabled: false nodeSelector: kubernetes.io/hostname: 98-fa-9b-b6-2e-cb node-role.kubernetes.io/worker: ""
- links to
- mentioned in
-
Page Loading...