You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Marcus Sorensen (JIRA)" <ji...@apache.org> on 2013/07/09 05:57:50 UTC
[jira] [Created] (CLOUDSTACK-3407) network remains in 'allocated'
if nic is added to it as first action
Marcus Sorensen created CLOUDSTACK-3407:
-------------------------------------------
Summary: network remains in 'allocated' if nic is added to it as first action
Key: CLOUDSTACK-3407
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3407
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Affects Versions: 4.1.0
Reporter: Marcus Sorensen
Fix For: 4.1.1
1. Create a VPC
2. Create a network
3. Create a VM
4. Create a second netowrk
5. Add nic to vm on second network
result: Second network remains allocated, rather than implemented. Normally when the first vm is launched the network is provisioned, this isn't happening if a nic is added to a running VM as the first action on the network. This seems like there would be a simple fix.
Not sure if this applies to 4.2.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira