diff --git a/releasenotes/notes/clean-actions-for-cluster-node-438ca5268e7fd258.yaml b/releasenotes/notes/clean-actions-for-cluster-node-438ca5268e7fd258.yaml new file mode 100644 index 000000000..4f2495359 --- /dev/null +++ b/releasenotes/notes/clean-actions-for-cluster-node-438ca5268e7fd258.yaml @@ -0,0 +1,5 @@ +--- +features: + - | + When a cluster or a node is deleted, the action records associated with + them are now automatically deleted from database. diff --git a/releasenotes/notes/cluster-check-interval-b01e8140cc83760e.yaml b/releasenotes/notes/cluster-check-interval-b01e8140cc83760e.yaml new file mode 100644 index 000000000..1f471048c --- /dev/null +++ b/releasenotes/notes/cluster-check-interval-b01e8140cc83760e.yaml @@ -0,0 +1,5 @@ +--- +features: + - | + A new configuration option check_interval_max is added (default=3600) for + cluster health check intervals. diff --git a/releasenotes/notes/db-action-retries-d471fe85b4510afd.yaml b/releasenotes/notes/db-action-retries-d471fe85b4510afd.yaml new file mode 100644 index 000000000..9a64b6914 --- /dev/null +++ b/releasenotes/notes/db-action-retries-d471fe85b4510afd.yaml @@ -0,0 +1,4 @@ +--- +other: + - | + DB layer operations now feature some retries if there are transient errors. diff --git a/releasenotes/notes/doc-fixes-e60bb1a486f67e0c.yaml b/releasenotes/notes/doc-fixes-e60bb1a486f67e0c.yaml new file mode 100644 index 000000000..5124344d7 --- /dev/null +++ b/releasenotes/notes/doc-fixes-e60bb1a486f67e0c.yaml @@ -0,0 +1,4 @@ +--- +fixes: + - | + Various bug fixes to the user manual and sample profiles/policies. diff --git a/releasenotes/notes/drop-py34-support-21e20efb9bf0b326.yaml b/releasenotes/notes/drop-py34-support-21e20efb9bf0b326.yaml new file mode 100644 index 000000000..e5c87438a --- /dev/null +++ b/releasenotes/notes/drop-py34-support-21e20efb9bf0b326.yaml @@ -0,0 +1,4 @@ +--- +deprecations: + - | + The support to py3.4 is dropped. Please use py3.5 instead. diff --git a/releasenotes/notes/fix-action-triggering-e880b02234028315.yaml b/releasenotes/notes/fix-action-triggering-e880b02234028315.yaml new file mode 100644 index 000000000..2157fa84c --- /dev/null +++ b/releasenotes/notes/fix-action-triggering-e880b02234028315.yaml @@ -0,0 +1,5 @@ +--- +fixes: + - | + When an action was marked as RETRY, its status is reset to READY for a + reschedule. A bug related to this behavior is now fixed. diff --git a/releasenotes/notes/fix-cooldown-5082711989ecd536.yaml b/releasenotes/notes/fix-cooldown-5082711989ecd536.yaml new file mode 100644 index 000000000..e1ac5ab9c --- /dev/null +++ b/releasenotes/notes/fix-cooldown-5082711989ecd536.yaml @@ -0,0 +1,4 @@ +--- +fixes: + - | + Fixed immature return from policy cooldown check. diff --git a/releasenotes/notes/fix-desired-when-omitted-e7ffc0aa72ab8cc9.yaml b/releasenotes/notes/fix-desired-when-omitted-e7ffc0aa72ab8cc9.yaml new file mode 100644 index 000000000..acc5bc382 --- /dev/null +++ b/releasenotes/notes/fix-desired-when-omitted-e7ffc0aa72ab8cc9.yaml @@ -0,0 +1,6 @@ +--- +fixes: + - | + Fixed a bug related to desired_capacity when creating a cluster. The old + behavior was having it default to 1, however, the correct behavior should + be having it default to min_size if provided. diff --git a/releasenotes/notes/fix-dup-of-action-dump-0b95a07adf3ccdba.yaml b/releasenotes/notes/fix-dup-of-action-dump-0b95a07adf3ccdba.yaml new file mode 100644 index 000000000..e9b264da0 --- /dev/null +++ b/releasenotes/notes/fix-dup-of-action-dump-0b95a07adf3ccdba.yaml @@ -0,0 +1,4 @@ +--- +fixes: + - | + Fixed a problem related to duplicated event dumps during action execution. diff --git a/releasenotes/notes/fix-node-status-for-lb-fc7714da09bec2fb.yaml b/releasenotes/notes/fix-node-status-for-lb-fc7714da09bec2fb.yaml new file mode 100644 index 000000000..c5574968f --- /dev/null +++ b/releasenotes/notes/fix-node-status-for-lb-fc7714da09bec2fb.yaml @@ -0,0 +1,6 @@ +--- +features: + - | + When a node cannot be added to a load-balancer although desired, or it can + not be removed from a load-balancer when requested, the node will be + marked as in WARNING status. diff --git a/releasenotes/notes/fix-recover-trigger-749600f500f7bf4a.yaml b/releasenotes/notes/fix-recover-trigger-749600f500f7bf4a.yaml new file mode 100644 index 000000000..f6a0718ba --- /dev/null +++ b/releasenotes/notes/fix-recover-trigger-749600f500f7bf4a.yaml @@ -0,0 +1,5 @@ +--- +fixes: + - | + Fixed error in the return value of node-check which prevents node-recover + from being triggered. diff --git a/releasenotes/notes/fix-registry-claim-5421dca1ed9b0783.yaml b/releasenotes/notes/fix-registry-claim-5421dca1ed9b0783.yaml new file mode 100644 index 000000000..c72613c3a --- /dev/null +++ b/releasenotes/notes/fix-registry-claim-5421dca1ed9b0783.yaml @@ -0,0 +1,5 @@ +--- +fixes: + - | + Fixed a problem when claiming a cluster from health registry if service + engine is stopped (killed) and restarted quickly. diff --git a/releasenotes/notes/fix-tag-for-stacks-2ef70be061e80253.yaml b/releasenotes/notes/fix-tag-for-stacks-2ef70be061e80253.yaml new file mode 100644 index 000000000..074e5b52f --- /dev/null +++ b/releasenotes/notes/fix-tag-for-stacks-2ef70be061e80253.yaml @@ -0,0 +1,5 @@ +--- +fixes: + - | + Fixed an error in updating stack tags when the stack joins or leaves a + cluster. diff --git a/releasenotes/notes/gc-for-dead-engine-2246c714edc9a2df.yaml b/releasenotes/notes/gc-for-dead-engine-2246c714edc9a2df.yaml new file mode 100644 index 000000000..2954968dd --- /dev/null +++ b/releasenotes/notes/gc-for-dead-engine-2246c714edc9a2df.yaml @@ -0,0 +1,6 @@ +--- +features: + - | + When an engine is detected to be dead, the actions (and the clusters/nodes + locked by those actions) are now unlocked. Such clusters and nodes can be + operated again. diff --git a/releasenotes/notes/health-check-interval-b3850c072600bfdf.yaml b/releasenotes/notes/health-check-interval-b3850c072600bfdf.yaml new file mode 100644 index 000000000..7d4d6b24f --- /dev/null +++ b/releasenotes/notes/health-check-interval-b3850c072600bfdf.yaml @@ -0,0 +1,5 @@ +--- +other: + - | + Sample health policy file was using 60 seconds as the interval which could + be misleading. This has been tuned to 600 seconds. diff --git a/releasenotes/notes/lb-support-to-recover-8f822d3c2665e225.yaml b/releasenotes/notes/lb-support-to-recover-8f822d3c2665e225.yaml new file mode 100644 index 000000000..72290edff --- /dev/null +++ b/releasenotes/notes/lb-support-to-recover-8f822d3c2665e225.yaml @@ -0,0 +1,5 @@ +--- +features: + - | + The load-balancing policy now properly supports the CLUSTER_RECOVER action + and NODE_RECOVER action. diff --git a/releasenotes/notes/node-check-before-recover-abf887a39ab0d355.yaml b/releasenotes/notes/node-check-before-recover-abf887a39ab0d355.yaml new file mode 100644 index 000000000..f59a0c0b8 --- /dev/null +++ b/releasenotes/notes/node-check-before-recover-abf887a39ab0d355.yaml @@ -0,0 +1,6 @@ +--- +features: + - | + API microversion 1.6 comes with an optional parameter 'check' that tells + the engine to perform a health check before doing actual recovery. + This applies to both clusters and nodes. diff --git a/releasenotes/notes/non-operation-recover-cf0f3c0ac62bb0f3.yaml b/releasenotes/notes/non-operation-recover-cf0f3c0ac62bb0f3.yaml new file mode 100644 index 000000000..7f9c05789 --- /dev/null +++ b/releasenotes/notes/non-operation-recover-cf0f3c0ac62bb0f3.yaml @@ -0,0 +1,5 @@ +--- +fixes: + - | + Fixed error that raises when no operation is provided during node health + recovery. diff --git a/releasenotes/notes/nova-az-fccf8db758642d34.yaml b/releasenotes/notes/nova-az-fccf8db758642d34.yaml new file mode 100644 index 000000000..e00cc17b7 --- /dev/null +++ b/releasenotes/notes/nova-az-fccf8db758642d34.yaml @@ -0,0 +1,5 @@ +--- +fixes: + - | + Fixed an error introduced by openstacksdk when checking/setting the + availability zone of a nova server. diff --git a/releasenotes/notes/profile-only-update-5cdb3ae46a8139a8.yaml b/releasenotes/notes/profile-only-update-5cdb3ae46a8139a8.yaml new file mode 100644 index 000000000..fcbe887cc --- /dev/null +++ b/releasenotes/notes/profile-only-update-5cdb3ae46a8139a8.yaml @@ -0,0 +1,7 @@ +--- +features: + - | + A new feature is introduced in API microversion 1.6 which permits a cluster + update operation to change the profile used by the cluster only without + actually updating the existing nodes (if any). The new profile will be used + when new nodes are created as members of the cluster. diff --git a/releasenotes/notes/resize-params-ab4942dc11f05d9a.yaml b/releasenotes/notes/resize-params-ab4942dc11f05d9a.yaml new file mode 100644 index 000000000..69c90672c --- /dev/null +++ b/releasenotes/notes/resize-params-ab4942dc11f05d9a.yaml @@ -0,0 +1,5 @@ +--- +other: + - | + The parameter checking for cluster-resize operation is revised so that + min_step will be ignored if the ajustment type is not CHANGE_IN_PERCENTAGE.