Repository navigation
UI: Import VM wizard doesn't list the project networks #12685
Description
problem
The import VM from external vcenter in UI doesn't list the project networks when the project is selected. It requires the UI to be changed to the project view to list the project networks.
Since the project is allowed to be selected and the ROOT admin can list the project networks in another domain, it should list the project networks without changing the view to the project.
versions
4.22.0.0
The steps to reproduce the bug
1.Create project and guest network in a sub domain
2.Import VM using UI , select the project from the drop down while importing
3. The networks for the project are not listed
...
What to do about it?
Networks should be listed and allowed to be selected
Activity
dheeraj12347 commentedon Mar 11, 2026
Hi, I was reviewing this issue and it seems that when a project is selected during the VM import workflow, the UI does not fetch or display the networks belonging to that project unless the view is switched to the project context.
I’d like to investigate the UI logic responsible for fetching and filtering the networks during the import workflow and see why the project networks are not being listed.
If no one is currently working on this, I’d be happy to take a look and propose a fix.
DaanHoogland commentedon Mar 11, 2026
sure @dheeraj12347 , don’t take too much in parallel (but only you can decide what’s too much ;)
dheeraj12347 commentedon Mar 12, 2026
okay @DaanHoogland :)
dheeraj12347 commentedon Mar 15, 2026
Hi @rajujith, @DaanHoogland
I’ve implemented a fix for this issue by:
Adding a projectid prop to MultiNetworkSelection.vue and using it to pass the project into the listNetworks call.
Passing form.projectid into in ImportUnmanagedInstance.vue so the networks are filtered by the selected project.
npm run lint passes successfully. When I try npm run dev on the latest main (with and without my changes), I hit this error, which seems unrelated to this patch:
Syntax Error: TypeError: Cannot read properties of null (reading 'content') in src/views/AutogenView.vue
Could you please confirm if this approach looks correct and if I should open a PR with these changes?
DaanHoogland commentedon Mar 16, 2026
if there’s no PR, it doesn’t exist @dheeraj12347 ;)
that said
npm run devis not a valid command as far as I am aware. Try running a simulator first and then runnpm run serve.dheeraj12347 commentedon Mar 18, 2026
Hi @DaanHoogland ,
I’ve implemented the UI changes to pass projectid into the multi-network selector so that only project networks are shown when importing unmanaged instances for a project, and opened a PR with these changes. I also ran npm run lint (passes) and npm run serve successfully on my machine to verify the UI builds, but I’m currently blocked on logging in to the UI because I don’t have valid username/password credentials for the test environment, so I couldn’t fully test the import unmanaged instance flow end-to-end.
DaanHoogland commentedon Mar 19, 2026
Can you link this issue and the PR, @dheeraj12347 ?
admin/password are the default credentials. You should be able to connect using those. Have you configured the right backend in your running ui? (see ui/.env.local.sample, it should be installed as ui/.env.local)
dheeraj12347 commentedon Mar 19, 2026
Thanks for the pointers. The PR for this change is here: #12854.
I’ll configure ui/.env.local to point to my backend and test the flow using the default admin/password credentials.
And what to write in domain ?
DaanHoogland commentedon Mar 19, 2026
for admin you write nothing, only if you add domains (and accounts/users in them) this becomes an item.