Re: [Airship-discuss] Airship in a bottle install failure...

10 Dec 2018

      Hi there Alex.

Thanks for the reply.
...
From your logs it seems to me like  maas-db-init is not able to connect to postgres DB with psql client to the other container. (clients should be listed by IP in pg_hba.conf, wildcards should be possible....)
I will try another install from

Thanks

________________________________ From: Alex Arnoldy <alex.arnoldy@suse Sent: Monday, December 10, 2018 4:26 PM To: Balsiger Daniel, INI-EAI-INO-MBL; Subject: RE: Airship in a bottle

Hello Daniel,

I had launched the same thing but

root@airship:~# kubectl get pods

NAMESPACE     NAME

kube-system   auxiliary-etcd-airship

kube-system   bootstrap-armada-airship

kube-system   calico-etcd-airship

kube-system   calico-etcd-anchor-nqntm

kube-system   calico-kube-controllers-6d

kube-system   calico-node-2sgkk

kube-system   calico-settings-bqs5v

kube-system   coredns-d4587b7f8-bbpr6

kube-system   coredns-d4587b7f8-tdl8v

kube-system   coredns-d4587b7f8-ts9lr

kube-system   haproxy-airship

kube-system   ingress-error-pages-5ccf96bf7d-8q6g5

kube-system   ingress-fmrmk

kube-system   kubernetes-apiserver-airship

kube-system   kubernetes-apiserver-anchor-rkfpz

kube-system   kubernetes-controller-manager-airship

kube-system   kubernetes-controller-mana

kube-system   kubernetes-etcd-airship

kube-system   kubernetes-etcd-anchor-hzcrz

kube-system   kubernetes-proxy-994kg

kube-system   kubernetes-scheduler-airship

kube-system   kubernetes-scheduler-anchor-gsqtj

kube-system   nfs-provisioner-7799d64d59-g2g6n

kube-system   tiller-deploy-7d88c6f956-9jjk7

ucp           airship-ucp-keystone-memca

ucp           airship-ucp-rabbitmq-rabbitmq-0

ucp           ingress-6cd5b89d5d-xx592

ucp           ingress-error-pages-5c97bb46bb-ljmw6

ucp           keystone-api-7657986b8c-b49r6

ucp           keystone-bootstrap-8494p

ucp           keystone-credential-setup-r5twm

ucp           keystone-db-init-pxlzr

ucp           keystone-db-sync-zx665

ucp           keystone-domain-manage-rbfl5

ucp           keystone-fernet-rotate-1544356800-kcgg9

ucp           keystone-fernet-rotate-1544400000-78qc8

ucp           keystone-fernet-rotate-1544443200-v8bkn

ucp           keystone-fernet-setup-srrqj

ucp           keystone-rabbit-init-x4stm

ucp           maas-bootstrap-admin-user-26lhf

ucp           maas-db-init-v7z6r

ucp           maas-db-sync-5c24z

ucp           maas-export-api-key-zhfxp

ucp           maas-import-resources-j6tzd

ucp           maas-rack-0

ucp           maas-region-0

ucp           mariadb-ingress-6c4f9c76f-sg8cx

ucp           mariadb-ingress-6c4f9c76f-sz26m

ucp           mariadb-ingress-error-page

ucp           mariadb-server-0

ucp           postgresql-0

The only output from that pod is this:

root@airship:~# kubectl logs -n

+ 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

+ DB_COMMAND='SELECT 1 FROM pg_database

+ [[ ! -z '' ]]

+ grep -q 1

+ psql -h postgresql.ucp.svc.cluster.local

psql: FATAL:  no pg_hba.conf entry

+ pgsql_superuser_cmd 'CREATE DATABASE

+ DB_COMMAND='CREATE DATABASE maasdb'

+ [[ ! -z '' ]]

+ psql -h postgresql.ucp.svc.cluster.local

psql: FATAL:  no pg_hba.conf entry

Unfortunately, I haven’t been

Best,

--Alex.

Alex Arnoldy Software Defined Infrastructure SUSE Alex.Arnoldy@SUSE.com<mailto:Alex.Arn (P) +1 (408) 828-9797

From: Balsiger Daniel, INI-EAI-INO-MBL Sent: Monday, December 10, 2018 6:32 AM To: airship-discuss@lists.airshipit.org Subject: [Airship-discuss] Airship

Hi there Airshippers

I wanted to try installing airhip-in-a-bottle

--snip

sudo -i

mkdir -p /root/deploy && cd "$_"

git clone  <Daniel.Balsiger@swisscom.com> in a bottle install failure... in a fresh Ubuntu16.04 VM running on OpenStack over the weekend. I followed the instructions on airshipit.org ://github.com/openstack/airship-in-a-bottle">https://github.com/openstack/airship-in-a-bottle fests/dev_single_node 2 days so I think something went wrong. listing running/restarted containers (I think postgres is the one not coming up properly) READY     STATUS      RESTARTS   AGE 3/3       Running     0          2d 4/4       Running     0          2d 1/1       Running     0          2d 1/1       Running     0          2d 5997c8c4-zxftw      1/1       Running     0          2d 2/2       Running     0          2d 0/1       Completed   0          2d 1/1       Running     0          2d 1/1       Running     0          2d 1/1       Running     0          2d 1/1       Running     0          2d 1/1       Running     0          2d 1/1       Running     0          2d 1/1       Running     0          2d 1/1       Running     0          2d 1/1       Running     1          2d ger-anchor-2wsg8    1/1       Running     0          2d 1/1       Running     0          2d 1/1       Running     0          2d 1/1       Running     0          2d 1/1       Running     1          2d 1/1       Running     0          2d 1/1       Running     0          2d 1/1       Running     0          2d 1/1       Running     0          2d 1/1       Running     0          2d 0/1       Running     0          2d 0/1       Running     0          2d s-5dd6fbb75-89qmx   1/1       Running     0          2d 0/1       Running     0          2d 1/1       Running     1          2d problem or (even better) a solution for it? or commit?