[
https://issues.apache.org/jira/browse/CLOUDSTACK-4717?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13801523#comment-13801523
]
Murali Reddy commented on CLOUDSTACK-4717:
------------------------------------------
Sailaja,
This bug purpose is to allow acquiring IP on to a network even when there is no
source NAT service is chosen in the network offering used to create the
network. The test you are run is correct by there is bug with VR, it can
support service combination of DHCP,DNS, LB. This is specific issue of VR. I
have opened a bug CLOUDSTACK-4918 for this. So please try this service
combination where LB service is provided by NetScaler.
> associate IP does not work on shared networks with out source NAT service
> -------------------------------------------------------------------------
>
> Key: CLOUDSTACK-4717
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4717
> 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
(v6.1#6144)
