We see the behavior when the microshift.service is showing errors connecting to the etcd:

Aug 20 09:38:22 hostname microshift[1011453]: etcd W0820 09:38:22.049043 1011453 logging.go:59] [core] [Channel #1 SubChannel #2] grpc: addrConn.createTransport failed to connect to {Addr: "localhost:2379", ServerName: "localhost:2379", }. Err: connection error: desc = "transport: authentication handshake failed: context deadline exceeded"

However, the microshift-etcd.scope is fine.

● microshift-etcd.scope - /usr/bin/microshift-etcd run
     Loaded: loaded (/run/systemd/transient/microshift-etcd.scope; transient)
  Transient: yes
     Active: active (running) since Thu 2024-08-22 05:01:05 UTC; 8s ago
      Tasks: 8 (limit: 203135)
     Memory: 125.8M
        CPU: 10.156s
     CGroup: /system.slice/microshift-etcd.scope
             └─1267087 /usr/bin/microshift-etcd run

And the logs do not present any error.

We saw this issue once, where the microshift service is not able to start due to the microshift-etcd.scope.

We are checking if the etcd is running and listening normally.

    

$ cat microshift_version
MicroShift Version: 4.14.32
Base OCP Version: 4.14.32

Proxy on CRIO is in place.
    

- I was not able to reproduce that.
    

    1.
    2.
    3.