Creating a lease using the CLI client without providing the start date can sometimes fail
Bug #1783296 reported by
Pierre Riteau
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Blazar |
Fix Released
|
Low
|
Pierre Riteau |
Bug Description
When the Blazar CLI client is run without specifying a start date, it uses the current time on the client machine. If the lease creation request is sent to the Blazar service just before the end of a minute (e.g. at 12:34:59), the Blazar manager might only process it during the next minute (e.g. after 12:35:00). In this case, the manager will reject the request with:
Start date must be later than current date
This can also be an issue if the clocks on the client and server are not synchronized closely.
description: | updated |
Changed in blazar: | |
assignee: | nobody → Pierre Riteau (priteau) |
milestone: | none → rocky-3 |
Changed in blazar: | |
status: | New → Fix Released |
importance: | Undecided → Low |
To post a comment you must log in.
This issue was fixed in the openstack/ python- blazarclient 2.0.0 release.