Fixed instance creation failure on dvswitch when using vlan id 4095#4557
Conversation
|
@Spaceman1984 have you tested this |
|
@blueorangutan package |
|
@rhtyd a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress. |
yadvr
left a comment
There was a problem hiding this comment.
LGTM - but should the vlan range be 1-4094 @Spaceman1984 ?
yadvr
left a comment
There was a problem hiding this comment.
LGTM 0-4094 is correct, thnx Alex for confirming.
|
Packaging result: ✖centos7 ✖centos8 ✖debian. JID-2507 |
|
Seems like there are some test failures, looking into it |
|
@blueorangutan package |
|
@Spaceman1984 a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress. |
|
Packaging result: ✔centos7 ✖centos8 ✔debian. JID-2508 |
|
@blueorangutan test help |
|
@blueorangutan test matrix |
|
@Spaceman1984 a Trillian-Jenkins matrix job (centos7 mgmt + xs71, centos7 mgmt + vmware65, centos7 mgmt + kvmcentos7) has been kicked to run smoke tests |
|
Trillian test result (tid-3363)
|
|
Trillian test result (tid-3364)
|
|
Trillian test result (tid-3365)
|
|
@alexandremattioli @andrijapanicsb have you tested/reviewed this? Thanks |
| } | ||
|
|
||
| public static VmwareDistributedVirtualSwitchVlanSpec createDVPortVlanSpec(Integer vlanId, String vlanRange) { | ||
| if (vlanId != null && vlanId == 4095){ |
There was a problem hiding this comment.
@Spaceman1984 Have you tested this?
this method createDVPortVlanSpec() is called only when vlanId is null, so if check here is always 'false' and the underlying code never executes. Please check and try to fix this in the appropriate top level method in the call stack.
There was a problem hiding this comment.
This method is not onlly called when vlanid is null.
If vid is not null, spvlanid would be evaluated and if spvlanid is null, the method will be called.
if (vid == null || spvlanid == null) {
vlanspec = createDVPortVlanSpec(vid, vlanRange);
...
}
I tested this as I stated in the description.
|
Tested. LGTM |
Description
When creating an instance on a guest network where the vlan id has been set to 4095, the instance fails to start.
This PR sets the vlan id and range on the created port group to allow the instance to be created.
Fixes #4358
Types of changes
Feature/Enhancement Scale or Bug Severity
Bug Severity
Screenshots (if appropriate):
How Has This Been Tested?
This has been tested by creating a guest network and setting the vlan id to 4095 and creating an instance using the specific network.