Doc: Install instructions implies that sriov=enabled is mandatory

Bug #1943600 reported by Thiago Paiva Brito
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
StarlingX
Low
Juanita-Balaraj

Bug Description

Brief Description
-----------------
The installation instructions for StarlingX, when using Openstack, implies that sriov=enabled is mandatory, when that option should only be used when the user actually has a NIC that supports SRIO-V.

Severity
--------
Minor: System/Feature is usable with minor issue

Steps to Reproduce
------------------
Install StarlingX blindly following the instructions in a (baremetal) server that doesn't support SRIO-V.

Expected Behavior
------------------
System works

Actual Behavior
----------------
The kube-sriov-device-plugin-amd64-XXXXX pod crashes.

Reproducibility
---------------
Seen several times with unwarned users.

System Configuration
--------------------
SX:
https://docs.starlingx.io/deploy_install_guides/r5_release/virtual/aio_simplex_install_kubernetes.html#openstack-specific-host-configuration
https://docs.starlingx.io/deploy_install_guides/r5_release/bare_metal/aio_simplex_install_kubernetes.html#openstack-specific-host-configuration
https://docs.starlingx.io/deploy_install_guides/r6_release/virtual/aio_simplex_install_kubernetes.html#openstack-specific-host-configuration
https://docs.starlingx.io/deploy_install_guides/r6_release/bare_metal/aio_simplex_install_kubernetes.html#openstack-specific-host-configuration
DX:
https://docs.starlingx.io/deploy_install_guides/r5_release/virtual/aio_duplex_install_kubernetes.html#openstack-specific-host-configuration
https://docs.starlingx.io/deploy_install_guides/r5_release/bare_metal/aio_duplex_install_kubernetes.html#openstack-specific-host-configuration
https://docs.starlingx.io/deploy_install_guides/r6_release/virtual/aio_duplex_install_kubernetes.html#openstack-specific-host-configuration
https://docs.starlingx.io/deploy_install_guides/r6_release/bare_metal/aio_duplex_install_kubernetes.html#openstack-specific-host-configuration
Standard:
https://docs.starlingx.io/deploy_install_guides/r5_release/virtual/controller_storage_install_kubernetes.html#id2
https://docs.starlingx.io/deploy_install_guides/r5_release/bare_metal/controller_storage_install_kubernetes.html#id2
https://docs.starlingx.io/deploy_install_guides/r6_release/virtual/controller_storage_install_kubernetes.html#id2
https://docs.starlingx.io/deploy_install_guides/r6_release/bare_metal/controller_storage_install_kubernetes.html#id2

Branch/Pull Time/Commit
-----------------------
-

Last Pass
---------
-

Timestamp/Logs
--------------
[sysadmin@controller-0 ~(keystone_admin)]$ kubectl get pods -A -o wide
NAMESPACE NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES
armada armada-api-7c44fd56fd-mqxcm 2/2 Running 4 3d5h 172.16.192.79 controller-0 <none> <none>
cert-manager cm-cert-manager-856678cfb7-2t7z6 1/1 Running 0 10h 172.16.166.131 controller-1 <none> <none>
cert-manager cm-cert-manager-856678cfb7-7jngc 1/1 Running 1 3d5h 172.16.192.77 controller-0 <none> <none>
cert-manager cm-cert-manager-cainjector-85849bd97-5ftv6 1/1 Running 1 10h 172.16.166.130 controller-1 <none> <none>
cert-manager cm-cert-manager-cainjector-85849bd97-xdggf 1/1 Running 2 3d5h 172.16.192.76 controller-0 <none> <none>
cert-manager cm-cert-manager-webhook-5745478cbc-4mtrk 1/1 Running 1 3d5h 172.16.192.75 controller-0 <none> <none>
cert-manager cm-cert-manager-webhook-5745478cbc-ww9nn 1/1 Running 0 10h 172.16.166.132 controller-1 <none> <none>
kube-system calico-kube-controllers-5cd4695574-87sjg 1/1 Running 1 3d5h 172.16.192.80 controller-0 <none> <none>
kube-system calico-node-cxg5w 1/1 Running 3 6h16m 192.168.204.167 worker-0 <none> <none>
kube-system calico-node-kddhp 1/1 Running 0 10h 192.168.204.3 controller-1 <none> <none>
kube-system calico-node-ptnh4 1/1 Running 1 3d5h 192.168.204.2 controller-0 <none> <none>
kube-system ceph-pools-audit-1631559900-d2h69 0/1 Completed 0 58s 172.16.192.85 controller-0 <none> <none>
kube-system cephfs-provisioner-54847c557b-vp45q 1/1 Running 0 5m40s 172.16.192.83 controller-0 <none> <none>
kube-system cephfs-provisioner-54847c557b-zdbgp 1/1 Running 0 5m40s 172.16.166.134 controller-1 <none> <none>
kube-system cephfs-storage-init-pzxdc 0/1 Completed 0 5m27s 172.16.192.84 controller-0 <none> <none>
kube-system coredns-6d64d47ff4-pmqpj 1/1 Running 0 3d5h 172.16.166.129 controller-1 <none> <none>
kube-system coredns-6d64d47ff4-vbp4v 1/1 Running 1 3d5h 172.16.192.78 controller-0 <none> <none>
kube-system ic-nginx-ingress-ingress-nginx-controller-b227s 1/1 Running 1 3d5h 192.168.204.2 controller-0 <none> <none>
kube-system ic-nginx-ingress-ingress-nginx-controller-v5pcd 1/1 Running 0 10h 192.168.204.3 controller-1 <none> <none>
kube-system kube-apiserver-controller-0 1/1 Running 2 3d5h 192.168.204.2 controller-0 <none> <none>
kube-system kube-apiserver-controller-1 1/1 Running 0 10h 192.168.204.3 controller-1 <none> <none>
kube-system kube-controller-manager-controller-0 1/1 Running 3 3d5h 192.168.204.2 controller-0 <none> <none>
kube-system kube-controller-manager-controller-1 1/1 Running 0 10h 192.168.204.3 controller-1 <none> <none>
kube-system kube-multus-ds-amd64-64vrf 1/1 Running 0 4h15m 192.168.204.167 worker-0 <none> <none>
kube-system kube-multus-ds-amd64-jf2zw 1/1 Running 1 3d5h 192.168.204.2 controller-0 <none> <none>
kube-system kube-multus-ds-amd64-r7j8m 1/1 Running 0 10h 192.168.204.3 controller-1 <none> <none>
kube-system kube-proxy-2fxxf 1/1 Running 1 3d5h 192.168.204.2 controller-0 <none> <none>
kube-system kube-proxy-c7hp8 1/1 Running 0 10h 192.168.204.3 controller-1 <none> <none>
kube-system kube-proxy-q6bv2 1/1 Running 3 6h16m 192.168.204.167 worker-0 <none> <none>
kube-system kube-scheduler-controller-0 1/1 Running 2 3d5h 192.168.204.2 controller-0 <none> <none>
kube-system kube-scheduler-controller-1 1/1 Running 1 10h 192.168.204.3 controller-1 <none> <none>
kube-system kube-sriov-cni-ds-amd64-4n69c 1/1 Running 1 3d5h 192.168.204.2 controller-0 <none> <none>
kube-system kube-sriov-cni-ds-amd64-m5ljn 1/1 Running 0 10h 192.168.204.3 controller-1 <none> <none>
kube-system kube-sriov-cni-ds-amd64-ml6df 1/1 Running 0 4h15m 192.168.204.167 worker-0 <none> <none>
kube-system kube-sriov-device-plugin-amd64-8nwwl 0/1 CrashLoopBackOff 4 117s 192.168.204.167 worker-0 <none> <none>
kube-system rbd-provisioner-77bfb6dbb-4c77n 1/1 Running 0 6m9s 172.16.166.133 controller-1 <none> <none>
kube-system rbd-provisioner-77bfb6dbb-4nzvw 1/1 Running 0 6m9s 172.16.192.81 controller-0 <none> <none>
kube-system storage-init-rbd-provisioner-jbjrh 0/1 Completed 0 5m53s 172.16.192.82 controller-0 <none> <none>
[sysadmin@controller-0 ~(keystone_admin)]$ kubectl delete pods -n kube-system
[sysadmin@controller-0 ~(keystone_admin)]$ kubectl logs kube-sriov-device-plugin-amd64-8nwwl -n kube-system
I0913 19:05:37.762865 227879 manager.go:52] Using Kubelet Plugin Registry Mode
I0913 19:05:37.763370 227879 main.go:44] resource manager reading configs
I0913 19:05:37.763594 227879 manager.go:86] raw ResourceList: {
  "resourceList": [

  ]
}
I0913 19:05:37.763613 227879 manager.go:106] unmarshalled ResourceList: []
E0913 19:05:37.763634 227879 main.go:51] no resource configuration; exiting

Test Activity
-------------
Evaluation

Workaround
----------
Remove the label

tags: added: stx.docs
Changed in starlingx:
assignee: nobody → Juanita-Balaraj (balaraj)
M Camp (mcamp859)
Changed in starlingx:
status: New → Triaged
Ghada Khalil (gkhalil)
Changed in starlingx:
importance: Undecided → Low
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers