Hi Matt


Thanks for the quick reply. No, no proxy is in place.

VM has a private tenant network address and one floating IP assigned.


The floating IP is regularly NATed (Masquerade) to the outside world.

I access the VM by floating IP via SSH.


KR Daniel

From: MCEUEN, MATT <MM9745@att.com>
Sent: Monday, December 10, 2018 4:29 PM
To: Balsiger Daniel, INI-EAI-INO-MBL; airship-discuss@lists.airshipit.org
Subject: RE: Airship in a bottle install failure...
 

Hi Daniel,

 

Are you running from behind a proxy?  A few fixes have gone in recently, so I want to try to reproduce your setup.

 

Thanks,

Matt

 

From: Balsiger Daniel, INI-EAI-INO-MBL <Daniel.Balsiger@swisscom.com>
Sent: Monday, December 10, 2018 8:32 AM
To: airship-discuss@lists.airshipit.org
Subject: [Airship-discuss] Airship in a bottle install failure...

 

Hi there Airshippers

 

I wanted to try installing airhip-in-a-bottle in a fresh Ubuntu16.04 VM running on OpenStack over the weekend. I followed the instructions on airshipit.org

 

--snip

sudo -i
mkdir -p /root/deploy && cd "$_"
git clone https://github.com/openstack/airship-in-a-bottle
cd /root/deploy/airship-in-a-bottle/manifests/dev_single_node
./airship-in-a-bottle.sh

--snip

 

The script is still running after 2 days so I think something went wrong.

The output is repeating itself, listing running/restarted containers (I think postgres is the one not coming up properly)

--snip

NAMESPACE     NAME                                          READY     STATUS      RESTARTS   AGE
kube-system   auxiliary-etcd-airship                        3/3       Running     0          2d
kube-system   bootstrap-armada-airship                      4/4       Running     0          2d
kube-system   calico-etcd-airship                           1/1       Running     0          2d
kube-system   calico-etcd-anchor-2jrqf                      1/1       Running     0          2d
kube-system   calico-kube-controllers-6d5997c8c4-zxftw      1/1       Running     0          2d
kube-system   calico-node-l885v                             2/2       Running     0          2d
kube-system   calico-settings-kbq79                         0/1       Completed   0          2d
kube-system   coredns-d4587b7f8-7wlpm                       1/1       Running     0          2d
kube-system   coredns-d4587b7f8-98t62                       1/1       Running     0          2d
kube-system   coredns-d4587b7f8-frx5w                       1/1       Running     0          2d
kube-system   haproxy-airship                               1/1       Running     0          2d
kube-system   ingress-8w29l                                 1/1       Running     0          2d
kube-system   ingress-error-pages-5ccf96bf7d-jsrww          1/1       Running     0          2d
kube-system   kubernetes-apiserver-airship                  1/1       Running     0          2d
kube-system   kubernetes-apiserver-anchor-55x59             1/1       Running     0          2d
kube-system   kubernetes-controller-manager-airship         1/1       Running     1          2d
kube-system   kubernetes-controller-manager-anchor-2wsg8    1/1       Running     0          2d
kube-system   kubernetes-etcd-airship                       1/1       Running     0          2d
kube-system   kubernetes-etcd-anchor-64wgx                  1/1       Running     0          2d
kube-system   kubernetes-proxy-9s68d                        1/1       Running     0          2d
kube-system   kubernetes-scheduler-airship                  1/1       Running     1          2d
kube-system   kubernetes-scheduler-anchor-npmn7             1/1       Running     0          2d
kube-system   nfs-provisioner-7799d64d59-scgdc              1/1       Running     0          2d
ucp           airship-ucp-rabbitmq-rabbitmq-0               1/1       Running     0          2d
ucp           ingress-6cd5b89d5d-gp98m                      1/1       Running     0          2d
ucp           ingress-error-pages-5c97bb46bb-zq5cw          1/1       Running     0          2d
ucp           mariadb-ingress-6c4f9c76f-bjd99               0/1       Running     0          2d
ucp           mariadb-ingress-6c4f9c76f-xjrn9               0/1       Running     0          2d
ucp           mariadb-ingress-error-pages-5dd6fbb75-89qmx   1/1       Running     0          2d
ucp           mariadb-server-0                              0/1       Running     0          2d
ucp           postgresql-0                                  1/1       Running     1          2d
--snip

 

Anybody out there with the same problem or (even better) a solution for it?

Should I pick a particular branch or commit?

Any help is appreciated.

 

Best Regards, Daniel