Thanks, Marco. `juju status --format yaml` <- http://paste.ubuntu.com/21818491/
The messages for the machines show "Security group sg-9d6c8ce7 and subnet subnet-930c61b8 belong to different networks. (InvalidParameter)'" This seems odd, as the subnet I've bootstrapped to is 'subnet-930c61b8' On Mon, Aug 1, 2016 at 2:53 PM, Marco Ceppi <[email protected]> wrote: > What does `juju status --format yaml` produce? it should provide more > fruitful machine errors. > > Marco > > On Mon, Aug 1, 2016 at 5:46 PM James Beedy <[email protected]> wrote: > >> I'm having some issues with deploying instances to network spaces on aws. >> >> Problem: Instance errors on deploy >> >> I have successfully bootstrapped into my aws vpc with `juju bootstrap >> mycloud aws --credential mycred --config vpc-id=my-vpcid--config >> force-vpc-id='true' --upload-tools` and subsequently created a model on >> my aws controller in the vpc with `juju add-model my-new-model -credential >> mycred --config vpc-id=my-vpcid --config force-vpc-id='true'`. Following >> which, I add a network space, and then my subnet -> >> http://paste.ubuntu.com/21814798/. Ok, everything looks great so far >> .... then I go and launch an instance and it all falls apart -> >> http://paste.ubuntu.com/21815678/ >> >> Any insight into what is going on here would be greatly appreciated. Are >> these network spaces ops even supported on aws? >> >> ~thanks >> -- >> Juju-dev mailing list >> [email protected] >> Modify settings or unsubscribe at: >> https://lists.ubuntu.com/mailman/listinfo/juju-dev >> >
-- Juju-dev mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
