Hi Loïc & Dimitrios,

Shoot, sorry you guys hit this.  This looks like the Airship-in-a-Bottle single node dev site may have gotten stale.  We have a few different sets of YAMLs that should be aligned to one another to keep this from happening; I’ve captured the issue and proposed resolution in this story[1].  If you’d like to help with this it would be very much appreciated :-), and if anyone has some time to get the AiaB single-node dev site definition trued up in the meantime that would be valuable too.

For a MaaS-free dev deployment, I suggest looking at the Airskiff [2] deployment scripts.  These deploy the software provisioning components (no MaaS, Drydock, Promenade) in a bring-your-own-k8s setup.  Dwalt has a patchset in progress to align these site manifests fully to the treasuremap reference globals, per the story.

[1]: https://storyboard.openstack.org/#!/story/2005123

[2]: https://airship-treasuremap.readthedocs.io/en/latest/airskiff.html

Thanks,

Matt

From: Loic Le Gal <l.legal.astellia@gmail.com>
Sent: Wednesday, March 6, 2019 9:49 AM
To: airship-discuss@lists.airshipit.org
Subject: Re: [Airship-discuss] Airship-In-A-Bottle_Dev-Single-Node_No-Proxy-Environment_Mass-Ingress_Error

Hi Airshipers,

Same issue for me, going back to previous commit (ad53fbf5c312929e8d0873e5095c5a0d1dcdd7f5), but another problem arise with maas-import-resources. I will open new thread if can't fix.

Why is maas required even for AiaB as we don't have any baremetal involved ??

BR,

Loïc