Juju cannot work after renew the microk8s certificate

juju
1

juju version: 3.2.0-genericlinux-amd64 MAAS version: **2.7.3 (8290-g.ebe2b9884)

Problem: Two days ago, the microk8s certificate was expired. The kubectl command cannot work. By using the below command, the certificate was renewed and the k8s can work again. However, one day later, the juju ssh command cannot work. If I run juju status, which is saying the below error.

root@maas8:~# juju status

ERROR No controllers registered.

Please either create a new controller using “juju bootstrap” or connect to another controller that you have been given access to using “juju register”.

root@maas8:~# juju list-clouds

Only clouds with registered credentials are shown.

There are more clouds, use --all to see them.

You can bootstrap a new controller using one of these clouds…

Clouds available on the client:

Cloud Regions Default Type Credentials Source Description

auto-simulators 0 k8s 0 built-in A local Kubernetes context

auto-simulators-maas8 0 k8s 0 built-in A local Kubernetes context

localhost 1 localhost lxd 0 built-in LXD Container Hypervisor

Could anyone know this issue, and how to fix it? Is it possible to fix it instead of creating a new controller? Thank you so much.

BRs, Tingting

2

I’ve checked and the controller is running as below.

Using ‘juju ssh’ won’t work. I use SSH into the controller. ssh ubuntu@<ip address> However, nothing valued finding in the logs in /var/log/juju.

ubuntu@juju-controller-VM84:/var/log/juju$ sudo service jujud-machine-0 status ● jujud-machine-0.service - juju agent for machine-0 Loaded: loaded (/etc/systemd/system/jujud-machine-0.service; enabled; vendor preset: enabled) Active: active (running) since Mon 2022-05-23 14:41:39 UTC; 1 years 0 months ago Main PID: 1056 (bash) Tasks: 21 (limit: 4915) CGroup: /system.slice/jujud-machine-0.service ├─1056 bash /etc/systemd/system/jujud-machine-0-exec-start.sh └─1182 /var/lib/juju/tools/machine-0/jujud machine --data-dir /var/lib/juju --machine-id 0 --debug

                 May 23 14:41:39 juju-controller-VM84 systemd[1]: Started juju agent for machine-0.

                           

            ubuntu@openstack-controller-VM84:~$ sudo service jujud-machine-0 status
           ● jujud-machine-0.service - juju agent for machine-0
           Loaded: loaded (/etc/systemd/system/jujud-machine-0.service; enabled; vendor preset: enabled)
                Active: active (running) since Wed 2022-11-23 09:14:23 UTC; 6 months 8 days ago
          Main PID: 1442 (bash)
             Tasks: 24 (limit: 4915)
           CGroup: /system.slice/jujud-machine-0.service
                   ├─1442 bash /etc/systemd/system/jujud-machine-0-exec-start.sh
                   └─1471 /var/lib/juju/tools/machine-0/jujud machine --data-dir /var/lib/juju --machine-id 0 --debug

           Nov 23 09:14:23 openstack-controller-VM84 systemd[1]: Started juju agent for machine-0.