Airship in a bottle installation
Hello airship community, currently evaluating openstack deployments tools available, I have trouble running airship in a bottle script my setup is as follow : A ubuntu 16.04 vm with nat networking 30GB RAM 100GB disk space 8vcpu provisioned with virtmanager / kvm on a fresh baremetal server running Ubuntu 20.04 LTS. The error of airshipinabottle.sh is : The connection to the server 127.0.0.1:6553 was refused - did you specify the right host or port? The kubelet error include ( with journalctl ) : aiab kubelet[9641]: E0622 15:50:49.435913 9641 kubelet.go:2263] node "aiab" not found Systemctl status kubelet show : /opt/kubernetes/bin/kubelet --config=/etc/kubernetes/kubelet/config.yaml --dynamic-config-dir=/etc/kubernetes/kubelet/dynamic-config --hostname-override=aiab --kubeconfig=/etc/kubernetes/kubeconfig --node-ip=192.168.122.187 --cni-bin-dir=/opt/cni/bin --cni-conf-dir=/etc/cni/net.d --network-plugin=cni --seccomp-profile-root=/var/lib/kubelet/seccomp --pod-infra-container-image= gcr.io/google-containers/pause-amd64:3.1 Do you have any idea what I am not doing right ? Thank you
Hello Swann, have you already found a solution to the problem? Thanks and Regards Dominik Bender
Hello, I went through the deployment guide [0] as specified, but the Genesis deployment fails. No containers are created while the script is running. I suspect the problem is the lack of the calico conflist in /etc/cni/net.d (this directory is not created). This triggers a number of consequential errors. What's wrong? The hostname match with the manifests. *Output of the script until the timeout *The connection to the server 127.0.0.1:6553 was refused - did you specify the right host or port? *Docker error* Not continuing with pull after error: context canceled *Partial syslog errors:* ... cni.go:237] Unable to update cni config: no networks found in /etc/cni/net.d hostport_manager.go:69] The binary conntrack is not installed, this can cause failures in network connection cleanup. k8s.io/kubernetes/pkg/kubelet/config/apiserver.go:46: Failed to list *v1.Pod: Get https://127.0.0.1:6553/api/v1/pods?fieldSelector=spec.nodeName... kubelet config controller: could not get Node "loc1-rack1-srv1", will not sync status, error: Get https://127.0.0.1:6553/api/v1/nodes/loc1-rack1-srv1: dial tcp ... If necessary, I can provide the entire syslog. *Treasuremap branch* seaworthy master *Genesis kernel* linux-image-4.15.0-46-generic *Genesis Hardware *R620, 2x E5 2680v2, 256GB, 480G SSD R1, 1,6TB UCP-Ceph-OSD [0] https://airship-treasuremap.readthedocs.io/en/latest/authoring_and_deploymen... Thanks and Regards Dominik Bender
Hello Community, short update, we tested: * *master* 1. no containers came up 2. The connection to the server 127.0.0.1:6553 was refused 3. Unable to update cni config: no networks found * *master v1.7* 1. containers came up 2. Unable to connect to the server: EOF / failed to "StartContainer" for "kube-apiserver" with CrashLoopBackOff 3. etcdmain: error verifying flags, --initial-advertise-peer-urls "https://:2380" must be "host:port" (unexpected empty host (https://:2380)) Anyone have an idea? BR, Dominik Bender Am 16.11.2020 um 01:38 schrieb Dominik Bender | db IT Solutions:
Hello,
I went through the deployment guide [0] as specified, but the Genesis deployment fails. No containers are created while the script is running. I suspect the problem is the lack of the calico conflist in /etc/cni/net.d (this directory is not created). This triggers a number of consequential errors. What's wrong? The hostname match with the manifests.
*Output of the script until the timeout *The connection to the server 127.0.0.1:6553 was refused - did you specify the right host or port?
*Docker error* Not continuing with pull after error: context canceled
*Partial syslog errors:* ... cni.go:237] Unable to update cni config: no networks found in /etc/cni/net.d hostport_manager.go:69] The binary conntrack is not installed, this can cause failures in network connection cleanup. k8s.io/kubernetes/pkg/kubelet/config/apiserver.go:46: Failed to list *v1.Pod: Get https://127.0.0.1:6553/api/v1/pods?fieldSelector=spec.nodeName... kubelet config controller: could not get Node "loc1-rack1-srv1", will not sync status, error: Get https://127.0.0.1:6553/api/v1/nodes/loc1-rack1-srv1: dial tcp ... If necessary, I can provide the entire syslog.
*Treasuremap branch* seaworthy master
*Genesis kernel* linux-image-4.15.0-46-generic
*Genesis Hardware *R620, 2x E5 2680v2, 256GB, 480G SSD R1, 1,6TB UCP-Ceph-OSD
[0] https://airship-treasuremap.readthedocs.io/en/latest/authoring_and_deploymen...
Thanks and Regards Dominik Bender
_______________________________________________ Airship-discuss mailing list Airship-discuss@lists.airshipit.org http://lists.airshipit.org/cgi-bin/mailman/listinfo/airship-discuss
participants (2)
-
Dominik Bender | db IT Solutions
-
Swann Legras