2017-03-24 17:17 GMT+00:00 Clark Boylan :
> On Fri, Mar 24, 2017, at 05:24 AM, Jens Rosenboom wrote:
>> 2017-03-24 9:48 GMT+00:00 Jens Rosenboom :
>> > 2017-03-24 9:30 GMT+00:00 Simon Leinen :
>> >> Clark Boylan writes:
>> >>
On Fri, Mar 24, 2017, at 05:24 AM, Jens Rosenboom wrote:
> 2017-03-24 9:48 GMT+00:00 Jens Rosenboom :
> > 2017-03-24 9:30 GMT+00:00 Simon Leinen :
> >> Clark Boylan writes:
> >> [...]
> >>> {
> >>> "id": "network1",
> >>>
2017-03-24 9:48 GMT+00:00 Jens Rosenboom :
> 2017-03-24 9:30 GMT+00:00 Simon Leinen :
>> Clark Boylan writes:
>> [...]
>>> {
>>> "id": "network1",
>>> "link": "tap14b906ba-8c",
>>> "network_id":
2017-03-24 9:30 GMT+00:00 Simon Leinen :
> Clark Boylan writes:
> [...]
>> {
>> "id": "network1",
>> "link": "tap14b906ba-8c",
>> "network_id": "7ee08c00-7323-4f18-94bb-67e081520e70",
>> "type": "ipv6_dhcp"
>>
Clark Boylan writes:
[...]
> {
> "id": "network1",
> "link": "tap14b906ba-8c",
> "network_id": "7ee08c00-7323-4f18-94bb-67e081520e70",
> "type": "ipv6_dhcp"
> }
> ],
> "services": []
> }
> You'll notice that the network1
Hello,
The infra team ran into glean not being able to correctly configure host
interfaces on boot. The trigger for this appears to be this change to
nova which enabled ipv6 in metadata/config drive [0]. I don't think
there is anything wrong with this but it exposed another interesting
behavior.