Here's a guess: by the time maas-rack-controller was installed on the 2nd machine, the rack had already auto-enlisted in MAAS and grabbed a generated name. Then when the rack was registered, no subsequent update occurred.
I would try starting up the 2nd VM after the first MAAS is up and running, so that it auto-enlists first.
Here's a guess: by the time maas-rack- controller was installed on the 2nd machine, the rack had already auto-enlisted in MAAS and grabbed a generated name. Then when the rack was registered, no subsequent update occurred.
I would try starting up the 2nd VM after the first MAAS is up and running, so that it auto-enlists first.