[Airship-discuss] Divingbell in AIAB

Georg Kunz georg.kunz at ericsson.com
Thu Jan 24 22:37:26 UTC 2019

Hi Craig,

Thanks for the hint regarding the hugepages. I never noticed that Ubuntu does this automatically because we typically control this explicitly in our deployments.

Anyway, in the meantime I also came across the versioning mismatch of divingbell and htk. I just bumped both versions to HEAD for testing purposes and it seems to have resolved the problem. 

Thanks a lot!

Best regards

-----Original Message-----
From: ANDERSON, CRAIG <ca846m at att.com> 
Sent: Thursday, January 24, 2019 10:43 PM
To: Georg Kunz <georg.kunz at ericsson.com>; airship-discuss at lists.airshipit.org
Subject: RE: Divingbell in AIAB

If you're running Ubuntu 16.04 or later, then Ubuntu will do this already by default, e.g.:
or check with:
"sudo systemctl status dev-hugepages.mount"

Regarding the error, this appears to be happening because the version of helm toolkit we have specified in versions.yaml is wrong for this version of divingbell. We need to either be using a newer version of divingbell, or an older version of helm toolkit to be compatible. I'll see about getting the versions aligned upstream, if not also re-enabling divingbell in AIAB.


-----Original Message-----
From: Georg Kunz [mailto:georg.kunz at ericsson.com] 
Sent: Thursday, January 24, 2019 7:13 AM
To: airship-discuss at lists.airshipit.org
Subject: [Airship-discuss] Divingbell in AIAB

Hi again,

I'll try to deploy divingbell in an AIAB multigate environment. By default divingbell is disabled in AIAB [1], but I'd like to use it to mount hugepages in the local filesystem.

After enabling (uncommenting ) divingbell in the manifest [1] and re-deploying the system, divingbell pods get deployed, but they get stuck in state "ContainerCreating". Digging deeper, the pod isn't able to mount one configmap:

Warning  FailedMount  1m (x470 over 15h)  kubelet, n0  MountVolume.SetUp failed for volume "divingbell-mounts" : configmaps "divingbell-mounts" not found

Checking the configmaps, there are in fact multiple divingbell configmaps, however the names are slightly different:


If I understand the divingbell chart templates correctly, the name "divingbell-mounts" is hardcoded there for the configmap [2][3]. Can somebody help me understand where the "-default" postfix comes from and how to resolve it?

[1] https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_openstack_airship-2Din-2Da-2Dbottle_blob_master_deployment-5Ffiles_global_v1.0demo_software_manifests_full-2Dsite.yaml-23L26&d=DwIGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=aimn2OylFgog_5_aS85wtQ&m=pgFJVPOeqLQoFm6_D-4rZS96wuvpXr-JbgM1VAuqqrY&s=okijvpj9PzyzWcl3plIejYr_Y9h3uBKUY_BxtIruGFw&e=
[2] https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_openstack_airship-2Ddivingbell_blob_master_divingbell_templates_daemonset-2Dmounts.yaml-23L59&d=DwIGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=aimn2OylFgog_5_aS85wtQ&m=pgFJVPOeqLQoFm6_D-4rZS96wuvpXr-JbgM1VAuqqrY&s=_ob8nMUQreMHsw-ziq-N1WLq_7dyVJdYno9A8Muh5Qg&e=

Thanks a lot!

Best regards

Airship-discuss mailing list
Airship-discuss at lists.airshipit.org

More information about the Airship-discuss mailing list