Juju agent status remains "Allocating" and is not starting on MAAS 2.0 when --storage option is used

[Shilpa Kaul]

Hi,

I am trying to deploy a charm on MAAS 2.0 and making use of Juju Storage 
feature, so when I deploy my charm as shown below:
juju deploy  ibm-spectrum-scale  --storage disks=maas, the machine gets 
started and status on MAAS is "deployed" but the juju agent does not 
start. The agent message is "agent initializing" and nothing happens after 
that.

The same charm gets deployed if I dont give the --storage parameter during 
deploy time or use --storage disks=loop. This issue is seen only when i 
deploy the charm with --storage disks=maas. I have tried deploying the 
charm on AWS environment with --storage disks=ebs, there it works fine and 
no issues are seen.

In the juju logs I see the below messages:
to agent config as ["192.168.100.101:17070" "192.168.122.101:17070"]
2016-11-08 17:47:59 ERROR juju.worker.dependency engine.go:539 
"metric-collect" manifold worker returned unexpected error: failed to read 
charm from: /var/lib/juju/agents/unit-ibm-spectrum-scale-manager2-2/charm: 
stat /var/lib/juju/agents/unit-ibm-spectrum-scale-manager2-2/charm: no 
such file or directory
2016-11-08 17:47:59 INFO juju.worker.leadership tracker.go:184 
ibm-spectrum-scale-manager2/2 will renew ibm-spectrum-scale-manager2 
leadership at 2016-11-08 17:48:29.13919966 +0000 UTC
2016-11-08 17:47:59 INFO juju.worker.meterstatus connected.go:112 skipped 
"meter-status-changed" hook (missing)
2016-11-08 17:47:59 INFO worker.uniter.jujuc tools.go:20 ensure jujuc 
symlinks in /var/lib/juju/tools/unit-ibm-spectrum-scale-manager2-2
2016-11-08 17:47:59 INFO worker.uniter.jujuc tools.go:40 was a symlink, 
now looking at /var/lib/juju/tools/2.0.1-xenial-amd64
2016-11-08 17:47:59 INFO juju.worker.uniter uniter.go:159 unit 
"ibm-spectrum-scale-manager2/2" started
2016-11-08 17:47:59 INFO juju.worker.uniter uniter.go:168 resuming charm 
install
2016-11-08 17:47:59 INFO juju.worker.uniter.charm bundles.go:77 
downloading local:xenial/ibm-spectrum-scale-manager2-3 from API server
2016-11-08 17:47:59 INFO juju.downloader download.go:111 downloading from 
local:xenial/ibm-spectrum-scale-manager2-3
2016-11-08 17:47:59 INFO juju.downloader download.go:94 download complete 
("local:xenial/ibm-spectrum-scale-manager2-3")
2016-11-08 17:47:59 INFO juju.downloader download.go:174 download verified 
("local:xenial/ibm-spectrum-scale-manager2-3")

I compared the logs of the charm that I deployed on AWS and MAAS. In AWS 
also when I deploy the charm, same messages are logged, the only 
difference is that there its resuming the correct unit ie 
ibm-spectrum-scale-manager2-2, but in case of MAAS, it resumes for unit 
ibm-spectrum-scale-manager2-3 which does not exist. 

Can anyone please help me in resolving this issue, I  need to test my 
charm deployment on MAAS making use of juju storage, but unable to do so 
due to the above noted behavior.

Thanks and Regards,
Shilpa Kaul


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/juju/attachments/20161108/629c4747/attachment.html>