juju/MAAS Tag constraints do not work in Precise

[Andres Rodriguez]

So I created a maas tag constraint, however, when deploying a node, the tagged nodes are not being selected. I created the tag as follows:

ubuntu@cluster2:/var/log/maas$ maas-cli admin tags new name='ram512' comment='Nodes with 512MB RAM' definition='//node[@id="memory"]/size > 524288000'

ubuntu@cluster2:/var/log/maas$ maas-cli admin tags list
[
    {
        "comment": "Nodes with 512MB RAM",
        "definition": "//node[@id=\"memory\"]/size > 524288000",
        "name": "ram512",
        "resource_uri": "/MAAS/api/1.0/tags/ram512/"
    }
]
ubuntu@cluster2:/var/log/maas$ maas-cli admin tag nodes ram512
[
    {
        "status": 4,
        "macaddress_set": [
            {
                "resource_uri": "/MAAS/api/1.0/nodes/node-6a13c942-090b-11e3-93bb-525400354c95/macs/00:16:3e:3e:aa:01/",
                "mac_address": "00:16:3e:3e:aa:01"
            }
        ],
        "netboot": true,
        "hostname": "node01",
        "power_type": "",
        "system_id": "node-6a13c942-090b-11e3-93bb-525400354c95",
        "architecture": "amd64/generic",
        "tag_names": [
            "ram512"
        ],
        "resource_uri": "/MAAS/api/1.0/nodes/node-6a13c942-090b-11e3-93bb-525400354c95/"
    },
    {
        "status": 4,
        "macaddress_set": [
            {
                "resource_uri": "/MAAS/api/1.0/nodes/node-661f1cc4-090b-11e3-b365-525400354c95/macs/00:16:3e:3e:aa:02/",
                "mac_address": "00:16:3e:3e:aa:02"
            }
        ],
        "netboot": true,
        "hostname": "node02",
        "power_type": "",
        "system_id": "node-661f1cc4-090b-11e3-b365-525400354c95",
        "architecture": "amd64/generic",
        "tag_names": [
            "ram512"
        ],
        "resource_uri": "/MAAS/api/1.0/nodes/node-661f1cc4-090b-11e3-b365-525400354c95/"
    }
]

Deployed as follows:

juju deploy mysql --constraints "maas-tags=ram512"

[Kapil Thangavelu (hazmat)]

what's the output of $ apt-cache policy juju on the bootstrap node. i assume this is precise with juju-origin:ppa ?

[Andres Rodriguez (andreserl)]

Correct!

[Kapil Thangavelu (hazmat)]

the behavior of juju-origin: ppa varies by client version and installation mechanism (a questionable choice that's embedded in the packaging), could confirm the version of juju on the bootstrap server per previous.

[Rajiv Shah (rajivshah3)]

Hi Andres,
Do you mind running sudo apt-get install python-launchpadlib and then running apport-collect 1214172 ? This will provide us with some logs to help the developers solve this bug.

Thanks,
Rajiv