ustcweizhou opened a new pull request #3342: VPC: Fail to restart VPC with 
cleanup if there are multiple public IPs in different subnets
URL: https://github.com/apache/cloudstack/pull/3342
 
 
   ## Description
   
   If there are multiple IPs in different subnet assigned to a VPC, after 
restarting VPC with cleanup, the VRs will be FAULT state.
   
   Step to reproduce:
   (1) create vpc, source nat IP is 10.11.118.X
   (2) assign two public IPs in other subnet to this VPC. 10.11.119.X and 
10.11.119.Y
   (3) deploy two vms in the vpc, and enable static nat 10.11.119.X and 
10.11.119.Y to these two vms
   (4) restart vpc with cleanup. There are more than 1 nic allocated for 
10.11.119 to new VRs
   
   Logs as below:
   2019-05-10 14:12:24,652 DEBUG [o.a.c.e.o.NetworkOrchestrator] 
(API-Job-Executor-36:ctx-839f6522 job-652 ctx-35fb4667) (logid:1ab7aa37) 
Allocating nic for vm VM[DomainRouter|r-85-VM] in network Ntwk[200|Public|1] 
with requested profile NicProfile[0-0-null-10.11.118.157-vlan://untagged
   2019-05-10 14:12:24,676 DEBUG [o.a.c.e.o.NetworkOrchestrator] 
(API-Job-Executor-36:ctx-839f6522 job-652 ctx-35fb4667) (logid:1ab7aa37) 
Allocating nic for vm VM[DomainRouter|r-85-VM] in network Ntwk[200|Public|1] 
with requested profile NicProfile[0-0-null-10.11.119.110-vlan://119
   2019-05-10 14:12:24,699 DEBUG [o.a.c.e.o.NetworkOrchestrator] 
(API-Job-Executor-36:ctx-839f6522 job-652 ctx-35fb4667) (logid:1ab7aa37) 
Allocating nic for vm VM[DomainRouter|r-85-VM] in network Ntwk[200|Public|1] 
with requested profile NicProfile[0-0-null-10.11.119.110-vlan://119
   2019-05-10 14:12:24,723 DEBUG [o.a.c.e.o.NetworkOrchestrator] 
(API-Job-Executor-36:ctx-839f6522 job-652 ctx-35fb4667) (logid:1ab7aa37) 
Allocating nic for vm VM[DomainRouter|r-85-VM] in network Ntwk[200|Public|1] 
with requested profile NicProfile[0-0-null-10.11.119.110-vlan://119
   
   This is a regression issue caused by commit 
1d382e0cb48fc428bbe753dcfe4116bc71231206
   
   <!--- Describe your changes in detail -->
   
   <!-- For new features, provide link to FS, dev ML discussion etc. -->
   <!-- In case of bug fix, the expected and actual behaviours, steps to 
reproduce. -->
   
   <!-- When "Fixes: #<id>" is specified, the issue/PR will automatically be 
closed when this PR gets merged -->
   <!-- For addressing multiple issues/PRs, use multiple "Fixes: #<id>" -->
   <!-- Fixes: # -->
   
   ## Types of changes
   <!--- What types of changes does your code introduce? Put an `x` in all the 
boxes that apply: -->
   - [ ] Breaking change (fix or feature that would cause existing 
functionality to change)
   - [ ] New feature (non-breaking change which adds functionality)
   - [X] Bug fix (non-breaking change which fixes an issue)
   - [ ] Enhancement (improves an existing feature and functionality)
   - [ ] Cleanup (Code refactoring and cleanup, that may add test cases)
   
   ## How Has This Been Tested?
   <!-- Please describe in detail how you tested your changes. -->
   <!-- Include details of your testing environment, and the tests you ran to 
-->
   <!-- see how your change affects other areas of the code, etc. -->
   
   see Description
   Everything works fine with this patch.
   
   <!-- Please read the 
[CONTRIBUTING](https://github.com/apache/cloudstack/blob/master/CONTRIBUTING.md)
 document -->
   

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


With regards,
Apache Git Services

Reply via email to