| 2016-06-14 08:27:06 |
Domhnall Walsh |
bug |
|
|
added bug |
| 2016-06-14 10:03:38 |
Domhnall Walsh |
freezer: assignee |
|
Domhnall Walsh (domhnall-walsh) |
|
| 2016-06-14 10:23:10 |
Domhnall Walsh |
freezer: assignee |
Domhnall Walsh (domhnall-walsh) |
|
|
| 2016-07-06 17:43:51 |
Pierre-Arthur MATHIEU |
freezer: status |
New |
Triaged |
|
| 2016-07-06 17:43:55 |
Pierre-Arthur MATHIEU |
freezer: importance |
Undecided |
Low |
|
| 2016-12-04 12:59:57 |
Partha Bera |
freezer: assignee |
|
Partha Bera (partha.b) |
|
| 2016-12-28 08:56:07 |
OpenStack Infra |
freezer: status |
Triaged |
In Progress |
|
| 2023-11-01 07:51:12 |
suzhengwei |
description |
There is no way within the Freezer API to update a client's information after it's been POSTed other than to delete it and create it again.
There is no HTTP PUT/POST/PATCH support for this, despite the fact that the Readme alludes to that possibility. |
There is no way within the Freezer API to update a client's information after it's been POSTed other than to delete it and create it again.
There is no HTTP PUT/POST/PATCH support for this, despite the fact that the Readme alludes to that possibility.
If there is mechanism to update clients heartbeat to api, once freezer client
is found not up, users could bring the client back to up status. |
|
| 2023-11-01 08:29:11 |
suzhengwei |
description |
There is no way within the Freezer API to update a client's information after it's been POSTed other than to delete it and create it again.
There is no HTTP PUT/POST/PATCH support for this, despite the fact that the Readme alludes to that possibility.
If there is mechanism to update clients heartbeat to api, once freezer client
is found not up, users could bring the client back to up status. |
There is no way within the Freezer API to update a client's information after it's been POSTed other than to delete it and create it again.
There is no HTTP PUT/POST/PATCH support for this, despite the fact that the Readme alludes to that possibility. |
|
