vr: add missing rule for port forwarding rule in vpc#3857
Conversation
|
@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-734 |
|
@blueorangutan test |
|
@rhtyd a Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been kicked to run smoke tests |
|
Trillian test result (tid-873)
|
yadvr
left a comment
There was a problem hiding this comment.
lgmt, did not test it manually.
|
Rekicked Travis job1, it failed; need to check if it fails again cc @ustcweizhou |
|
@weizhouapache (cc @rhtyd ) it is a pylint format error. you care to fix? |
…debian/opt/cloud/bin/configure.py'
|
@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-769 |
|
@blueorangutan test |
|
@DaanHoogland a Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been kicked to run smoke tests |
|
Trillian test result (tid-914)
|
add missing rule for port forwarding rule in vpc Originally authored in apache#3857 and cherrypicked. See merge request dev/cloudstack!160
Description
When create a port forwarding rule to a vm in vpc, we cannot access the port forwarding rule from inside the vm.
Steps to reproduce
(1) create a port forwarding rule in VPC, public ip X.X.X.X to vm Y.Y.Y.Y port 22
(2) ssh to vm, or login vm console
(3) in vm, ssh X.X.X.X does not work.
Fixes: #3763
Types of changes
Screenshots (if appropriate):
How Has This Been Tested?
with this change, the public Ip is reachable from inside vm in step (3) above.