/org/open_power/control/enumerate
{
"/org/open_power/control/host0": {},
"/org/open_power/control/occ0": {
"OccActive": 0
},
"/org/open_power/control/occ1": {
"OccActive": 1
}
}
Enumerate shows the OCC objects
Accessing the occ attribute
/org/open_power/control/occ1/attr/OccActive
{
"description": "The specified property cannot be found: 'OccActive'"
}
And
/org/open_power/control/occ1/
[]
@gkeishin OccActive is supposed to be set only by the Host via IPMI anyway and I don't see any reason why an external client has any interest in it.
This does not defend the I can not see attribute via REST but I am saying the current behaviour does not affect the production code.
Matter of fact, the OccStatus should have been an Internal interface @williamspatrick ?
this seems like a rest server bug if the properties show up with enumerate but not when you access them directly.
With the @bradbishop fix.. looking good, Tanks
$ ./rest_cmd -i xx.xx.xx.xx -o GET -u /org/open_power/control/enumerate
Executing: GET /org/open_power/control/enumerate
/org/open_power/control/enumerate
{
"/org/open_power/control/host0": {},
"/org/open_power/control/occ0": {
"OccActive": 0
},
"/org/open_power/control/occ1": {
"OccActive": 0
}
}
$ ./rest_cmd -i xx.xx.xx.xx -o GET -u /org/open_power/control/occ0
Executing: GET /org/open_power/control/occ0
/org/open_power/control/occ0
{
"OccActive": 0
}
$ ./rest_cmd -i xx.xx.xx.xx -o GET -u /org/open_power/control/occ1
Executing: GET /org/open_power/control/occ1
/org/open_power/control/occ1
{
"OccActive": 0
}
$ ./rest_cmd -i xx.xx.xx.xx -o GET -u /org/open_power/control/occ0/attr/OccActive
Executing: GET /org/open_power/control/occ0/attr/OccActive
/org/open_power/control/occ0/attr/OccActive
0
$ ./rest_cmd -i xx.xx.xx.xx -o GET -u /org/open_power/control/occ1/attr/OccActive
Executing: GET /org/open_power/control/occ1/attr/OccActive
/org/open_power/control/occ1/attr/OccActive
0