Bootstrapping juju model failed i/o timeout

The problem showed when bootstrapping a controller for Juju :

Error:

Error Get “http://192.168.100.180:5240/MAAS/api/2.0/version/”: Dial tcp 192.168.100.180:5240: i/o timeout
Failed to bootstrap model

I can access MAAS at http://192.168.100.180:5240/MAAS and deploy machines.

Set Up

Maas Host:

  • public address: 192.168.100.180
  • private subnet: 172.30.1.0/24
  • hostname: clusterhead1
  • interfaces:
    eno1 : 192.168.100.180
    eno2 : 172.30.1.1
  • routing
Destination        Gateway        Genmask         Flags  Metric  Ref  Iface  
0.0.0.0           192.168.100.1   0.0.0.0          UG     0     0   eno1 
192.168.100.1     0.0.0.0         255.255.255.0     U      0     0   eno1 
172.30.1.0        0.0.0.0         255.255.255.0     U      0     0   eno2
  • Maas Subnet DHCP :
    • addresses: 172.30.1.0/24
    • gateway: 172.30.1.1
    • DNS:
  • nslookup

Deployed LXD Machine

  • addresses: 172.30.1.6
  • hostname: worker17
  • Interfaces
    br-eno1 : 172.30.1.6
    lxdbr0 : 10.37.82.1
  • Ping
    172.30.1.1: success
    8.8.8.8: success
    192.168.100.180: FAIL
    192.168.100.185: success
  • routing
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
0.0.0.0         172.30.1.1      0.0.0.0         UG    0      0        0 br-eno1
10.37.82.0      0.0.0.0         255.255.255.0   U     0      0        0 lxdbr0
172.30.1.0      0.0.0.0         255.255.255.0   U     0      0        0 br-eno1
  • nslookup
    • public(ubuntu.com): success
    • clusterhead1: success

Juju Deployment

  • Mass create LXD container on LXD machine
  • Juju bootstrap controller to LXD container.

Question

  • What I miss in order to ping from the deployed machine to the public host address?

Let me know if you need more info. Thanks.

Hi,

MAAS won’t automatically set up routes on the machines where it’s running, so by default you won’t be able to reach the public MAAS address from inside a separate VLAN.

From your config I see 172.30.1.1 is the default gateway for that subnet, so you’ll need to manually add firewall rules to allow forwarding between the private and public subnet.

Alternatively, since MAAS listens on all IPs by default, you can use 172.30.1.1 as address to reach MAAS when bootstrapping Juju.

Thanks for your answer:

From your config I see 172.30.1.1 is the default gateway for that subnet, so you’ll need to manually add firewall rules to allow forwarding between the private and public subnet.

I forgot to mention the iptables rules to forward traffic from the private to public interface and vice versa (BTW, no more rules for debugging purpose). In addition, I can ping from the LXD Machine (subnet 172.10.1.6/24) to 8.8.8.8 and 192.168.100.185, but I cannot ping to 192.168.100.180 (the MAAS host).

Chain INPUT (policy ACCEPT)
target prot opt source destination

Chain FORWARD (policy ACCEPT)
target prot opt source destination
ACCEPT all – anywhere anywhere state RELATED,ESTABLISHED
ACCEPT all – anywhere anywhere
ACCEPT all – anywhere anywhere state RELATED,ESTABLISHED
ACCEPT all – anywhere anywhere

Chain OUTPUT (policy ACCEPT)
target prot opt source destination

Alternatively, since MAAS listens on all IPs by default, you can use 172.30.1.1 as address to reach MAAS when bootstrapping Juju.

Do you mind elaborating more, this answer?

I really appreciate your help.

Thanks.

I mean you could use http://172.30.1.1:5240/MAAS as URL for MAAS endpoint in juju

Thanks for your help and that works.

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