UI: Fix VPC network offerings listing on VPC tier creation#9557
UI: Fix VPC network offerings listing on VPC tier creation#9557DaanHoogland merged 4 commits intoapache:4.19from
Conversation
|
@nvazquez a Jenkins job has been kicked to build UI QA env. I'll keep you posted as I make progress. |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## 4.19 #9557 +/- ##
============================================
- Coverage 15.08% 15.08% -0.01%
Complexity 11184 11184
============================================
Files 5406 5406
Lines 472908 472921 +13
Branches 60405 61613 +1208
============================================
- Hits 71345 71342 -3
- Misses 393619 393635 +16
Partials 7944 7944
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
|
UI build: ✔️ |
|
@nvazquez , as discussed off-line; I still see both types thanks |
|
Thanks for reviewing @DaanHoogland @weizhouapache - before the fix the network offerings listing was passing |
as I understand
I think network offerings should be filtered by the LB service provider (VpcVirtualRouter or InternalLbVm) instead of service (Lb). |
|
@DaanHoogland @weizhouapache I've revisited the logic and got the following results: Can you please review the latest changes? |
|
@nvazquez a Jenkins job has been kicked to build UI QA env. I'll keep you posted as I make progress. |
|
UI build: ✔️ |
@nvazquez if yes, I think it should be in the list as well. |
The vpc networks are created from vpc offerings which have LB of either vpcvrouter and internalLBVM
so i believe "DefaultIsolatedNetworkOfferingForVpcNetworksNoLB" should not be displayed |
kiranchavala
left a comment
There was a problem hiding this comment.
LGTM
Tested manually
- Create a 2 vpc offerings ,
Vpc Offering 1 > with LB as VpcVirtualRouter
Vpc Offering 2 > with LB as InternalLBVM
- Create 2 vpc networks
VPC network 1 > with Vpc Offering 1
VPC network 2 > with Vpc Offering 2
- Create 2 Network offering
Network offering 1 > with Loadbalancer type as public IP
Network offering 2 > with Loadbalancer type as internalLB
- Navigate to VPC network 1 and create a tier > the correct network offering is displayed
- Navigate to VPC network 2 and create a tier > the correct network offering is displayed
@kiranchavala @nvazquez |
|
Thanks @weizhouapache I tried it from the API and it fails for public LB VPC but works for the internal LB VPC: For public LB VPC: For internal LB VPC: I didn't find this intuitive, will refactor the logic to support this case also |
thanks @nvazquez for the testing regarding the error above, it seems to be caused by Dhcp of the VPC offering, not LB. |
|
@weizhouapache you are right, it got created properly. Sorry I wasn't aware of this behavior, will refactor accordingly |
|
@weizhouapache @kiranchavala I've refactored the logic, can you have a final review? Many thanks |
|
@nvazquez a Jenkins job has been kicked to build UI QA env. I'll keep you posted as I make progress. |
|
UI build: ✔️ |
|
@weizhouapache does this lgty now? |
|
@DaanHoogland this needs re-testing as there are some changes after last testing by @kiranchavala |
|
@DaanHoogland @kiranchavala could you if its looking good after the latest changes? |
|
@kiranchavala a Jenkins job has been kicked to build UI QA env. I'll keep you posted as I make progress. |
|
UI build: ✔️ |








Description
This PR fixes the VPC network offerings listing on VPC tiers creation
Fixes: #8023
Types of changes
Feature/Enhancement Scale or Bug Severity
Feature/Enhancement Scale
Bug Severity
Screenshots (if appropriate):
How Has This Been Tested?
Create VPC offering with Lb as supported service and VpcVirtualRouter as provider
Create VPC with the selected VPC offering
VPC -> Add new network tier -> verify available network offerings
How did you try to break this feature and the system with this change?