endpoint not used in lxd provider

Bug #1618798 reported by José Pekkarinen on 2016-08-31
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
juju
High
Unassigned

Bug Description

Hi,

I'm trying to use the endpoint with the lxd provider, and it doesn't use the information provided. Config file is this:

clouds:
  ant-lxd:
    type: lxd
    authtypes: [empty]
    regions:
      ant:
        endpoint: https://192.168.0.29:8443

lxd is added as a remote in local lxd and can be used:

lxc remote list
+-----------------+------------------------------------------+---------------+--------+--------+
| NAME | URL | PROTOCOL | PUBLIC | STATIC |
+-----------------+------------------------------------------+---------------+--------+--------+
| ant | https://192.168.0.29:8443 | lxd | NO | NO |
+-----------------+------------------------------------------+---------------+--------+--------+

Using it:

lxc launch ant:f4c4c60a6b75 ant:mycontainer
Creating mycontainer
Starting mycontainer

lxc list
+-------------+---------+---------------------+------+------------+-----------+
| NAME | STATE | IPV4 | IPV6 | TYPE | SNAPSHOTS |
+-------------+---------+---------------------+------+------------+-----------+
| mycontainer | RUNNING | 192.168.0.2 (eth0) | | PERSISTENT | 0 |
+-------------+---------+---------------------+------+------------+-----------+

Bootstrapping the cloud:

juju bootstrap ant-controller ant-lxd
ERROR invalid config: lxdbr0 has no ipv4 or ipv6 subnet enabled
It looks like your lxdbr0 has not yet been configured. Please configure it via:

        sudo dpkg-reconfigure -p medium lxd

and then bootstrap again.

Which corresponds to locally use the default profile in the host it tries to connect to the remote:

lxc profile show default
name: default
config:
  environment.http_proxy: http://[fe80::1%eth0]:13128
  user.network_mode: link-local
description: Default LXD profile
devices:
  eth0:
    name: eth0
    nictype: bridged
    parent: lxdbr0
    type: nic

This is the profile in the remote host:

lxc profile show default
name: default
config: {}
description: Default LXD profile
devices:
  eth0:
    name: eth0
    nictype: bridged
    parent: br0
    type: nic

Any clue what is going on? Any other info I can provide?

Thanks!

José.

José Pekkarinen (koalinux) wrote :

Way to test it:

1) Create a xenial container connected to a bridge in your machine.
2) Install juju 2 on it.
3) juju add-cloud ant-lxd lxd.yaml
4) juju bootstrap ant-controller ant-lxd

no longer affects: juju-core
Changed in juju:
status: New → Triaged
importance: Undecided → High
milestone: none → 2.0-beta18
Richard Harding (rharding) wrote :

Juju doesn't currently support remote lxd endpoints. It's something we've got on the roadmap for after 2.0 release.

Changed in juju:
milestone: 2.0-beta18 → 2.1.0
Anastasia (anastasia-macmood) wrote :

Removing 2.1 milestone as we will not be addressing this issue in 2.1.

Changed in juju:
milestone: 2.1.0 → none
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers