Current Series Release Notes¶
19.0.0-10¶
New Features¶
Registering a client returns the
uuidof the record along with itsclient_id.
GETandDELETE /v2/{project_id}/clients/{uuid}accept a clientuuidas well as aclient_id.
The command
freezer-manage db purgehas been added. It permanently deletes soft deleted rows. It accepts optional--age-in-days DAYSparameter to specify the age of the rows to delete. Default value is 30 days. Supported by the SQLAlchemy driver only.
Upgrade Notes¶
A client is identified by its project,
client_idandhostname. Several schedulers can register under oneclient_id, each with its own record. Before, a second scheduler took over the record of the first one.
A central
client_idis unique across all projects. A central registration is rejected if another project uses theclient_id, and any registration is rejected if another project uses it as a central client.
A registration with a
uuidthat has no record is rejected as not found. Register without theuuidto get a new record.
GETandDELETEwith aclient_idshared by several clients are rejected as unprocessable. Use theuuidinstead.
A job is now validated against every freezer-scheduler serving its client. Several schedulers may share a
client_idand the coordination ring may hand the job to any of them, so the job is refused unless all of them support its actions. It was previously checked against an arbitrary one of them, so a job the chosen scheduler could run was accepted even when a sibling could not, and that sibling then skipped it without saying so. The rejection names theuuidof the scheduler that lacks the capability; one that has been decommissioned, and is narrowing what its client supports, is removed withDELETE /v2/{project_id}/clients/{uuid}.
Bug Fixes¶
Deleting non-existent resources (
backups,jobs,actions,sessions, andclients) now returnsHTTP 404 Not Found(DocumentNotFound) instead ofHTTP 204 No Content, properly indicating when a resource cannot be deleted because it does not exist.
The ‘all_projects’ parameter in the jobs API was overwritten by the policy check, so admins always got jobs from all projects no matter what was in the request. The policy is now checked only when ‘all_projects’ is set to True. If the policy does not allow listing all projects, 403 Forbidden is returned.