[Starlingx-discuss] kube-system kube-sriov-device-plugin-amd64-547xh 0/1 CrashLoopBackOff
Pratik M.
pvmpublic at gmail.com
Tue Jan 12 13:04:34 UTC 2021
Hi,
1. What does your /etc/pcidp/config.json look like?
2. Did you do all these steps?
# system host-label-assign controller-0 sriovdp=enabled
# system host-if-modify controller-0 <interface> -c pci-sriov -n sriov0 -N
<num vfs>
# system interface-datanetwork-assign controller-0 <interface>
<datanetwork>
# system host-unlock
Thanks
Pratik
On Tue, Jan 12, 2021 at 1:39 PM <lists at optimcloud.com> wrote:
> any idea how to resolve this, was installed from a recent 01/08/2021 build
> AIO
> Simplex ojn bare metal
>
> kube-system kube-sriov-device-plugin-amd64-547xh 0/1
> CrashLoopBackOff 4 2m49s
> [sysadmin at controller-0 ~(keystone_admin)]$ kubectl get logs
> kube-sriov-device-
> plugin-amd64-547xh --namespace kube-system
> error: the server doesn't have a resource type "logs"
> [sysadmin at controller-0 ~(keystone_admin)]$ kubectl logs kube-sriov-device-
> plugin-amd64-547xh --namespace kube-system
> I0112 08:05:19.714569 158061 manager.go:52] Using Kubelet Plugin Registry
> Mode
> I0112 08:05:19.714707 158061 main.go:44] resource manager reading configs
> I0112 08:05:19.714789 158061 manager.go:86] raw ResourceList: {
> "resourceList": [
>
> ]
> }
> I0112 08:05:19.714795 158061 manager.go:106] unmarshalled ResourceList: []
> E0112 08:05:19.714801 158061 main.go:51] no resource configuration;
> exiting
>
>
>
>
> _______________________________________________
> Starlingx-discuss mailing list
> Starlingx-discuss at lists.starlingx.io
> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.starlingx.io/pipermail/starlingx-discuss/attachments/20210112/28c1c49e/attachment.html>
More information about the Starlingx-discuss
mailing list