summaryrefslogtreecommitdiffstats
path: root/mcp/config/scenario/k8-calico-nofeature-noha.yaml
diff options
context:
space:
mode:
authorAlexandru Avadanii <Alexandru.Avadanii@enea.com>2020-01-08 17:33:13 +0100
committerAlexandru Avadanii <Alexandru.Avadanii@enea.com>2020-01-13 10:21:01 +0000
commit181d6ccbb8f7fdfa46cb2bacb599406bb810f1c0 (patch)
tree559318d534b17a6fcf4ce391408d3e2f86c9815d /mcp/config/scenario/k8-calico-nofeature-noha.yaml
parentc7c70e890292ec85b05546d91f9dbedbb6df81fb (diff)
baremetal, virtual: Bump kernel to hwe-18.04 (5.0)
On some aarch64 platforms (e.g. ThunderX 1), lvcreate manifests some spurious timing issues resulting in incomplete/corrupted LVM thin creation and eventually to transaction ID mismatch between userspace and kernel space. This eventually leads to cinder-volume issues, either when creating the thin storage pool (vgroot-pool) and/or when creating the LVs inside said pool. The issue manifests spuriously on Ubuntu Bionic + UCA, so until a working combination of userspace/kernel is found, work around this by bumping the kernel package to hwe-18.04 (kernel 5.0), effectively bypassing the timing issues during volume creation. This affects all cluster machines (both HA and NOHA scenarios, baremetal and virtual, x86_64 and aarch64, baremetal and virtualized nodes). Note: Ubuntu Bionic cloud image partition handling requires e2fsprogs 1.43, not currently available on Ubuntu Xenial / CentOS 7. Change-Id: I839e03080104c391fe18185b9544c9df43c114e6 Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com> (cherry picked from commit f03bfd30206c1d21de7e5c9ef2f6ed79f6ee13f4)
Diffstat (limited to 'mcp/config/scenario/k8-calico-nofeature-noha.yaml')
0 files changed, 0 insertions, 0 deletions