keystoneclient can not change tenant state of enable or disable

[Yaguang Tang]

I have a keystone running and i created a tenant name demo
Now am trying to disable it with command below.

# keystone tenant-get 28b652ae29d941d78f67b754e2d3ff67

+-------------+----------------------------------+
| Property | Value |
+-------------+----------------------------------+
| description | demo tenant |
| enabled | True |
| id | 28b652ae29d941d78f67b754e2d3ff67 |
| name | demo |
+-------------+----------------------------------+

# keystone tenant-update --name=demo --enabled=False 28b652ae29d941d78f67b754e2d3ff67 OR
#keystone tenant-update --name=demo --enabled=false 28b652ae29d941d78f67b754e2d3ff67

I don`t get any error msg. Am i doing something wrong?

#keystone tenant-get 28b652ae29d941d78f67b754e2d3ff67

+-------------+----------------------------------+
| Property | Value |
+-------------+----------------------------------+
| description | demo tenant |
| enabled | True |
| id | 28b652ae29d941d78f67b754e2d3ff67 |
| name | demo |
+-------------+----------------------------------+

It does notthing.

Am i hitting a Bug?

[Joseph Heck (heckj)]

I believe this was an issue that was fixed in the code just a day or so ago. Could you verify you have the latest code from trunk and let us know if you're still seeing this?

If you're working from a package, that package may need updating.

marking this as a duplicate of 953678

[Dolph Mathews (dolph)]

The bug is that keystoneclient is evaluating the string as a boolean, so as a workaround, you might try --enabled='' (I'm just guessing) until the next RC is packaged.