Hyper-V - MicroStack not usable after VM restart

[Miroslav Rešetar]

1. MicroStack is installed and initialized using Windows steps from https://microstack.run/

After initial setup console is accessible and admin user can login

2. VM is restarted or suspended

After VM resume external IP of the VM has been changed.

3. As a consequence MicroStack is no longer functional.

Login returns "504 Gateway Time-out".
In Journal log we can see timeouts as well.

  2022-11-15 15:47:46.292 222279 ERROR neutron.db.agentschedulers_db oslo_db.exception.DBConnectionError: (pymysql.err.OperationalError) (2003, "Can't connect to MySQL server on '172.31.138.248' (timed out)")
                                                      2022-11-15 15:47:46.292 222279 ERROR neutron.db.agentschedulers_db (Background on this error at: http://sqlalche.me/e/e3q8)

Here we can see original IP address logged 172.31.138.248.

Where command multipass info microstack-vm returns

Name: microstack-vm
State: Running
IPv4: 172.29.129.178
                10.20.20.1
Release: Ubuntu 22.04.1 LTS
Image hash: 1d24e397489d (Ubuntu 22.04 LTS)
CPU(s): 8
Load: 5.86 4.73 2.02
Disk usage: 2.8GiB out of 96.7GiB
Memory usage: 3.1GiB out of 23.5GiB
Mounts: --

This is really bad CX.

I would expect that:

1. No IP address is used to connect to internal services. Couldn't VM machine name be used? Or an arbitrary name that resolves to the current IP?
2. If an external IP address is expected to be consumed there should be a script that would rectify the configuration so after restart it would be a matter of running a script.

Is there a plan to better support Hyper-V? Maybe better documentation at least so it can be made to work after restarts.

[Billy Olsen (billy-olsen)]

Unfortunately, this isn't specific to the Hyper-V solution. It's basically whenever the IP address of the instance changes. Your suggestion is a good one to have a script which can be used to update the IP address. These are some things we will take into consideration for the sunbeam edition of MicroStack.

In the meantime, you can provide a static IP address to the hyper-v instance to ensure that the IP address is the same each time.

[Miroslav Rešetar (remi2022)]

Yes, I see that it was reported before in ticket 1942741 also. I've seen a problem described elsewhere.
In my understanding, Hyper-V doesn't support static IPs on Default Switch.
So if Default Switch is used static IP is not something that could be achieved.

There is a possibility to add extra networks but I have experienced some issues when multipass is connecting to the VM in this configuration.

Do you have some documentation on how static IP could be achieved for Microstack in combination with multipass and Hyper-V?

Thanks a lot!