ERROR failed to bootstrap model: bootstrap instance started but did not change to Deployed state: instance "6d6c3x" failed to deploy

juju
,
1

Hi,

I am deploying canonical openstack using MAAS, am getting below error while installing “openstackLinuxKvm” , please help me out to solve this issue.

2019-11-24 20:16:39,888 [ERROR] conjure-up/openstack-base - common.py:60 - Error bootstrapping controller: ['Creating Juju controller "conjure-up-cloud-maas-32b-cca" on cloud-maas-32b', 'Looking for packaged Juju agent version 2.6.10 for amd64', 'Launching controller instance(s) on cloud-maas-32b...', ' - 6d6c3x (arch=amd64 mem=192G cores=48)', 'Installing Juju agent on bootstrap instance', 'Fetching Juju GUI 2.15.0', 'ERROR failed to bootstrap model: bootstrap instance started but did not change to Deployed state: instance "6d6c3x" failed to deploy']
2019-11-24 20:16:39,891 [DEBUG] conjure-up/openstack-base - events.py:52 - Setting Error at conjureup/events.py:149
2019-11-24 20:16:39,897 [ERROR] conjure-up/openstack-base - events.py:161 - Unhandled exception in <Task finished coro=<BaseBootstrapController.run() done, defined at /snap/conjure-up/1058/lib/python3.6/site-packages/conjureup/controllers/juju/bootstrap/common.py:15> exception=BootstrapError('Unable to bootstrap (cloud type: maas)',)>
Traceback (most recent call last):
  File "/snap/conjure-up/1058/lib/python3.6/site-packages/conjureup/controllers/juju/bootstrap/common.py", line 21, in run
    await self.do_bootstrap()
  File "/snap/conjure-up/1058/lib/python3.6/site-packages/conjureup/controllers/juju/bootstrap/common.py", line 65, in do_bootstrap
    app.provider.cloud_type))
conjureup.errors.BootstrapError: Unable to bootstrap (cloud type: maas)
2019-11-24 20:16:39,913 [DEBUG] conjure-up/openstack-base - __init__.py:27 - Showing dialog for exception: Unable to bootstrap (cloud type: maas)
1 Like
2

Hmm, it looks like Juju asked MAAS for a machine but the machine that was assigned never completed and got to the “Deployed” state in MAAS before Juju’s timeout (II think 10 minutes by default?) was hit.

That’s what this is saying

ERROR failed to bootstrap model: bootstrap instance started but did not change to Deployed state: instance "6d6c3x" failed to deploy

It might be worth trying to deploy that machine through MAAS manually and get a rough idea if it’ll deploy and come up and if so, how long that takes. You might need to adjust the timeout using the option on bootstrap (juju bootstrap --help for examples of using the timeout config setting)

1 Like
3

Thank you @rick_h,

If am triggering manual deployment from MAAS , it took around 15 - 20 min to complete the deployment.

am using juju version 2.6.X and its timeout value is 1200 Sec (20 min). And i increased timeout value 20 min to 30 min, and stated the deployment again, facing same issue.

and i am using external proxy server in my environment (10.144.1.10)

but in deployed node i could see following,

ubuntu@Node-106:/etc/apt/apt.conf.d$ cat /etc/environment
PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games"
ubuntu@Node-106:/etc/apt/apt.conf.d$ sudo vi /etc/environment
ubuntu@Node-106:/etc/apt/apt.conf.d$
ubuntu@Node-106:/etc/apt/apt.conf.d$ cat 90curtin-aptproxy
Acquire::http::Proxy “http://10.144.1.10:8080”;
ubuntu@Node-106:/etc/apt/apt.conf.d$ cat 95-juju-proxy-settings
Acquire::http::Proxy::“127.0.0.1” “DIRECT”;
Acquire::https::Proxy::“127.0.0.1” “DIRECT”;
Acquire::ftp::Proxy::“127.0.0.1” “DIRECT”;
Acquire::http::Proxy::“localhost” “DIRECT”;
Acquire::https::Proxy::“localhost” “DIRECT”;
Acquire::ftp::Proxy::“localhost” “DIRECT”;
Acquire::http::Proxy::"::1" “DIRECT”;
Acquire::https::Proxy::"::1" “DIRECT”;
Acquire::ftp::Proxy::"::1" “DIRECT”;
ubuntu@Node-106:/etc/apt/apt.conf.d$

90curtin-aptproxy is fine, but juju proxy-setting using a local host, is this fine ?

4

Some how i fixed with updating proxy in bootstrap.yaml

now juju bootstrap completed, trying for installing openstack components and getting i/o time out error, and i have stoped ufw, disabled and reset the same in MAAS server. still facing same issue. Any idea where am missing the configuration ?

2019-11-27 11:24:50,233 [DEBUG] conjure-up/openstack-base - websockets.protocol: protocol.py:886 - client < Frame(fin=True, opcode=1, data=b’{“request-id”:8,“error”:“cannot retrieve charm \“cs:ceph-mon-44\”: cannot get archive: Get https://api.jujucharms.com/charmstore/v5/ceph-mon-44/archive: dial tcp 162.213.33.121:443: i/o timeout”,“response”:{}}\n’, rsv1=False, rsv2=False, rsv3=False)

5

Hi
i’ve the same issue when try to make the bootstrap of juju controller

20:08:10 ERROR juju.cmd.juju.commands bootstrap.go:783 failed to bootstrap model: bootstrap instance started but did not change to Deployed state: instance "8epqeq" failed to deploy

have you resolved that?? I’ve also open a new topic. thanks

6

@rick_h
I’ve maybe resolved that issue, here my topic, I don’t know if that is a bug or no…

7

Setting the disk type to LVM in the maas settings fixed it for me after folowing that topic.

1 Like