On folsom, even with the "s", the update is still accepted :
# quantum subnet-update cb4f7e7e-3152-4c5b-a620-9b9bd5b75ac3 --allocation-pools start=10.0.13.210,end=10.0.13.254 Updated subnet: cb4f7e7e-3152-4c5b-a620-9b9bd5b75ac3
May be we should split this bug in two bugs : 1 : folsom bug on subnet-update --allocation-pools with a grizzly backport 2 : this bug about errors in keys
On folsom, even with the "s", the update is still accepted :
# quantum subnet-update cb4f7e7e- 3152-4c5b- a620-9b9bd5b75a c3 --allocation-pools start=10. 0.13.210, end=10. 0.13.254 3152-4c5b- a620-9b9bd5b75a c3
Updated subnet: cb4f7e7e-
May be we should split this bug in two bugs :
1 : folsom bug on subnet-update --allocation-pools with a grizzly backport
2 : this bug about errors in keys