om: set-errand-state doesn't seem to work with non-cf tiles
We have a tile that has a few post-deploy and pre-delete errands, as follows:
$> om ... errands -p the-tile
+--------------------+---------------------+--------------------+
| NAME | POST DEPLOY ENABLED | PRE DELETE ENABLED |
+--------------------+---------------------+--------------------+
| broker-registrar | true | |
| smoke-tests | true | |
| broker-deregistrar | | true |
+--------------------+---------------------+--------------------+
However, trying to disable any errands with set-errand-state doesn’t do anything.
$> om ... set-errand-state -p the-tile -e broker-deregistrar --pre-delete-state disabled
$> echo $? # 0
$> om ... set-errand-state -p the-tile -e broker-registrar --post-deploy-state disabled
$> echo $? # 0
$> om ... errands -p the-tile
+--------------------+---------------------+--------------------+
| NAME | POST DEPLOY ENABLED | PRE DELETE ENABLED |
+--------------------+---------------------+--------------------+
| broker-registrar | true | |
| smoke-tests | true | |
| broker-deregistrar | | true |
+--------------------+---------------------+--------------------+
$> ☹️
It works with om curl.
Similar commands all work fine on our ERT tile. It only seems to not-work with tiles not-called “cf”
with @totherme
About this issue
- Original URL
- State: closed
- Created 7 years ago
- Comments: 17 (9 by maintainers)
@DonBower thanks for the data, can you also send output with om curl (not just set-errand-state) when using “false” as a string instead of bool?
errands='{ "errands": [ { "pre_delete": "false", "name": "broker-deregistrar" }] }'