MicroStack breaks once the IP address of the workstation changes
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MicroStack |
Triaged
|
Low
|
Unassigned |
Bug Description
I noticed that MicroStack breaks once the IP address of the workstation changes.
I had MicroStack installed according to the following tutorial: https:/
guardian@
...
2: wlp0s20f3: <BROADCAST,
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:
valid_lft forever preferred_lft forever
...
guardian@
+------
| Name | Type | Endpoints |
+------
| neutron | network | microstack |
| | | internal: http://
| | | microstack |
| | | public: http://
| | | microstack |
| | | admin: http://
| | | |
| glance | image | microstack |
| | | internal: http://
| | | microstack |
| | | admin: http://
| | | microstack |
| | | public: http://
| | | |
| nova | compute | microstack |
| | | internal: http://
| | | microstack |
| | | admin: http://
| | | microstack |
| | | public: http://
| | | |
| keystone | identity | microstack |
| | | public: http://
| | | microstack |
| | | internal: http://
| | | microstack |
| | | admin: http://
| | | |
| placement | placement | microstack |
| | | admin: http://
| | | microstack |
| | | internal: http://
| | | microstack |
| | | public: http://
| | | |
| cinderv2 | volumev2 | microstack |
| | | public: http://
| | | microstack |
| | | internal: http://
| | | microstack |
| | | admin: http://
| | | |
| cinderv3 | volumev3 | microstack |
| | | admin: http://
| | | microstack |
| | | internal: http://
| | | microstack |
| | | public: http://
| | | |
+------
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:/
I tried restarting MicroStack, but it failed:
guardian@
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-
See "systemctl status snap.microstack
)
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
guardian@
● snap.microstack
Loaded: loaded (/etc/systemd/
Active: failed (Result: exit-code) since Mon 2021-09-06 09:05:39 CEST; 9min ago
Process: 1121827 ExecStart=
Main PID: 1121827 (code=exited, status=5)
wrz 06 09:05:39 Guardian-Inspiron microstack.
wrz 06 09:05:39 Guardian-Inspiron microstack.
wrz 06 09:05:39 Guardian-Inspiron microstack.
wrz 06 09:05:39 Guardian-Inspiron microstack.
wrz 06 09:05:39 Guardian-Inspiron microstack.
wrz 06 09:05:39 Guardian-Inspiron microstack.
wrz 06 09:05:39 Guardian-Inspiron microstack.
wrz 06 09:05:39 Guardian-Inspiron systemd[1]: snap.microstack
wrz 06 09:05:39 Guardian-Inspiron systemd[1]: snap.microstack
wrz 06 09:05:39 Guardian-Inspiron systemd[1]: Failed to start Service for snap application microstack.
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.