MicroStack breaks once the IP address of the workstation changes

[Tytus Kurek]

I noticed that MicroStack breaks once the IP address of the workstation changes.

I had MicroStack installed according to the following tutorial: https://ubuntu.com/tutorials/microstack-get-started#4-interact-with-openstack . The IP address of my wireless wlp0s20f3 interface was 192.168.1.111/24 and I could see OpenStack services registered at this address:

guardian@Guardian-Inspiron:~$ ip addr
...
2: wlp0s20f3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 24:41:8c:ac:8e:b5 brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.111/24 brd 192.168.1.255 scope global dynamic noprefixroute wlp0s20f3
       valid_lft 77409sec preferred_lft 77409sec
    inet6 fe80::28b0:e707:5f46:86ce/64 scope link noprefixroute
       valid_lft forever preferred_lft forever
...

guardian@Guardian-Inspiron:~$ microstack.openstack catalog list
+-----------+-----------+---------------------------------------------------------------------------+
| Name | Type | Endpoints |
+-----------+-----------+---------------------------------------------------------------------------+
| neutron | network | microstack |
| | | internal: http://192.168.1.111:9696 |
| | | microstack |
| | | public: http://192.168.1.111:9696 |
| | | microstack |
| | | admin: http://192.168.1.111:9696 |
| | | |
| glance | image | microstack |
| | | internal: http://192.168.1.111:9292 |
| | | microstack |
| | | admin: http://192.168.1.111:9292 |
| | | microstack |
| | | public: http://192.168.1.111:9292 |
| | | |
| nova | compute | microstack |
| | | internal: http://192.168.1.111:8774/v2.1 |
| | | microstack |
| | | admin: http://192.168.1.111:8774/v2.1 |
| | | microstack |
| | | public: http://192.168.1.111:8774/v2.1 |
| | | |
| keystone | identity | microstack |
| | | public: http://192.168.1.111:5000/v3/ |
| | | microstack |
| | | internal: http://192.168.1.111:5000/v3/ |
| | | microstack |
| | | admin: http://192.168.1.111:5000/v3/ |
| | | |
| placement | placement | microstack |
| | | admin: http://192.168.1.111:8778 |
| | | microstack |
| | | internal: http://192.168.1.111:8778 |
| | | microstack |
| | | public: http://192.168.1.111:8778 |
| | | |
| cinderv2 | volumev2 | microstack |
| | | public: http://192.168.1.111:8776/v2/b4601193c91d4d39bd26f2689c0c3785 |
| | | microstack |
| | | internal: http://192.168.1.111:8776/v2/b4601193c91d4d39bd26f2689c0c3785 |
| | | microstack |
| | | admin: http://192.168.1.111:8776/v2/b4601193c91d4d39bd26f2689c0c3785 |
| | | |
| cinderv3 | volumev3 | microstack |
| | | admin: http://192.168.1.111:8776/v3/b4601193c91d4d39bd26f2689c0c3785 |
| | | microstack |
| | | internal: http://192.168.1.111:8776/v3/b4601193c91d4d39bd26f2689c0c3785 |
| | | microstack |
| | | public: http://192.168.1.111:8776/v3/b4601193c91d4d39bd26f2689c0c3785 |
| | | |
+-----------+-----------+---------------------------------------------------------------------------+

However, when the IP address of my wlp0s20f3 interface changed to 192.168.1.12/24 I was no longer able to log in to the Horizon dashboard. I could see the following message in the keystone logs:

https://pastebin.ubuntu.com/p/kvv5wVx5Vz/

I tried restarting MicroStack, but it failed:

guardian@Guardian-Inspiron:~$ sudo snap restart microstack
error: cannot perform the following tasks:
- Run service command "restart" for services ["cinder-backup" "cinder-scheduler" "cinder-uwsgi" "cinder-volume" "cluster-uwsgi" "external-bridge" "filebeat" "glance-api" "horizon-uwsgi" "iscsid" "keystone-uwsgi" "libvirtd" "load-modules" "memcached" "mysqld" "neutron-api" "neutron-ovn-metadata-agent" "nginx" "nova-api" "nova-api-metadata" "nova-compute" "nova-conductor" "nova-scheduler" "nova-spicehtml5proxy" "nrpe" "ovn-controller" "ovn-northd" "ovn-ovsdb-server-nb" "ovn-ovsdb-server-sb" "ovs-vswitchd" "ovsdb-server" "placement-uwsgi" "rabbitmq-server" "setup-lvm-loopdev" "target" "telegraf" "virtlogd"] of snap "microstack" ([start snap.microstack.setup-lvm-loopdev.service] failed with exit status 1: Job for snap.microstack.setup-lvm-loopdev.service failed because the control process exited with error code.
See "systemctl status snap.microstack.setup-lvm-loopdev.service" and "journalctl -xe" for details.
)

I tried changing the IP address of the wlp0s20f3 interface back to 192.168.1.111/24 and restarting MicroStack, but it failed with the same error.

The "systemctl status snap.microstack.setup-lvm-loopdev.service" results with the following output:

guardian@Guardian-Inspiron:~$ sudo systemctl status snap.microstack.setup-lvm-loopdev.service
● snap.microstack.setup-lvm-loopdev.service - Service for snap application microstack.setup-lvm-loopdev
     Loaded: loaded (/etc/systemd/system/snap.microstack.setup-lvm-loopdev.service; disabled; vendor preset: enabled)
     Active: failed (Result: exit-code) since Mon 2021-09-06 09:05:39 CEST; 9min ago
    Process: 1121827 ExecStart=/usr/bin/snap run microstack.setup-lvm-loopdev (code=exited, status=5)
   Main PID: 1121827 (code=exited, status=5)

wrz 06 09:05:39 Guardian-Inspiron microstack.setup-lvm-loopdev[1121861]: ++ snapctl get config.cinder.lvm-backend-volume-group
wrz 06 09:05:39 Guardian-Inspiron microstack.setup-lvm-loopdev[1121827]: + cinder_volumes_vg=cinder-volumes
wrz 06 09:05:39 Guardian-Inspiron microstack.setup-lvm-loopdev[1121865]: ++ snapctl get config.cinder.setup-loop-based-cinder-lvm-backend
wrz 06 09:05:39 Guardian-Inspiron microstack.setup-lvm-loopdev[1121827]: + '[' false = true ']'
wrz 06 09:05:39 Guardian-Inspiron microstack.setup-lvm-loopdev[1121827]: + lvchange -a y cinder-volumes
wrz 06 09:05:39 Guardian-Inspiron microstack.setup-lvm-loopdev[1121871]: Volume group "cinder-volumes" not found
wrz 06 09:05:39 Guardian-Inspiron microstack.setup-lvm-loopdev[1121871]: Cannot process volume group cinder-volumes
wrz 06 09:05:39 Guardian-Inspiron systemd[1]: snap.microstack.setup-lvm-loopdev.service: Main process exited, code=exited, status=5/NOTINSTALLED
wrz 06 09:05:39 Guardian-Inspiron systemd[1]: snap.microstack.setup-lvm-loopdev.service: Failed with result 'exit-code'.
wrz 06 09:05:39 Guardian-Inspiron systemd[1]: Failed to start Service for snap application microstack.setup-lvm-loopdev.

[Billy Olsen (billy-olsen)]

Yes, this is a challenge in an environment where DHCP is used and the IP addresses can change. This is due to IP information being recorded in a variety of services. You should use a static IP address or configure your router to provide the same address to your microstack servers.