You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 26, 2022. It is now read-only.
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.
The text was updated successfully, but these errors were encountered:
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.
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.
The text was updated successfully, but these errors were encountered: