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
If I have an interface that is configured, and I then change that configuration so it is put on a different fabric and subnet, when I click Save, instead of saving, MAAS changes the Interface to Unconfigured, forcing me to configure the interface a second time.
This is pretty easily and reliably reproducible on MAAS 2.6, I've had it happen on multiple systems when trying to move an interface from one Fabric to another.
This does not seem to occur when configuring one for the first time, or when simply changing the type of addressing (e.g. from DHCP to AutoAssign). It only seems to happen when I change one from one Fabric to Another, and choose a different subnet.
Bug originally filed by bladernr at https://bugs.launchpad.net/bugs/1840049
See the attached video.
If I have an interface that is configured, and I then change that configuration so it is put on a different fabric and subnet, when I click Save, instead of saving, MAAS changes the Interface to Unconfigured, forcing me to configure the interface a second time.
This is pretty easily and reliably reproducible on MAAS 2.6, I've had it happen on multiple systems when trying to move an interface from one Fabric to another.
This does not seem to occur when configuring one for the first time, or when simply changing the type of addressing (e.g. from DHCP to AutoAssign). It only seems to happen when I change one from one Fabric to Another, and choose a different subnet.
MAAS version: 2.6.0 (7802-g59416a869-0ubuntu1~18.04.1)
The text was updated successfully, but these errors were encountered: