Comment 14 for bug 1834974

Revision history for this message
Gary.Wang (gary-wzl77) wrote :

Deploy the Anbox Cloud on the OCI with juju 2.9.32 and hit the same issue.
Check the output of juju status
https://paste.ubuntu.com/p/WT8ZsK7Y3V/

1. Access the LXD daemon from an external network(my host):

$ nc -vz 132.145.160.190 8443
nc: connect to 132.145.160.190 port 8443 (tcp) failed: No route to host

2. Access the LXD daemon from the AMS unit
  - With the private address (the ip addresses of LXD unit and AMD unit are under the same subnet)
    $ juju ssh ams/0 -- "nc -vz 10.0.0.122 8443"
      nc: connect to 10.0.0.122 port 8443 (tcp) failed: No route to host
  - With the public address
    $ juju ssh ams/0 -- "nc -vz 132.145.160.190 8443"
      nc: connect to 132.145.160.190 port 8443 (tcp) failed: No route to host

3. Access the LXD daemon from the LXD unit
  - With the private address
    $ juju ssh lxd/0 -- "nc -vz 10.0.0.122 8443"
      Connection to 10.0.0.122 8443 port [tcp/*] succeeded!
  - With the public address
    $ juju ssh lxd/0 -- "nc -vz 132.145.160.190 8443"
      nc: connect to 132.145.160.190 port 8443 (tcp) failed: No route to host

-------------------------------------------------------
 Manually setup IP table rule to expose LXD daemon with
  $ juju ssh lxd/0 -- "sudo iptables -I INPUT 1 -p tcp -m state --state NEW -m tcp --dport 8443 -j ACCEPT"

4. Access the LXD daemon from the LXD unit
  - With the private address
    $ juju ssh lxd/0 -- "nc -vz 10.0.0.122 8443"
      Connection to 10.0.0.122 8443 port [tcp/*] succeeded!
  - With the public address
    $ juju ssh lxd/0 -- "nc -vz 132.145.160.190 8443"
      Connection to 132.145.160.190 8443 port [tcp/*] succeeded!

5. Access the LXD daemon from the AMS unit
  - With the private address
    $ juju ssh ams/0 -- "nc -vz 10.0.0.122 8443"
      Connection to 10.0.0.122 8443 port [tcp/*] succeeded!
  - With the public address
    $ juju ssh ams/0 -- "nc -vz 132.145.160.190 8443"
     Connection to 132.145.160.190 8443 port [tcp/*] succeeded!