After dedicating some compute resources to a customer, Cloudstack correctly
created an Affinity Group called “DedicatedGrp-domain-custdomain.tld” and it’s
working as expected.
The issue we’re having is that now when other customers in different domains go
to create instances they see this affin
On 1/21/16, 2:52 PM, "Matthew M. Gamble" wrote:
>Trying to debug this again, I got the ip_associations.json that is being
>passed to the router on create:
>
>{
> "ip_address":[
> {
> "public_ip":"XXX.XX
":"ips"
}
The one thing I noticed is the trackback is an issue parsing the nic_dev_id
field, which makes sense, since the nic_dev_id field doesn’t exist in the json
file. So my question is, why is this field missing from the file and how to I
backtrace this issue further?
contact the sender if you
believe you have received this email in error.
From: Matthew M. Gamble mailto:mgam...@thoughtfire.ca>>
Sent: Wednesday, December 30, 2015 8:44 PM
To: users@cloudstack.apache.org<mailto:users@cloudstack.apache.org>
Subject: Cannot create VPC
When attemptin
When attempting to create a VPC using 4.7 (with the 4.6 system images) under
KVM, I’m getting the following error on the agent when it attempts to deploy
the virtual router:
{"results":["null - success:
null","null - failed: [INFO] update_config.py :: Processing incoming
file => ip_association
I’m running into an odd issues with a virtual router for an isolated guest
network on a new 4.6 installation.
The router is created successfully, however, when we assign a new static NAT IP
the IP isn’t being added to the VR – the source NAT IP is used instead. Right
now I have a VR that has t
