Results 1 to 2 of 2

Thread: How to Recover After a Failed juju or conjure-up deploy

  1. #1
    Join Date
    Sep 2019
    Beans
    3

    How to Recover After a Failed juju or conjure-up deploy

    Just tried to conjure-up Openstack NovaKVM and one box was not ready. So one box is listed as failed but the deployment is still waiting for it.

    I am using MAAS.

    I have the machine now in Ready status that should have the remaining deployment items which are still blocking other things.

    Out of the 4 needed machines, labeled 0-3, 2 is the remaining machine that errored out before.

    How do I retry machine 2. I am guessing if successful, my ready machine will move to allocated and then deploying in mass and in the Juju gui and with `juju status ` I will see the deployment resume.

    Thanks!

  2. #2
    Join Date
    Sep 2019
    Beans
    3

    Re: How to Recover After a Failed juju or conjure-up deploy

    I tried this as well.

    [last: 0s][~]$ juju retry-provisioning 2 --debug
    21:50:15 INFO juju.cmd supercommand.go:57 running juju [2.6.8 gc go1.10.4]
    21:50:15 DEBUG juju.cmd supercommand.go:58 args: []string{"/snap/juju/8873/bin/juju", "retry-provisioning", "2", "--debug"}
    21:50:15 INFO juju.juju api.go:67 connecting to API addresses: [192.168.0.131:17070]
    21:50:15 DEBUG juju.api apiclient.go:1092 successfully dialed "wss://192.168.0.131:17070/model/37236835-d3b3-4b2b-8087-5f60789c1e21/api"
    21:50:15 INFO juju.api apiclient.go:624 connection established to "wss://192.168.0.131:17070/model/37236835-d3b3-4b2b-8087-5f60789c1e21/api"
    21:50:15 DEBUG juju.api monitor.go:35 RPC connection died
    21:50:15 INFO cmd supercommand.go:502 command finished
    [last: 0s][~]$ juju --version
    2.6.8-bionic-amd64

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •