[
https://issues.apache.org/jira/browse/CLOUDSTACK-8915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14942966#comment-14942966
]
ASF GitHub Bot commented on CLOUDSTACK-8915:
--------------------------------------------
Github user bvbharatk commented on the pull request:
https://github.com/apache/cloudstack/pull/908#issuecomment-145441458
@remibergsma
Hi,
I see that currently we invoke the main function of configure.py every time
we call the update_config when a new config to vr is pushed.The main function
tries to process all the components again, even the once which are not
modified. IMHO this is not a good way to update vr config. We should only
configure things which are changed newly. I think we need to fix this as it is
not scalable and redoing the whole config again might result in restarting one
or many services like you said is happening with conntrackd. However i think we
can fix the conntrackd issue temporarily by copying the conntrackd to some non
standard location and run conntrackd using this config file.Currently the
config file is copied to a standard location in /etc, doing this will make sure
that the conntrackd will not be there when this script runs for the first time.
I do not know of any tests for conntrackd case and for the default routes
case in the isolated networks. I think we need to test this manually.
> Cannot SSH into VMs deployed Redundant VPC routers
> --------------------------------------------------
>
> Key: CLOUDSTACK-8915
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8915
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Virtual Router
> Affects Versions: 4.6.0
> Reporter: Wilder Rodrigues
> Assignee: Wilder Rodrigues
> Priority: Blocker
>
> The Marvin test under componenet/test_vpc_redundant.py no longer passes. I
> also tried to test it manually, but unfortunately the feature is now broken.
> * Create a Redundant VPC
> * Add a tier
> * Add a new VM to the tier
> * Add an ACL, open port 22 and associate the ACL with the tier
> * Acquire a pub IP
> * Add a PF rule to port 22 towards the VM
> * Try to SSH to the VM through the Pub IP
> It fails with "No route to host"
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
