etcd looses 'snap connections' on reboot

Bug #1958541 reported by David Negreira
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Etcd Charm
New
Undecided
Unassigned

Bug Description

I have seen this in two different infrastructures, they were both running etcd on latest/stable channel (version 3.4.5) and running in a LXD container deployed by juju.

We first figured that this showing on the journalctl logs the following error message:
listen tcp 0.0.0.0:2380: socket: permission denied

Then we figured that the snap connections were missing, because when we were running `snap connections` nothing is returned related to the etcd unit.

The fix was to manually add the connections again with:

- sudo snap connect etcd:network-bind :network-bind
- sudo snap connect etcd:home :home

The issue seems to happen (ocasionally) after a reboot, but was unable to reproduce this yet on a test environment, but happened in a really short time within two different infrastructures.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.