kvm: fix issue that network rules for secondary IPs are not applied#3636
Merged
yadvr merged 1 commit intoapache:4.13from Nov 21, 2019
Merged
kvm: fix issue that network rules for secondary IPs are not applied#3636yadvr merged 1 commit intoapache:4.13from
yadvr merged 1 commit intoapache:4.13from
Conversation
When I add a secondary IP to a nic on shared network in advanced zone with security groups, the network rules for new IP are not applied on KVM hypervisors. It is because "--action -A" cannot be recognized in security_group.py after commit ac73e7e. changing to "--action=-A" will fix it.
Contributor
Author
|
@wido @GabrielBrascher could you please review and test it ? |
Merged
5 tasks
Member
|
@blueorangutan package |
|
@rhtyd a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress. |
|
Packaging result: ✔centos6 ✔centos7 ✔debian. JID-343 |
GabrielBrascher
approved these changes
Nov 13, 2019
yadvr
approved these changes
Nov 21, 2019
Member
|
Requires SG env that BO cannot kick by default, since manually tested, not kicking explicit test. |
ustcweizhou
added a commit
to ustcweizhou/cloudstack
that referenced
this pull request
Feb 28, 2020
…pache#3636) When I add a secondary IP to a nic on shared network in advanced zone with security groups, the network rules for new IP are not applied on KVM hypervisors. It is because "--action -A" cannot be recognized in security_group.py after commit ac73e7e. changing to "--action=-A" will fix it.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
When I add a secondary IP to a nic on shared network in advanced zone with security groups, the network rules for new IP are not applied on KVM hypervisors.
It is because "--action -A" cannot be recognized in security_group.py after commit ac73e7e. changing to "--action=-A" will fix it.
Types of changes
Screenshots (if appropriate):
How Has This Been Tested?
When add a ip (ip must to be specified see #3635) to a nic, in advanced zone with security groups, the network rules for the ip should be added on hypervisor. However it does not work in 4.13/master.
in agent.log it gives the following error
The rules (ipset, iptables, ebtables) are added after this fix.