cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-8793) Project Site-2-Site VPN Connection Fails to Register Correctly
Date Wed, 28 Oct 2015 14:02:27 GMT

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-8793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14978459#comment-14978459
] 

ASF GitHub Bot commented on CLOUDSTACK-8793:
--------------------------------------------

Github user pdube commented on the pull request:

    https://github.com/apache/cloudstack/pull/879#issuecomment-151854916
  
    @remibergsma I rebased and repushed. I will take some screen shots later! Thanks!


> Project Site-2-Site VPN Connection Fails to Register Correctly
> --------------------------------------------------------------
>
>                 Key: CLOUDSTACK-8793
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8793
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Projects
>    Affects Versions: 4.5.2
>         Environment: Clean install of ACS 4.5.2 on CentOS 6.6
>            Reporter: Geoff Higgibottom
>            Assignee: Patrick D.
>              Labels: project, vpc, vpn
>
> When trying to create a new Site-2-Site VPN Connection for a Project using the UI the
following error message is presented.
> "VPN connection can only be esitablished between same account's VPN gateway and customer
gateway!"
> Apart from the spelling mistake in the error message, the main issue is that the VPN
Connection fails to create as the VPN Customer Gateway is linked to the Logged in user account,
and not the Project.
> The VPN Gateway is correctly linked to the Project, as this was fixed in CLOUDSTACK-5409.
> Manually updating the ‘domain_id’ and ‘account_id’ values in the ‘s2s_vpn_connection’
table in the DB will result in the successful creation of the VPN Connection, but this connection
will not display in the UI or when querying via the API.
> The same error exists when using only the API so it is not a UI issue.
> This prevents the use of Site-2Site VPNs for VPCs belonging to Projects.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message