diff --git a/changelog/8.5.1.yaml b/changelog/8.5.1.yaml new file mode 100644 index 00000000000..9a5e2f352a3 --- /dev/null +++ b/changelog/8.5.1.yaml @@ -0,0 +1,38 @@ +version: 8.5.1 +entries: + - kind: bug-fix + summary: Fix how multiple Fleet Server hosts are handled + description: It fixes the bug when the Elastic Agent would be enrolled using a valid Fleet Server URL, but the policy would contain more than one, being the first URL unreachable. In that case the Elastic Agent would enroll with Fleet Server, but become unhealthy as it'd get stuck trying only the first, unreachable Fleet Server host. + component: "" + pr: + - https://github.com/elastic/elastic-agent/pull/1329 + issue: + - https://github.com/elastic/elastic-agent/issues/1328 + timestamp: 1666281194 + file: + name: 1666281194-Fix-how-multiple-Fleet-Server-hosts-are-handled.yaml + checksum: 6fb9e56c4b750ec352431cef72a4c45251f54c7f + - kind: bug-fix + summary: 'Fix: Windows Agent Left Unhealthy After Removing Endpoint Integration' + description: "" + component: "" + pr: + - https://github.com/elastic/elastic-agent/pull/1286 + issue: + - https://github.com/elastic/elastic-agent/issues/1262 + timestamp: 1666611696 + file: + name: 1666611696-fix_service_stop_timeout.yaml + checksum: 212c7142d5ac4f6f061f7da0149d7600e97df2d5 + - kind: feature + summary: Improve shutdown logs + description: "" + component: cmd, handler, upgrade + pr: + - https://github.com/elastic/elastic-agent/pull/1618 + issue: + - https://github.com/elastic/elastic-agent/issues/1358 + timestamp: 1666789812 + file: + name: 1666789812-Improve-shutdown-logs.yaml + checksum: 0292242b3855f5e8e7701f9149404a71b04729f9 diff --git a/changelog/8.5.2.yaml b/changelog/8.5.2.yaml new file mode 100644 index 00000000000..132c4607cbc --- /dev/null +++ b/changelog/8.5.2.yaml @@ -0,0 +1,2 @@ +version: 8.5.2 +# No changes in this release. diff --git a/changelog/fragments/1665784342-use-stack-version-npm-synthetics.yaml b/changelog/fragments/1665784342-use-stack-version-npm-synthetics.yaml deleted file mode 100644 index a928c800d1e..00000000000 --- a/changelog/fragments/1665784342-use-stack-version-npm-synthetics.yaml +++ /dev/null @@ -1,31 +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: feature - -# Change summary; a 80ish characters long description of the change. -summary: use-stack-version-npm-synthetics - -# Long description; in case the summary is not enough to describe the change -# this field accommodate a description without length limits. -description: Always npm i the stack_release version of @elastic/synthetics - -# Affected component; a word indicating the component this changeset affects. -component: synthetics-integration - -# PR number; 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: 1528 - -# Issue number; 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: 1234 diff --git a/changelog/fragments/1666281194-Fix-how-multiple-Fleet-Server-hosts-are-handled.yaml b/changelog/fragments/1666281194-Fix-how-multiple-Fleet-Server-hosts-are-handled.yaml deleted file mode 100644 index c0f13aa3d9c..00000000000 --- a/changelog/fragments/1666281194-Fix-how-multiple-Fleet-Server-hosts-are-handled.yaml +++ /dev/null @@ -1,35 +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 how multiple Fleet Server hosts are handled - -# Long description; in case the summary is not enough to describe the change -# this field accommodate a description without length limits. -description: It fixes the bug when the Elastic Agent would be enrolled using - a valid Fleet Server URL, but the policy would contain more than one, being - the first URL unreachable. In that case the Elastic Agent would enroll with - Fleet Server, but become unhealthy as it'd get stuck trying only the first, - unreachable Fleet Server host. - -# Affected component; a word indicating the component this changeset affects. -#component: - -# PR number; 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: 1329 - -# Issue number; 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: 1234 diff --git a/changelog/fragments/1666611696-fix_service_stop_timeout.yaml b/changelog/fragments/1666611696-fix_service_stop_timeout.yaml deleted file mode 100644 index 5125282618f..00000000000 --- a/changelog/fragments/1666611696-fix_service_stop_timeout.yaml +++ /dev/null @@ -1,4 +0,0 @@ -kind: bug-fix -summary: "Fix: Windows Agent Left Unhealthy After Removing Endpoint Integration" -pr: 1286 -issue: 1262 diff --git a/changelog/fragments/1666789812-Improve-shutdown-logs.yaml b/changelog/fragments/1666789812-Improve-shutdown-logs.yaml deleted file mode 100644 index 091e2570ae6..00000000000 --- a/changelog/fragments/1666789812-Improve-shutdown-logs.yaml +++ /dev/null @@ -1,31 +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: feature - -# Change summary; a 80ish characters long description of the change. -summary: Improve shutdown logs - -# Long description; in case the summary is not enough to describe the change -# this field accommodate a description without length limits. -#description: - -# Affected component; a word indicating the component this changeset affects. -component: cmd, handler, upgrade - -# PR number; 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: 1618 - -# Issue number; 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: 1358