Hello Daniel,

I had launched the same thing but then got pulled away from it and totally forgot to check it. I thought I’d be able to tell you I got it running, but I don’t think that’s the case. For my installation all of the containers are either Running or Completed except for the following:

ucp maas-bootstrap-admin-user-26lhf 0/1 Init:0/1 0 3d 10.97.196.132 airship

ucp maas-db-init-v7z6r 0/1 CrashLoopBackOff 953 3d 10.97.196.143 airship

ucp maas-db-sync-5c24z 0/1 Init:0/1 0 3d 10.97.196.162 airship

ucp maas-export-api-key-zhfxp 0/1 Init:0/1 0 3d 10.97.196.147 airship

ucp maas-import-resources-j6tzd 0/1 Init:0/1 0 3d 10.97.196.152 airship

ucp maas-rack-0 0/1 Init:0/1 0 3d 172.16.231.60 airship

ucp maas-region-0 0/1 Init:0/1 0 3d 10.97.196.146 airship

The only output from the maas-db-init pod is this:

root@airship:~# kubectl logs -n ucp maas-db-init-v7z6r

+ export HOME=/tmp

+ HOME=/tmp

+ [[ ! -v DB_HOST ]]

+ [[ ! -v ROOT_DB_USER ]]

+ [[ ! -v PGPASSWORD ]]

+ [[ ! -v USER_DB_USER ]]

+ [[ ! -v USER_DB_PASS ]]

+ [[ ! -v USER_DB_NAME ]]

+ echo 'Got DB connection info'

Got DB connection info

+ pgsql_superuser_cmd 'SELECT 1 FROM pg_database WHERE datname = '\''maasdb'\'''

+ DB_COMMAND='SELECT 1 FROM pg_database WHERE datname = '\''maasdb'\'''

+ [[ ! -z '' ]]

+ grep -q 1

+ psql -h postgresql.ucp.svc.cluster.local -p 5432 -U postgres '--command=SELECT 1 FROM pg_database WHERE datname = '\''maasdb'\'''

psql: FATAL: no pg_hba.conf entry for host "10.97.196.143", user "postgres", database "postgres", SSL off

+ pgsql_superuser_cmd 'CREATE DATABASE maasdb'

+ DB_COMMAND='CREATE DATABASE maasdb'

+ [[ ! -z '' ]]

+ psql -h postgresql.ucp.svc.cluster.local -p 5432 -U postgres '--command=CREATE DATABASE maasdb'

psql: FATAL: no pg_hba.conf entry for host "10.97.196.143", user "postgres", database "postgres", SSL off

Unfortunately, I haven’t been able to troubleshoot this any further.

Best,

--Alex.

Alex Arnoldy
Software Defined Infrastructure Solutions Architect
SUSE
Alex.Arnoldy@SUSE.com
(P) +1 (408) 828-9797

From: Balsiger Daniel, INI-EAI-INO-MBL <Daniel.Balsiger@swisscom.com>
Sent: Monday, December 10, 2018 6: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