cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daan Hoogland (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-3357) network domain for a vpc is not propagated to the virtual router
Date Mon, 29 Jul 2013 19:47:49 GMT


Daan Hoogland commented on CLOUDSTACK-3357:

H Sheng,

Both describe scenarios describe the current situation. The first,
ping vm1 doesn't work in vm2, is
the more specific I think as the second could be resolved outside the
vpc. I will update the ticket tomorrow.

I think adding both fields to cloud.conf would work and I will test
that with a colleague.


> network domain for a vpc is not propagated to the virtual router
> ----------------------------------------------------------------
>                 Key: CLOUDSTACK-3357
>                 URL:
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>    Affects Versions: 4.0.2, 4.1.0
>            Reporter: Daan Hoogland
>            Assignee: Daan Hoogland
>              Labels: integration-test
>             Fix For: 4.2.0
> network domain for a vpc is propagated to the database but not to the virtual routers.
> When creating a new VPC, a network domain is given .This domain would be expected to
be used in the dns resolution for hosts and be programmed into /etc/dnsmasq.conf on the virtual
router (containing the dns for that network). That file is not touched at all, however.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message