You have been subscribed to a public bug: Steps to reproduce: LXD setup and juju installation are done following these instructions https://ubuntu.com/kubernetes/docs/install-local
Kubernetes Core bundle is installed as described here https://jaas.ai/kubernetes-core with juju deploy cs:bundle/kubernetes-core-1069 Expected result - 1 master and 1 worker node. Actual result - just 1 node. # juju status Model Controller Cloud/Region Version SLA Timestamp k8s localhost-localhost localhost/localhost 2.8.1 unsupported 11:28:37+02:00 App Version Status Scale Charm Store Rev OS Notes containerd 1.3.3 active 2 containerd jujucharms 80 ubuntu easyrsa 3.0.1 active 1 easyrsa jujucharms 318 ubuntu etcd 3.3.19 active 1 etcd jujucharms 521 ubuntu flannel 0.11.0 active 2 flannel jujucharms 492 ubuntu kubernetes-master 1.18.6 active 1 kubernetes-master jujucharms 850 ubuntu exposed kubernetes-worker 1.18.6 active 1 kubernetes-worker jujucharms 682 ubuntu exposed Unit Workload Agent Machine Public address Ports Message easyrsa/0* active idle 0/lxd/0 10.123.107.225 Certificate Authority connected. etcd/0* active idle 0 10.70.13.93 2379/tcp Healthy with 1 known peer kubernetes-master/0* active idle 0 10.70.13.93 6443/tcp Kubernetes master running. containerd/1 active idle 10.70.13.93 Container runtime available flannel/1 active idle 10.70.13.93 Flannel subnet 10.1.67.1/24 kubernetes-worker/0* active idle 1 10.70.13.168 80/tcp,443/tcp Kubernetes worker running. containerd/0* active idle 10.70.13.168 Container runtime available flannel/0* active idle 10.70.13.168 Flannel subnet 10.1.99.1/24 Machine State DNS Inst id Series AZ Message 0 started 10.70.13.93 juju-62238e-0 bionic Running 0/lxd/0 started 10.123.107.225 juju-62238e-0-lxd-0 bionic Container started 1 started 10.70.13.168 juju-62238e-1 bionic Running # kubectl get nodes NAME STATUS ROLES AGE VERSION juju-62238e-1 Ready <none> 74m v1.18.6 Output about pods on the cluster # kubectl get pods No resources found in default namespace. root@m8360041:~# kubectl get pods -A NAMESPACE NAME READY STATUS RESTARTS AGE ingress-nginx-kubernetes-worker default-http-backend-kubernetes-worker-6fc4c9975-2dwsc 1/1 Running 0 41m ingress-nginx-kubernetes-worker nginx-ingress-controller-kubernetes-worker-qmz2j 1/1 Running 0 41m kube-system coredns-7f748b899d-dc5hx 1/1 Running 0 42m kube-system kube-state-metrics-69f474f8cb-9s85h 0/1 CrashLoopBackOff 26 42m kube-system metrics-server-v0.3.6-5c9f85bbd6-8mksp 2/2 Running 0 42m kubernetes-dashboard dashboard-metrics-scraper-78d587b6b-2ggmz 0/1 CrashLoopBackOff 26 42m kubernetes-dashboard kubernetes-dashboard-76b6648555-x4fng 1/1 Running 0 42m ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Skipper Bug Screeners (skipper-screen-team) Status: New ** Tags: architecture-s39064 bugnameltc-187023 severity-high targetmilestone-inin2004 -- [UBUNTU 20.04] kubernetes-core is not fully installed on s390x https://bugs.launchpad.net/bugs/1889763 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
