Since no one has responded I am considering this to be a bug, and created
an issue in JIRA: https://issues.apache.org/jira/browse/CLOUDSTACK-7844
We are willing to pay someone to help us determine if this behavior is
intended, and if not to come up with some patches to correct it.
Thank You,
Lo
Has anyone else had any luck replicating this issue?
Thank You,
Logan Barfield
Tranquil Hosting
On Fri, Oct 31, 2014 at 9:58 AM, Logan Barfield
wrote:
> Hi Jayapal,
>
> Can you try destroying/redeploying the Virtual Router after the IP
> reservation is set up? I didn't encounter the issue un
Hi Jayapal,
Can you try destroying/redeploying the Virtual Router after the IP
reservation is set up? I didn't encounter the issue until I restarted the
network with 'cleanup' checked.
Thank You,
Logan Barfield
Tranquil Hosting
On Fri, Oct 31, 2014 at 2:08 AM, Jayapal Reddy Uradi <
jayapalred
Hi,
I tried it in my environment (cloudstack 4.5), this issue is not seen.
Here is the output from the router.
root@r-19-QA:~# cat /var/cache/cloud/cmdline
root=UUID=fa9e76eb-51fd-4435-93e9-77bc9498ff09 ro debian-installer=en_US quiet
-- quiet console=hvc0 template=domP name=r-19-QA eth2ip=10.
Just trying to clear something up before I submit a bug report:
When using IP reservation in an isolated network it looks like the virtual
router is getting the wrong netmask.
For example:
- Network CIDR: 10.1.1.0/24
- Guest CIDR: 10.1.1.0/25
- Reserved IP Range: 10.1.1.127-10.1.1.254
- Virtual R
