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

Network Watcher - Topology - error: __init__() takes 1 positional argument but 2 were given #6326

Closed
mattreatMSFT opened this issue May 10, 2018 · 0 comments · Fixed by #6330
Assignees
Labels
bug This issue requires a change to an existing behavior in the product in order to be resolved. Network az network vnet/lb/nic/dns/etc...
Milestone

Comments

@mattreatMSFT
Copy link

Describe the bug

Reporting with permission from user

error: init() takes 1 positional argument but 2 were given

I tried it without the –subnet option and got the same error. As you can see, the portal renders the topology using the same resource group and VNet names. Tried it this morning ONLY using –resource-group, and it worked! It should work with the other options too though, or they should be removed. I put two VNets in the resource group and the command returned the topology for both (as expected), but if I wanted it for only one VNet, it would be nice to be able to specify.

cli_bug

To Reproduce
See above.

Expected behavior
If this is a client error, the client should report back to the user with proper guidance on why the request failed.

Environment summary
CloudShell - unknown version

Additional context
@jimdial reported the issue.

@yugangw-msft yugangw-msft added the Network az network vnet/lb/nic/dns/etc... label May 10, 2018
@tjprescott tjprescott added the bug This issue requires a change to an existing behavior in the product in order to be resolved. label May 10, 2018
@tjprescott tjprescott self-assigned this May 10, 2018
@tjprescott tjprescott added this to the Sprint 37 milestone May 10, 2018
tjprescott added a commit that referenced this issue May 11, 2018
@haroldrandom haroldrandom added bug This issue requires a change to an existing behavior in the product in order to be resolved. Network az network vnet/lb/nic/dns/etc... labels Oct 25, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug This issue requires a change to an existing behavior in the product in order to be resolved. Network az network vnet/lb/nic/dns/etc...
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants