diff --git a/changelog/8.18.7.yaml b/changelog/8.18.7.yaml new file mode 100644 index 00000000000..b6d877bab0c --- /dev/null +++ b/changelog/8.18.7.yaml @@ -0,0 +1,138 @@ +version: 8.18.7 +entries: + - kind: bug-fix + summary: Retry service start command upon failure with 30-second delay. + description: "" + component: elastic-agent + pr: + - https://github.com/elastic/elastic-agent/pull/9313 + issue: [] + impact: "" + action: "" + timestamp: 1755283748 + file: + name: 1755283748-service-retry-install.yaml + checksum: 886d72511d47a5cae4f6cfbe361058fc784c1ed2 + - kind: enhancement + summary: Bump kube-stack Helm Chart to 0.9.1 and enable the cluster collector + description: "" + component: elastic-agent + pr: + - https://github.com/elastic/elastic-agent/pull/9535 + issue: [] + impact: "" + action: "" + timestamp: 1755873563 + file: + name: 1755873563-bump_kube_stack.yaml + checksum: 426353e1b9973af91cbc457becf854ad8326f9a7 + - kind: security + summary: redact secrets from pre-config, computed-config, components-expected, and components-actual files in diagnostics archive + description: "" + component: elastic-agent + pr: + - https://github.com/elastic/elastic-agent/pull/9560 + issue: [] + impact: "" + action: "" + timestamp: 1756122869 + file: + name: 1756122869-update-secret-redaction-in-diagnostics.yaml + checksum: 3fe28334e7831c7910a2161097c1643797fc6ef7 + - kind: bug-fix + summary: fix reporting of scheduled upgrade details across restarts and cancels + description: "" + component: elastic-agent + pr: + - https://github.com/elastic/elastic-agent/pull/9562 + issue: + - https://github.com/elastic/elastic-agent/issues/8778 + impact: "" + action: "" + timestamp: 1756218044 + file: + name: 1756218044-fix-upgrade-details-state.yaml + checksum: 9677e35d59df7dfef2ff540d19d9f05d7017ede1 + - kind: bug-fix + summary: enable root user to re-enroll unprivileged agent for mac and linux + description: "" + component: elastic-agent + pr: + - https://github.com/elastic/elastic-agent/pull/9603 + issue: + - https://github.com/elastic/elastic-agent/issues/8544 + impact: "" + action: "" + timestamp: 1756313785 + file: + name: 1756313785-enable-root-user-to-re-enroll-unprivileged-agent-for-mac-and-linux.yaml + checksum: 0f9fb2207e09b12416a5e661dde758f8d432b13f + - kind: bug-fix + summary: Fix missing liveness healthcheck during container enrollment + description: "" + component: elastic-agent + pr: + - https://github.com/elastic/elastic-agent/pull/9612 + issue: + - https://github.com/elastic/elastic-agent/issues/9611 + impact: "" + action: "" + timestamp: 1756325090 + file: + name: 1756325090-Fix-missing-liveness-healthcheck-during-container-enrollment.yaml + checksum: de9a5a42d9b6603cba3b3bf19596eb3213e892f6 + - kind: bug-fix + summary: enable admin user to re-enroll unprivileged agent for windows + description: "" + component: elastic-agent + pr: + - https://github.com/elastic/elastic-agent/pull/9623 + issue: + - https://github.com/elastic/elastic-agent/issues/8544 + impact: "" + action: "" + timestamp: 1756433743 + file: + name: 1756433743-enable-root-user-to-re-enroll-unprivileged-agent-for-windows.yaml + checksum: 65a96ffe81178578e80d9e800ebc31cf74a26d82 + - kind: enhancement + summary: Enhanced loggers for easier debugging of upgrade related issues. + description: "" + component: elastic-agent + pr: + - https://github.com/elastic/elastic-agent/pull/9689 + issue: + - https://github.com/elastic/elastic-agent/issues/9536 + impact: "" + action: "" + timestamp: 1756833043 + file: + name: 1756833043-enhance-upgrade-action-loggers.yaml + checksum: 14a08bc69878adbea5e5b81bdd507edb34c9d096 + - kind: bug-fix + summary: Treat exit code 284 from Endpoint binary as non-fatal + description: "" + component: elastic-agent + pr: + - https://github.com/elastic/elastic-agent/pull/9687 + issue: [] + impact: "" + action: "" + timestamp: 1756921212 + file: + name: 1756921212-endpoint-284-non-fatal.yaml + checksum: 958a1547c78ab758322016e0a672f726eecb0a80 + - kind: bug-fix + summary: ensure failed upgrade actions are removed from queue and details are set + description: "" + component: elastic-agent + pr: + - https://github.com/elastic/elastic-agent/pull/9634 + issue: + - https://github.com/elastic/elastic-agent/issues/9629 + impact: "" + action: "" + timestamp: 1757079091 + file: + name: 1757079091-fix-stale-upgrade-actions.yaml + checksum: b79516aaa48bcf3e06e746295c4f23b32df1b1b2 diff --git a/changelog/8.18.7/breaking.md b/changelog/8.18.7/breaking.md new file mode 100644 index 00000000000..d29183a3c32 --- /dev/null +++ b/changelog/8.18.7/breaking.md @@ -0,0 +1,3 @@ +## 8.18.7 [-8.18.7-breaking-changes] + +_No breaking changes._ diff --git a/changelog/8.18.7/deprecations.md b/changelog/8.18.7/deprecations.md new file mode 100644 index 00000000000..1f60fd369d9 --- /dev/null +++ b/changelog/8.18.7/deprecations.md @@ -0,0 +1,3 @@ +## 8.18.7 [-8.18.7-deprecations] + +_No deprecations._ diff --git a/changelog/8.18.7/index.md b/changelog/8.18.7/index.md new file mode 100644 index 00000000000..3b005e1c039 --- /dev/null +++ b/changelog/8.18.7/index.md @@ -0,0 +1,20 @@ +## 8.18.7 [-release-notes-8.18.7] + + +### Features and enhancements [-8.18.7-features-enhancements] + +* Bump kube-stack Helm Chart to 0.9.1 and enable the cluster collector. [#9535](https://github.com/elastic/elastic-agent/pull/9535) +* Enhanced loggers for easier debugging of upgrade related issues. [#9536](https://github.com/elastic/elastic-agent/issues/9536) + + +### Fixes [-8.18.7-fixes] + +* Redact secrets from pre-config, computed-config, components-expected, and components-actual files in diagnostics archive. [#9560](https://github.com/elastic/elastic-agent/pull/9560) +* Retry service start command upon failure with 30-second delay. [#9313](https://github.com/elastic/elastic-agent/pull/9313) +* Fix reporting of scheduled upgrade details across restarts and cancels. [#9562](https://github.com/elastic/elastic-agent/pull/9562) [#8778](https://github.com/elastic/elastic-agent/issues/8778) +* Enable root user to re-enroll unprivileged agent for mac and linux. [#9603](https://github.com/elastic/elastic-agent/pull/9603) [#8544](https://github.com/elastic/elastic-agent/issues/8544) +* Fix missing liveness healthcheck during container enrollment. [#9612](https://github.com/elastic/elastic-agent/pull/9612) [#9611](https://github.com/elastic/elastic-agent/issues/9611) +* Enable admin user to re-enroll unprivileged agent for windows. [#9623](https://github.com/elastic/elastic-agent/pull/9623) [#8544](https://github.com/elastic/elastic-agent/issues/8544) +* Treat exit code 284 from Endpoint binary as non-fatal. [#9687](https://github.com/elastic/elastic-agent/pull/9687) +* Ensure failed upgrade actions are removed from queue and details are set. [#9634](https://github.com/elastic/elastic-agent/pull/9634) [#9629](https://github.com/elastic/elastic-agent/issues/9629) + diff --git a/changelog/fragments/1755283748-service-retry-install.yaml b/changelog/fragments/1755283748-service-retry-install.yaml deleted file mode 100644 index f4fb880a8e0..00000000000 --- a/changelog/fragments/1755283748-service-retry-install.yaml +++ /dev/null @@ -1,32 +0,0 @@ -# Kind can be one of: -# - breaking-change: a change to previously-documented behavior -# - deprecation: functionality that is being removed in a later release -# - bug-fix: fixes a problem in a previous version -# - enhancement: extends functionality but does not break or fix existing behavior -# - feature: new functionality -# - known-issue: problems that we are aware of in a given version -# - security: impacts on the security of a product or a user’s deployment. -# - upgrade: important information for someone upgrading from a prior version -# - other: does not fit into any of the other categories -kind: bug-fix - -# Change summary; a 80ish characters long description of the change. -summary: Retry service start command upon failure with 30-second delay. - -# Long description; in case the summary is not enough to describe the change -# this field accommodate a description without length limits. -# NOTE: This field will be rendered only for breaking-change and known-issue kinds at the moment. -#description: - -# Affected component; usually one of "elastic-agent", "fleet-server", "filebeat", "metricbeat", "auditbeat", "all", etc. -component: elastic-agent - -# PR URL; optional; the PR number that added the changeset. -# If not present is automatically filled by the tooling finding the PR where this changelog fragment has been added. -# NOTE: the tooling supports backports, so it's able to fill the original PR number instead of the backport PR number. -# Please provide it if you are adding a fragment for a different PR. -pr: https://github.com/elastic/elastic-agent/pull/9313 - -# Issue URL; optional; the GitHub issue related to this changeset (either closes or is part of). -# If not present is automatically filled by the tooling with the issue linked to the PR number. -#issue: https://github.com/owner/repo/1234 diff --git a/changelog/fragments/1755873563-bump_kube_stack.yaml b/changelog/fragments/1755873563-bump_kube_stack.yaml deleted file mode 100644 index e3563a0b686..00000000000 --- a/changelog/fragments/1755873563-bump_kube_stack.yaml +++ /dev/null @@ -1,32 +0,0 @@ -# Kind can be one of: -# - breaking-change: a change to previously-documented behavior -# - deprecation: functionality that is being removed in a later release -# - bug-fix: fixes a problem in a previous version -# - enhancement: extends functionality but does not break or fix existing behavior -# - feature: new functionality -# - known-issue: problems that we are aware of in a given version -# - security: impacts on the security of a product or a user’s deployment. -# - upgrade: important information for someone upgrading from a prior version -# - other: does not fit into any of the other categories -kind: enhancement - -# Change summary; a 80ish characters long description of the change. -summary: Bump kube-stack Helm Chart to 0.9.1 and enable the cluster collector - -# Long description; in case the summary is not enough to describe the change -# this field accommodate a description without length limits. -# NOTE: This field will be rendered only for breaking-change and known-issue kinds at the moment. -#description: - -# Affected component; usually one of "elastic-agent", "fleet-server", "filebeat", "metricbeat", "auditbeat", "all", etc. -component: elastic-agent - -# PR URL; optional; the PR number that added the changeset. -# If not present is automatically filled by the tooling finding the PR where this changelog fragment has been added. -# NOTE: the tooling supports backports, so it's able to fill the original PR number instead of the backport PR number. -# Please provide it if you are adding a fragment for a different PR. -#pr: https://github.com/owner/repo/1234 - -# Issue URL; optional; the GitHub issue related to this changeset (either closes or is part of). -# If not present is automatically filled by the tooling with the issue linked to the PR number. -#issue: https://github.com/owner/repo/1234 diff --git a/changelog/fragments/1756122869-update-secret-redaction-in-diagnostics.yaml b/changelog/fragments/1756122869-update-secret-redaction-in-diagnostics.yaml deleted file mode 100644 index b6b27ffb032..00000000000 --- a/changelog/fragments/1756122869-update-secret-redaction-in-diagnostics.yaml +++ /dev/null @@ -1,32 +0,0 @@ -# Kind can be one of: -# - breaking-change: a change to previously-documented behavior -# - deprecation: functionality that is being removed in a later release -# - bug-fix: fixes a problem in a previous version -# - enhancement: extends functionality but does not break or fix existing behavior -# - feature: new functionality -# - known-issue: problems that we are aware of in a given version -# - security: impacts on the security of a product or a user’s deployment. -# - upgrade: important information for someone upgrading from a prior version -# - other: does not fit into any of the other categories -kind: security - -# Change summary; a 80ish characters long description of the change. -summary: redact secrets from pre-config, computed-config, components-expected, and components-actual files in diagnostics archive - -# Long description; in case the summary is not enough to describe the change -# this field accommodate a description without length limits. -# NOTE: This field will be rendered only for breaking-change and known-issue kinds at the moment. -#description: - -# Affected component; usually one of "elastic-agent", "fleet-server", "filebeat", "metricbeat", "auditbeat", "all", etc. -component: elastic-agent - -# PR URL; optional; the PR number that added the changeset. -# If not present is automatically filled by the tooling finding the PR where this changelog fragment has been added. -# NOTE: the tooling supports backports, so it's able to fill the original PR number instead of the backport PR number. -# Please provide it if you are adding a fragment for a different PR. -pr: https://github.com/elastic/elastic-agent/pull/9560 - -# Issue URL; optional; the GitHub issue related to this changeset (either closes or is part of). -# If not present is automatically filled by the tooling with the issue linked to the PR number. -#issue: https://github.com/owner/repo/1234 diff --git a/changelog/fragments/1756218044-fix-upgrade-details-state.yaml b/changelog/fragments/1756218044-fix-upgrade-details-state.yaml deleted file mode 100644 index f69339423d2..00000000000 --- a/changelog/fragments/1756218044-fix-upgrade-details-state.yaml +++ /dev/null @@ -1,5 +0,0 @@ -kind: bug-fix -summary: fix reporting of scheduled upgrade details across restarts and cancels -component: elastic-agent -pr: https://github.com/elastic/elastic-agent/pull/9562 -issue: https://github.com/elastic/elastic-agent/issues/8778 \ No newline at end of file diff --git a/changelog/fragments/1756313785-enable-root-user-to-re-enroll-unprivileged-agent-for-mac-and-linux.yaml b/changelog/fragments/1756313785-enable-root-user-to-re-enroll-unprivileged-agent-for-mac-and-linux.yaml deleted file mode 100644 index 73bc6c9e266..00000000000 --- a/changelog/fragments/1756313785-enable-root-user-to-re-enroll-unprivileged-agent-for-mac-and-linux.yaml +++ /dev/null @@ -1,32 +0,0 @@ -# Kind can be one of: -# - breaking-change: a change to previously-documented behavior -# - deprecation: functionality that is being removed in a later release -# - bug-fix: fixes a problem in a previous version -# - enhancement: extends functionality but does not break or fix existing behavior -# - feature: new functionality -# - known-issue: problems that we are aware of in a given version -# - security: impacts on the security of a product or a user’s deployment. -# - upgrade: important information for someone upgrading from a prior version -# - other: does not fit into any of the other categories -kind: bug-fix - -# Change summary; a 80ish characters long description of the change. -summary: enable root user to re-enroll unprivileged agent for mac and linux - -# Long description; in case the summary is not enough to describe the change -# this field accommodate a description without length limits. -# NOTE: This field will be rendered only for breaking-change and known-issue kinds at the moment. -#description: - -# Affected component; usually one of "elastic-agent", "fleet-server", "filebeat", "metricbeat", "auditbeat", "all", etc. -component: "elastic-agent" - -# PR URL; optional; the PR number that added the changeset. -# If not present is automatically filled by the tooling finding the PR where this changelog fragment has been added. -# NOTE: the tooling supports backports, so it's able to fill the original PR number instead of the backport PR number. -# Please provide it if you are adding a fragment for a different PR. -pr: https://github.com/elastic/elastic-agent/pull/9603 - -# Issue URL; optional; the GitHub issue related to this changeset (either closes or is part of). -# If not present is automatically filled by the tooling with the issue linked to the PR number. -issue: https://github.com/elastic/elastic-agent/issues/8544 diff --git a/changelog/fragments/1756325090-Fix-missing-liveness-healthcheck-during-container-enrollment.yaml b/changelog/fragments/1756325090-Fix-missing-liveness-healthcheck-during-container-enrollment.yaml deleted file mode 100644 index 60ffd90a769..00000000000 --- a/changelog/fragments/1756325090-Fix-missing-liveness-healthcheck-during-container-enrollment.yaml +++ /dev/null @@ -1,32 +0,0 @@ -# Kind can be one of: -# - breaking-change: a change to previously-documented behavior -# - deprecation: functionality that is being removed in a later release -# - bug-fix: fixes a problem in a previous version -# - enhancement: extends functionality but does not break or fix existing behavior -# - feature: new functionality -# - known-issue: problems that we are aware of in a given version -# - security: impacts on the security of a product or a user’s deployment. -# - upgrade: important information for someone upgrading from a prior version -# - other: does not fit into any of the other categories -kind: bug-fix - -# Change summary; a 80ish characters long description of the change. -summary: Fix missing liveness healthcheck during container enrollment - -# Long description; in case the summary is not enough to describe the change -# this field accommodate a description without length limits. -# NOTE: This field will be rendered only for breaking-change and known-issue kinds at the moment. -#description: - -# Affected component; usually one of "elastic-agent", "fleet-server", "filebeat", "metricbeat", "auditbeat", "all", etc. -component: elastic-agent - -# PR URL; optional; the PR number that added the changeset. -# If not present is automatically filled by the tooling finding the PR where this changelog fragment has been added. -# NOTE: the tooling supports backports, so it's able to fill the original PR number instead of the backport PR number. -# Please provide it if you are adding a fragment for a different PR. -pr: https://github.com/elastic/elastic-agent/pull/9612 - -# Issue URL; optional; the GitHub issue related to this changeset (either closes or is part of). -# If not present is automatically filled by the tooling with the issue linked to the PR number. -issue: https://github.com/elastic/elastic-agent/issues/9611 diff --git a/changelog/fragments/1756433743-enable-root-user-to-re-enroll-unprivileged-agent-for-windows.yaml b/changelog/fragments/1756433743-enable-root-user-to-re-enroll-unprivileged-agent-for-windows.yaml deleted file mode 100644 index db3371eb303..00000000000 --- a/changelog/fragments/1756433743-enable-root-user-to-re-enroll-unprivileged-agent-for-windows.yaml +++ /dev/null @@ -1,32 +0,0 @@ -# Kind can be one of: -# - breaking-change: a change to previously-documented behavior -# - deprecation: functionality that is being removed in a later release -# - bug-fix: fixes a problem in a previous version -# - enhancement: extends functionality but does not break or fix existing behavior -# - feature: new functionality -# - known-issue: problems that we are aware of in a given version -# - security: impacts on the security of a product or a user’s deployment. -# - upgrade: important information for someone upgrading from a prior version -# - other: does not fit into any of the other categories -kind: bug-fix - -# Change summary; a 80ish characters long description of the change. -summary: enable admin user to re-enroll unprivileged agent for windows - -# Long description; in case the summary is not enough to describe the change -# this field accommodate a description without length limits. -# NOTE: This field will be rendered only for breaking-change and known-issue kinds at the moment. -#description: - -# Affected component; usually one of "elastic-agent", "fleet-server", "filebeat", "metricbeat", "auditbeat", "all", etc. -component: "elastic-agent" - -# PR URL; optional; the PR number that added the changeset. -# If not present is automatically filled by the tooling finding the PR where this changelog fragment has been added. -# NOTE: the tooling supports backports, so it's able to fill the original PR number instead of the backport PR number. -# Please provide it if you are adding a fragment for a different PR. -pr: https://github.com/elastic/elastic-agent/pull/9623 - -# Issue URL; optional; the GitHub issue related to this changeset (either closes or is part of). -# If not present is automatically filled by the tooling with the issue linked to the PR number. -issue: https://github.com/elastic/elastic-agent/issues/8544 diff --git a/changelog/fragments/1756833043-enhance-upgrade-action-loggers.yaml b/changelog/fragments/1756833043-enhance-upgrade-action-loggers.yaml deleted file mode 100644 index 8c7ec78745a..00000000000 --- a/changelog/fragments/1756833043-enhance-upgrade-action-loggers.yaml +++ /dev/null @@ -1,32 +0,0 @@ -# Kind can be one of: -# - breaking-change: a change to previously-documented behavior -# - deprecation: functionality that is being removed in a later release -# - bug-fix: fixes a problem in a previous version -# - enhancement: extends functionality but does not break or fix existing behavior -# - feature: new functionality -# - known-issue: problems that we are aware of in a given version -# - security: impacts on the security of a product or a user’s deployment. -# - upgrade: important information for someone upgrading from a prior version -# - other: does not fit into any of the other categories -kind: enhancement - -# Change summary; a 80ish characters long description of the change. -summary: Enhanced loggers for easier debugging of upgrade related issues. - -# Long description; in case the summary is not enough to describe the change -# this field accommodate a description without length limits. -# NOTE: This field will be rendered only for breaking-change and known-issue kinds at the moment. -#description: - -# Affected component; usually one of "elastic-agent", "fleet-server", "filebeat", "metricbeat", "auditbeat", "all", etc. -component: elastic-agent - -# PR URL; optional; the PR number that added the changeset. -# If not present is automatically filled by the tooling finding the PR where this changelog fragment has been added. -# NOTE: the tooling supports backports, so it's able to fill the original PR number instead of the backport PR number. -# Please provide it if you are adding a fragment for a different PR. -#pr: https://github.com/owner/repo/1234 - -# Issue URL; optional; the GitHub issue related to this changeset (either closes or is part of). -# If not present is automatically filled by the tooling with the issue linked to the PR number. -issue: https://github.com/elastic/elastic-agent/issues/9536 diff --git a/changelog/fragments/1756921212-endpoint-284-non-fatal.yaml b/changelog/fragments/1756921212-endpoint-284-non-fatal.yaml deleted file mode 100644 index 2247bda6793..00000000000 --- a/changelog/fragments/1756921212-endpoint-284-non-fatal.yaml +++ /dev/null @@ -1,32 +0,0 @@ -# Kind can be one of: -# - breaking-change: a change to previously-documented behavior -# - deprecation: functionality that is being removed in a later release -# - bug-fix: fixes a problem in a previous version -# - enhancement: extends functionality but does not break or fix existing behavior -# - feature: new functionality -# - known-issue: problems that we are aware of in a given version -# - security: impacts on the security of a product or a user’s deployment. -# - upgrade: important information for someone upgrading from a prior version -# - other: does not fit into any of the other categories -kind: bug-fix - -# Change summary; a 80ish characters long description of the change. -summary: Treat exit code 284 from Endpoint binary as non-fatal - -# Long description; in case the summary is not enough to describe the change -# this field accommodate a description without length limits. -# NOTE: This field will be rendered only for breaking-change and known-issue kinds at the moment. -#description: - -# Affected component; usually one of "elastic-agent", "fleet-server", "filebeat", "metricbeat", "auditbeat", "all", etc. -component: elastic-agent - -# PR URL; optional; the PR number that added the changeset. -# If not present is automatically filled by the tooling finding the PR where this changelog fragment has been added. -# NOTE: the tooling supports backports, so it's able to fill the original PR number instead of the backport PR number. -# Please provide it if you are adding a fragment for a different PR. -pr: https://github.com/elastic/elastic-agent/pull/9687 - -# Issue URL; optional; the GitHub issue related to this changeset (either closes or is part of). -# If not present is automatically filled by the tooling with the issue linked to the PR number. -#issue: https://github.com/owner/repo/1234 diff --git a/changelog/fragments/1757079091-fix-stale-upgrade-actions.yaml b/changelog/fragments/1757079091-fix-stale-upgrade-actions.yaml deleted file mode 100644 index bd81715db16..00000000000 --- a/changelog/fragments/1757079091-fix-stale-upgrade-actions.yaml +++ /dev/null @@ -1,5 +0,0 @@ -kind: bug-fix -summary: ensure failed upgrade actions are removed from queue and details are set -component: elastic-agent -pr: https://github.com/elastic/elastic-agent/pull/9634 -issue: https://github.com/elastic/elastic-agent/issues/9629