Skip to content
This repository has been archived by the owner on Oct 26, 2022. It is now read-only.

VLAN interfaces names are not sufficiently unique in some circumstances #160

Open
hinchliff opened this issue Dec 7, 2017 · 1 comment

Comments

@hinchliff
Copy link
Contributor

As noted in #157, there are cases where the interfaces used to help distinguish VLAN are not sufficiently unique, and can cause manifest display issues.

@ibaldin
Copy link
Contributor

ibaldin commented Dec 7, 2017

Because interface names on e.g. ION connections are inherited from substrate descriptions, they end up not being unique if e.g. there are two connections coming out towards a multi-point connection from the same domain (has to be from a BM and a VM, because 2xVM connection collapses to a single connection to the multipoint).

The lack of name uniqueness prevents proper reconstruction of paths as shown in #157 by flukes, although does not affect the provisioning.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants