You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cloudstack.apache.org by GitBox <gi...@apache.org> on 2018/04/22 11:36:59 UTC

[GitHub] mdesaive opened a new issue #2592: Unable to add NIC to VM - Insufficient capacity when adding NIC to VM

mdesaive opened a new issue #2592: Unable to add NIC to VM - Insufficient capacity when adding NIC to VM
URL: https://github.com/apache/cloudstack/issues/2592
 
 
   <!--
   Verify first that your issue/request is not already reported on GitHub.
   Also test if the latest release and master branch are affected too.
   Always add information AFTER of these HTML comments, but no need to delete the comments.
   -->
   
   ##### ISSUE TYPE
   <!-- Pick one below and delete the rest -->
    * Bug Report
   
   ##### COMPONENT NAME
   <!--
   Categorize the issue, e.g. API, VR, VPN, UI, etc.
   -->
   ~~~
   UI
   ~~~
   
   ##### CLOUDSTACK VERSION
   <!--
   New line separated list of affected versions, commit ID for issues on master branch.
   -->
   
   ~~~
   4.11.0.0
   ~~~
   
   ##### CONFIGURATION
   <!--
   Information about the configuration if relevant, e.g. basic network, advanced networking, etc.  N/A otherwise
   -->
   
   
   ##### OS / ENVIRONMENT
   <!--
   Information about the environment if relevant, N/A otherwise
   -->
   Advanced Networking, Cloudstack 4.11.0.0 on Ubuntu 14.04 LTS,
   MySQL 5.5.59-0ubuntu0.14.04.1
   
   ##### SUMMARY
   <!-- Explain the problem/feature briefly -->
   On one of our two CloudStack instances we have an issue adding NICs to
   VMs through the Web-UI after upgrading to 4.11.0.0. On another instance the problem does
   not occur after the upgrade. I already asked on users@cloudstack to reproduce the issue, but got no response. So this might be an individual problem.
   
   Adding a NIC with CloudMonkey through a command like the following ist working perfectly:
   
   create network displaytext=deleteme-cloudmonkey
   name=deleteme-cloudmonkey networkofferingid=<id> zoneid=<id>
   projectid=<id> gateway=172.17.1.1 netmask=255.255.252.0
   networkdomain=deleteme-cloudmonkey.heinlein-intern.de
   
   This issue maybe is close to #2533 "Web-UI creates all isolated Nets with IP range 10.1.1.0/24" - in both cases the API call through CloudMonkey works fine, but using the web-UI leads to an error. Maybe it could make sense to investigate those two issues together.
   
   ##### STEPS TO REPRODUCE
   <!--
   For bugs, show exactly how to reproduce the problem, using a minimal test-case. Use Screenshots if accurate.
   
   For new features, show how the feature would be used.
   -->
   
   <!-- Paste example playbooks or commands between quotes below -->
   ~~~
   Create a new isolated network
   Wait until network is "implemented"
   Add NIC on this new network to a VM
   ~~~
   
   <!-- You can also paste gist.github.com links for larger files -->
   
   ##### EXPECTED RESULTS
   <!-- What did you expect to happen when running the steps above? -->
   
   ~~~
   To have the NIC added to VM and network. ;)
   ~~~
   
   ##### ACTUAL RESULTS
   <!-- What actually happened? -->
   
   <!-- Paste verbatim command output between quotes below -->
   ~~~
   => Textbox: Insufficient capacity when adding NIC to VM[User|i-<id>-VM]:
   com.cloud.exception.InsufficientAddressCapacityException: Insufficient
   address capacityScope=interface com.cloud.dc.DataCenter; id=1
   => No new NIC is added to the VM
   ~~~
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services