Rocky Series Release Notes¶
Creating leases using version 2.0.0 of the CLI client without specifying a start date was failing with the error
The lease parameters are incorrect, following changes related to bug 1783296. For more details, see bug 1784038.
When there are multiple leases with the same name, lease actions identifying the lease by name would display an error message including a dictionary of lease values, instead of
type 'lease'. For more details, see bug 1786030.
When creating a lease using the CLI client, the default value for start date was changed to use the string ‘now’, which is resolved to the current time on the server rather than on the client. Note that if the request is sent at the end of a minute and interpreted by the service at the beginning of the next minute, this can result in leases that are one minute shorter than what the user might expect, as the end date is still specified by the client. Users who care about the exact timing of their leases should explicitly specify both start and end dates.
When the blazar CLI client got an error code from the blazar server, it didn’t display error messages created in the blazar server. Instead, it displayed messages created in keystoneauth with poor information. See the bug report for example. It was fixed to display original error messages which include useful information.
Creating a lease using the CLI client without specifying a start date no longer fails if the request is sent to the Blazar service just before the end of a minute. For more details, see bug 1783296.
The region name value provided via an environment variable or a command line argument is now respected by the client. Without this fix, the wrong reservation endpoint could be selected in a multi-region cloud.