Uploaded image for project: 'Red Hat OpenStack Services on OpenShift'
  1. Red Hat OpenStack Services on OpenShift
  2. OSPRH-6180

NNCP fails always the firs time it is applied

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Normal Normal
    • rhos-18.0.0
    • None
    • architecture
    • None
    • False
    • Hide

      None

      Show
      None
    • False
    • ?
    • ?
    • ?
    • ?
    • None
    • Important

      This is the process:
      1. apply nncp process.
      oc apply -f nncp.yaml

      2. It fails
      [ciuser@tigon28 ~]$ oc get nncp
      NAME STATUS REASON
      nfv-master-0 Degraded FailedToConfigure
      nfv-master-1 Degraded FailedToConfigure
      nfv-master-2 Degraded FailedToConfigure

      3. I event have problems to execute oc commands, but this is solved after a few seconds
      [ciuser@tigon28 ovs-dpdk-sriov]$ oc get nncp
      Unable to connect to the server: dial tcp 192.168.51.2:6443: connect: no route to host
      [ciuser@tigon28 ovs-dpdk-sriov]$ oc get nncp
      Unable to connect to the server: dial tcp 192.168.51.2:6443: connect: no route to host

      4. I delete nncp
      [ciuser@tigon28 ~]$ oc delete nncp nfv-master-0
      nodenetworkconfigurationpolicy.nmstate.io "nfv-master-0" deleted
      [ciuser@tigon28 ~]$ oc delete nncp nfv-master-1
      nodenetworkconfigurationpolicy.nmstate.io "nfv-master-1" deleted
      [ciuser@tigon28 ~]$ oc delete nncp nfv-master-2
      nodenetworkconfigurationpolicy.nmstate.io "nfv-master-2" deleted

      5. I apply nncp again, same file
      [ciuser@tigon28 ovs-dpdk-sriov]$ oc apply -f nncp.yaml
      nodenetworkconfigurationpolicy.nmstate.io/nfv-master-0 created
      nodenetworkconfigurationpolicy.nmstate.io/nfv-master-1 created
      nodenetworkconfigurationpolicy.nmstate.io/nfv-master-2 created

      6. Now it is ok
      [ciuser@tigon28 ovs-dpdk-sriov]$ oc get nncp
      NAME STATUS REASON
      nfv-master-0 Available SuccessfullyConfigured
      nfv-master-1 Available SuccessfullyConfigured
      nfv-master-2 Available SuccessfullyConfigured

      In the logs of oc nodes I can see:
      Apr 05 12:19:12 nfv-master-0 kubenswrapper[2858]: E0405 12:19:12.279688 2858 kubelet_node_status.go:589] "Error updating node status, will retry" err="error getting node \"nfv-master-0\": Get \"https://api-int.nfv.openstack.lab:6443/api/v1/nodes/nfv-master-0?resourceVersion=0&timeout=10s\": net/http: request canceled (Client.Timeout exceeded while awaiting headers)"
      Apr 05 12:19:22 nfv-master-0 kubenswrapper[2858]: E0405 12:19:22.280340 2858 kubelet_node_status.go:589] "Error updating node status, will retry" err="error getting node \"nfv-master-0\": Get \"https://api-int.nfv.openstack.lab:6443/api/v1/nodes/nfv-master-0?timeout=10s\": net/http: request canceled (Client.Timeout exceeded while awaiting headers)"
      Apr 05 12:19:32 nfv-master-0 kubenswrapper[2858]: E0405 12:19:32.281222 2858 kubelet_node_status.go:589] "Error updating node status, will retry" err="error getting node \"nfv-master-0\": Get \"https://api-int.nfv.openstack.lab:6443/api/v1/nodes/nfv-master-0?timeout=10s\": net/http: request canceled (Client.Timeout exceeded while awaiting headers)"
      Apr 05 12:19:36 nfv-master-0 kubenswrapper[2858]: E0405 12:19:36.975833 2858 kubelet_node_status.go:589] "Error updating node status, will retry" err="error getting node \"nfv-master-0\": Get \"https://api-int.nfv.openstack.lab:6443/api/v1/nodes/nfv-master-0?timeout=10s\": http2: client connection lost"

            jpalanis@redhat.com Jaganathan Palanisamy
            mnietoji@redhat.com Miguel Angel Nieto Jimenez
            rhos-dfg-ci-framework
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: