Public bug reported: I have openstack queens setup and I have found following issues in creation of stack using fedora-automichost-29.
1. /var/run/kubernetes/ do not have permission for kube user to store certificate, kube-apiserver service failed to start due to it. [root@my-k8-cluster1-k4czdt6vc6vi-master-0 kube-apiserver.0]# /usr/bin/runc --systemd-cgroup run 'kube-apiserver' I0526 13:49:16.515448 1 server.go:121] Version: v1.9.3 error creating self-signed certificates: open /var/run/kubernetes/apiserver.crt: permission denied [root@my-k8-cluster1-k4czdt6vc6vi-master-0 2. wc-notify.service do not start as hostname,address not configured May 26 14:53:34 my-k8-cluster1-k4czdt6vc6vi-master-0.novalocal wc-notify[4187]: #!/bin/bash -v May 26 14:53:34 my-k8-cluster1-k4czdt6vc6vi-master-0.novalocal wc-notify[4187]: until curl -sf "http://127.0.0.1:8080/healthz";; do May 26 14:53:34 my-k8-cluster1-k4czdt6vc6vi-master-0.novalocal wc-notify[4187]: echo "Waiting for Kubernetes API..." May 26 14:53:34 my-k8-cluster1-k4czdt6vc6vi-master-0.novalocal wc-notify[4187]: sleep 5 May 26 14:53:34 my-k8-cluster1-k4czdt6vc6vi-master-0.novalocal wc-notify[4187]: done May 26 14:53:34 my-k8-cluster1-k4czdt6vc6vi-master-0.novalocal wc-notify[4187]: okcurl -i -X POST -H 'X-Auth-Token: gAAAAABezRtp3y_nVA8HFKkMscsEVa-RT4EEJWJnXQb4L876sMW0KxBx6yvHXH1dJK7nQ7CmKhdcuVNmzHNM57qdK8jSMyxccYn_izpbe7Bu3wbNN-GL6u3Xx6iwAotfZ52z1FHmNxnCsJNVuiR2sxVnzXsr3Q834VWPD4b3RR1ECHhwTOwsDQA' -H 'Content-Type: application/json' -H 'Accept: application/json' http://controller:8004/v1/48b376e2541846068fdb8ef2b79d271e/stacks/my-k8-cluster1-k4czdt6vc6vi-kube_masters-xeikxcjmuipw-0-3qfz22bpb3we/5f945567-eae3-4a59-a070-6d5dd9e6f0d3/resources/master_wait_handle/signal --data-binary '{"status": "SUCCESS"}' May 26 14:53:34 my-k8-cluster1-k4czdt6vc6vi-master-0.novalocal wc-notify[4187]: % Total % Received % Xferd Average Speed Time Time Time Current May 26 14:53:34 my-k8-cluster1-k4czdt6vc6vi-master-0.novalocal wc-notify[4187]: Dload Upload Total Spent Left Speed May 26 14:53:34 my-k8-cluster1-k4czdt6vc6vi-master-0.novalocal wc-notify[4187]: [123B blob data] May 26 14:53:34 my-k8-cluster1-k4czdt6vc6vi-master-0.novalocal audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=wc-notify comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed' May 26 14:53:34 my-k8-cluster1-k4czdt6vc6vi-master-0.novalocal systemd[1]: wc-notify.service: Main process exited, code=exited, status=6/NOTCONFIGURED May 26 14:53:34 my-k8-cluster1-k4czdt6vc6vi-master-0.novalocal systemd[1]: Failed to start Notify Heat. -- Subject: Unit wc-notify.service has failed -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit wc-notify.service has failed. -- -- The result is failed. ** Affects: magnum (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880709 Title: Magnum k8 stack failing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/magnum/+bug/1880709/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
