Migrating from etcd 2.x to 3.0 via the snap path does a transformation on the config data and leaves behind a etcd.conf.2x file in $SNAP_COMMON.
When issuing a snap revert on the snap to roll back the cluster appears broken at first glance, but if you restore operation using the etcd.conf.2x backup file; the unit is able to self-start using the 'last known' configuration.
Migrating from etcd 2.x to 3.0 via the snap path does a transformation on the config data and leaves behind a
etcd.conf.2xfile in$SNAP_COMMON.When issuing a
snap reverton the snap to roll back the cluster appears broken at first glance, but if you restore operation using theetcd.conf.2xbackup file; the unit is able to self-start using the 'last known' configuration.