failed to complete the MAAS install

[Narinder Gupta]

With latest version of maas-deployer in proposed failing to install.

error: failed to get domain 'node1-control'
error: Domain not found: no domain with matching name 'node1-control'

Traceback (most recent call last):
  File "/usr/bin/maas-deployer", line 9, in <module>
    load_entry_point('maas-deployer==0.0.7', 'console_scripts', 'maas-deployer')()
  File "/usr/lib/python2.7/dist-packages/maas_deployer/cli.py", line 88, in main
    engine.deploy(target)
  File "/usr/lib/python2.7/dist-packages/maas_deployer/vmaas/engine.py", line 83, in deploy
    self.configure_maas(client, maas_config)
  File "/usr/lib/python2.7/dist-packages/maas_deployer/vmaas/engine.py", line 691, in configure_maas
    util.virsh(['start', name])
  File "/usr/lib/python2.7/dist-packages/maas_deployer/vmaas/util.py", line 136, in virsh
    return execc(_cmd, fatal=fatal)
  File "/usr/lib/python2.7/dist-packages/maas_deployer/vmaas/util.py", line 111, in execc
    output=stderr)
subprocess.CalledProcessError: Command 'virsh -c qemu:///system start node1-control' returned non-zero exit status 1
jenkins@jumphostpod6:~/opnfv/slave_root/workspace/joid-deploy-intel-pod6-daily-master/ci$

looks like this patch is breaking the deployment.

http://bazaar.launchpad.net/~hopem/maas-deployer/juju-default-series/revision/69

here is complete logs http://paste.ubuntu.com/16146918/

[Felipe Reyes (freyes)]

Narinder, thanks for filing this bug report. could you share a small yaml that reproduces the problem?. I've been using this yaml http://paste.ubuntu.com/16208277/

[Narinder Gupta (narindergupta)]

please find the yaml file which reproduces the problem. http://paste.ubuntu.com/16230580/

here are the changes which i made in yaml file based on new feature added into maas-deployer

http://paste.ubuntu.com/16230589/

here is the deployment.yaml which works with 0.6 and failed with proposed released of 0.7

http://paste.ubuntu.com/16230625/

[Narinder Gupta (narindergupta)]

correct diff http://paste.ubuntu.com/16230648/

[Narinder Gupta (narindergupta)]

Also from the error it looks like maas-deployer is trying to start the first node wchich uses qemu+ssh while in my case it is ipmi. May i know the reason for bringing node1 n your case? As per my understanding if you are trying to bootstrap then it should be bootstrap node which needs to be started rather than node1.