Adam Stokes comments

Results 111 comments of


                                            Adam Stokes

trafficstars

ERROR failed to bootstrap model: bootstrap instance started but did not change to Deployed state: instance "XXXXX" is started but not deployed

We don't support manually powering on/off the machines during a deployment.

ERROR failed to bootstrap model: bootstrap instance started but did not change to Deployed state: instance "XXXXX" is started but not deployed

@deepsidhu1313 way ahead of you :) https://github.com/conjure-up/conjure-up/issues/1021

ERROR failed to bootstrap model: bootstrap instance started but did not change to Deployed state: instance "XXXXX" is started but not deployed

As far as I know manual power option is not disabled, however, it is not supported. If it worked prior to 2.1.5 it should work the same way as 2.1.3...

ERROR failed to bootstrap model: bootstrap instance started but did not change to Deployed state: instance "XXXXX" is started but not deployed

@muthu883 I dont think there is an official fix for it yet which is why no documentation exists

Allow adding units in architect screen

@mikemccracken ok good i was hoping you'd say that :)

conjure-down

ah.. this is an issue with the configure hook in the snap install, lemme get a fix out

conjure-down

Try with just `juju kill-controller conjure-up-localhost-763`

conjure-down

Working on a fix for the first issue now

conjure-down

You may have to delete the containers via `lxc delete`, sorry about that and thanks for finding this error :D

Ok, if you haven't gone through and deleted your containers I found where that certificate error was coming from. In your `~/.local/share/juju/credentials.yaml` there is now a certificate craeted for 'localhost'...