Juju error "No matching node is available" when specifying maas-name constraint with a fqdn

Bug #1130215 reported by Ramon Acedo
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
pyjuju
Triaged
Low
Unassigned

Bug Description

When specifying maas-name=node1.domain.net as a constraint an error is triggered as follows:

$ juju bootstrap --constraints "maas-name=node1.domain.net"
2013-02-19 11:17:27,341 INFO Bootstrapping environment 'maas' (origin: distro type: maas)...

When the domain is removed then it works:

$ juju bootstrap --constraints "maas-name=node1"
2013-02-19 11:17:38,886 INFO Bootstrapping environment 'maas' (origin: distro type: maas)...
2013-02-19 11:17:39,503 INFO 'bootstrap' command finished successfully

The MAAS nodes are all with the fqdn set in MAAAS:

$ sudo maas-cli root nodes list |egrep hostname
        "hostname": "node1.domain.net",
        "hostname": "node2.domain.net",

The maas version is: 0.2+1.2+bzr1349+dfsg-0+1349+157~ppa0~quantal1
The juju version is: 0.6.0.1+bzr615-0juju2~quantal1

Curtis Hovey (sinzui)
Changed in juju:
importance: Undecided → Low
status: New → Triaged
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.