Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

In the UI, after selecting two interfaces to create a network bond, app hangs and loads forever #4245

Open
webteam-app opened this issue Jul 14, 2022 · 2 comments
Milestone

Comments

@webteam-app
Copy link

Bug originally filed by marmite211 at https://bugs.launchpad.net/bugs/1975476

In MAAS UI, after selecting two interfaces to create a network bond, app hangs and loads forever.

I'm using Debian packages version maas/focal,now 1:3.1.0-10901-g.f1f8f1505-0ubuntu1~20.04.1 all [installed]

I'd like to deploy a machine with particular network settings via MAAS. The machine was commissioned successfully. Before deployment, I want to create a network bond from two interfaces.

I was able to do it for two other interfaces successfully. But for the other two, after selecting them and clicking 'Create bond' it hangs. The only difference I can see between the interfaces I managed to bond and the interfaces that I don't seem to be able to bond, is that the interfaces that I cannot bond are disconnected.

Steps to reproduce:

  1. Prepare a machine. Make sure it has at least 2 different NICs with at least 2 ports each.

  2. Connect network to the two ports of the first NIC. In the other NIC, leave all ports disconnected.

  3. Commission the machine.

  4. Go to network settings. Try to create a bond out of the two connected interfaces. That should work.

  5. Try to create a bond out of the two interfaces that have no cables connected. That shouldn't work. As soon as you click 'Create bond', the app hangs forever. (screenshots attached)

@anthonydillon anthonydillon added this to the MAAS 3.3.0 milestone Jul 15, 2022
@blackliner
Copy link

same here, 3.4 from apt (1:3.4.0-14319-g.3ab76533f-0ubuntu1~22.04.1)
image
image

@blackliner
Copy link

Found a workaround while trying to make it work with CLI. The CLI gives you a nice error message:

{"parents": ["All parents must belong to the same VLAN."]}

Solution: Mark the interface as connected, then click on "Edit Pyhsical" and manually set the right subnet set.
image

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

No branches or pull requests

3 participants