Hi all -
I’ve just detected some more strange behavior in Cloudmonkey. If I have a cluster named, “cluster1”, in a zone named, “pod1” inside a zone named, “zone1”, I should be able to list it correctly, yes? (local) 🐵 > list clusters count = 1 cluster: name = cluster1 id = d2e79c24-88e4-40f8-9639-e262c6e85f03 allocationstate = Enabled clustertype = CloudManaged cpuovercommitratio = 1.0 hypervisortype = XenServer managedstate = Managed memoryovercommitratio = 1.0 podid = d27ea9af-4228-482b-89ff-0f36f74e5a48 podname = pod1 zoneid = e362b144-04db-4540-aa53-75d9e2ffa832 zonename = zone1 So why does this happen? (local) 🐵 > list clusters name=ster1 count = 1 cluster: name = cluster1 id = d2e79c24-88e4-40f8-9639-e262c6e85f03 allocationstate = Enabled clustertype = CloudManaged cpuovercommitratio = 1.0 hypervisortype = XenServer managedstate = Managed memoryovercommitratio = 1.0 podid = d27ea9af-4228-482b-89ff-0f36f74e5a48 podname = pod1 zoneid = e362b144-04db-4540-aa53-75d9e2ffa832 zonename = zone1 Note that it appears to match the trailing characters of the object’s name. I also verified that this happens for pods, but zones appear to manifest the correct behavior. Tested with Cloudmonkey 5.3.0 and a fresh checkout from github (5.3.1) using the master branch. Can anyone else replicate this? -I
