As a result the new hugepage folder was being created at:
/sys/fs/cgroup/hugetlb/k8s-infra
However the helm-chart default location was still looking at:
/sys/fs/cgroup/hugetlb/kubepods
The k8s-infra label for the cgroup folder has now been added
to the armada manifest, and libvirt pods are able to launch.
Closes-Bug: 1824567
Change-Id: I3f420dc4643b37f56cec3b38449ca9b0d3b8fe4f
Signed-off-by: Al Bailey <email address hidden>
Reviewed: https:/ /review. openstack. org/652149 /git.openstack. org/cgit/ openstack/ stx-config/ commit/ ?id=bdf1d603b0b 75a217d5d98d153 ab0f45a3f51ffe
Committed: https:/
Submitter: Zuul
Branch: master
commit bdf1d603b0b75a2 17d5d98d153ab0f 45a3f51ffe
Author: Al Bailey <email address hidden>
Date: Fri Apr 12 15:49:29 2019 -0500
Fix an issue with libvirt pods not starting
The cgroup folder has been changed by commit: /review. openstack. org/#/c/ 648511/
https:/
As a result the new hugepage folder was being created at: fs/cgroup/ hugetlb/ k8s-infra fs/cgroup/ hugetlb/ kubepods
/sys/
However the helm-chart default location was still looking at:
/sys/
The k8s-infra label for the cgroup folder has now been added
to the armada manifest, and libvirt pods are able to launch.
Closes-Bug: 1824567 f56cec3b38449ca 9b0d3b8fe4f
Change-Id: I3f420dc4643b37
Signed-off-by: Al Bailey <email address hidden>