Juju bootstrap fails because updates cannot be fetched

Users
,
1

Hello. I’m testing out MaaS in a virtual environment. I have MaaS region and rack controllers deployed to one machine with two NICs:

  • NIC 1:

    • Connected to an upstream network
    • Has IP 10.0.1.208

  • NIC 2:

    • Acts as a gateway for a private network
    • Has IP 172.16.66.1
    • Provides DNS and DHCP for the 172.16.66.0/24 subnet

So far I’ve been able to add two machines to my cluster. Now I’m trying to provision one of them as a Juju controller. When I do that, the machine that MaaS selects fails deployment because it cannot reach 10.0.1.208.

I enabled IP forwarding on the MaaS rack/region controller, but that didn’t seem to help. The provisioning process for the Juju controller still fails with the same problem.

FWIW I am running MaaS version 2.4.2. Any ideas about what configuration is missing?

Thank you.

2

Does it work if you change the MAAS URL to point to 172.16.66.1?

maas-region local_config_set --maas-url http://172.16.66.1:5240/MAAS

1 Like
3

That helped. Thank you.

4

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.