Fix an issue with libvirt pods not starting

The cgroup folder has been changed by commit:
https://review.openstack.org/#/c/648511/

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 <Al.Bailey@windriver.com>
This commit is contained in:
Al Bailey 2019-04-12 15:49:29 -05:00
parent a5def9a144
commit bdf1d603b0
2 changed files with 4 additions and 1 deletions

View File

@ -1,3 +1,3 @@
SRC_DIR="stx-openstack-helm"
COPY_LIST_TO_TAR="$PKG_BASE/../../../helm-charts/rbd-provisioner $PKG_BASE/../../../helm-charts/garbd $PKG_BASE/../../../helm-charts/ceph-pools-audit"
TIS_PATCH_VER=10
TIS_PATCH_VER=11

View File

@ -657,6 +657,9 @@ data:
libvirt:
node_selector_key: openstack-compute-node
node_selector_value: enabled
conf:
kubernetes:
cgroup: "k8s-infra"
images:
tags:
libvirt: docker.io/starlingx/stx-libvirt:master-centos-stable-latest