cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Murali Reddy (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-4717) associate IP does not work on shared networks with out source NAT service
Date Wed, 23 Oct 2013 08:17:47 GMT


Murali Reddy commented on CLOUDSTACK-4717:

Please close the bug. If you find any issue with service combination with VR as provider,
please log the details in to 4918.

> associate IP does not work on shared networks with out source NAT service
> -------------------------------------------------------------------------
>                 Key: CLOUDSTACK-4717
>                 URL:
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Network Controller
>    Affects Versions: 4.2.0
>            Reporter: Murali Reddy
>            Assignee: Murali Reddy
>            Priority: Critical
>             Fix For: 4.2.1
> 'shared network' with only DNS, DHCP and LB service provided by CloudStack is a valid
service combination. in this case gateway is defined externally and cloudstack does not provide
any nat service. But currently there is restriction that in order to acquire an IP to a network
source nat service should have been enabled on the network. So effectively IP can not be acquired
and no LB rules can be created.
> Currenrly acquiring IP on to a network with no source NAT service will throw error:
> "In zone of type Advanced ip address can be associated only to the network of guest type
Isolated with the SourceNat enabled"
> Fix should be relax the restriction the source nat ip to enabled on the network on which
ip is being acquired.

This message was sent by Atlassian JIRA

View raw message