Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Backport of docs: update docs related to GH-16779 into release/1.15.x #17021

Merged
merged 3 commits into from
Apr 17, 2023
Merged

Backport of docs: update docs related to GH-16779 into release/1.15.x #17021

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
c6728cf
backport of commit c030771c774929e99c59d8ebc4bde2c7ed0f5fa9
jkirschner-hashicorp Apr 17, 2023
1709c68
backport of commit a12af289cb096f0ad7309a1f7cf76328eae3352b
jkirschner-hashicorp Apr 17, 2023
85a5581
backport of commit a4e963b133ae4e2575bd2278ae7ad203c46a4a1a
jkirschner-hashicorp Apr 17, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -58,7 +58,7 @@ BUG FIXES:

KNOWN ISSUES:

* connect: An issue with leaf certificate rotation can cause some service instances to lose their ability to communicate in the mesh after 72 hours (LeafCertTTL). This issue is not consistently reproducible. We are working to address this issue in an upcoming patch release. To err on the side of caution, service mesh deployments should not upgrade to Consul v1.15 at this time. Refer to [[GH-16779](https://github.com/hashicorp/consul/issues/16779)] for the latest information.
* connect: A race condition can cause some service instances to lose their ability to communicate in the mesh after 72 hours (LeafCertTTL) due to a problem with leaf certificate rotation. This bug is fixed in Consul v1.15.2 by [GH-16818](https://github.com/hashicorp/consul/issues/16818).

BREAKING CHANGES:

Expand Down
16 changes: 7 additions & 9 deletions website/content/docs/release-notes/consul/v1_15_x.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -68,30 +68,28 @@ For more detailed information, please refer to the [upgrade details page](/consu

The following issues are known to exist in the v1.15.x releases:

- All current 1.15.x versions are under investigation for a not-consistently-reproducible
issue that can cause some service instances to lose their ability to communicate in the mesh after
- v1.15.0 - v1.15.1 contain a race condition that can cause
some service instances to lose their ability to communicate in the mesh after
[72 hours (LeafCertTTL)](/consul/docs/connect/ca/consul#leafcertttl)
due to a problem with leaf certificate rotation.
We will update this section with more information as our investigation continues,
including the target availability for a fix.
Refer to [GH-16779](https://github.com/hashicorp/consul/issues/16779)
for the latest information.
This is resolved in Consul v1.15.2.

- For v1.15.0, Consul is reporting newer releases of Envoy (for example, v1.25.1) as not supported, even though these versions are listed as valid in the [Envoy compatilibity matrix](/consul/docs/connect/proxies/envoy#envoy-and-consul-client-agent). The following error would result for newer versions of Envoy:

```log hideClipboard
Envoy version 1.25.1 is not supported. If there is a reason you need to use this version of envoy use the ignore-envoy-compatibility flag. Using an unsupported version of Envoy is not recommended and your experience may vary.
```

The workaround to resolve this issue until Consul v1.15.1 would be to run the client agents with the new `ingore-envoy-compatiblity` flag:
To workaround this issue on Consul v1.15.0, launch sidecar proxies
with the `ignore-envoy-compatiblity` flag:

```shell-session
$ consul connect envoy --ignore-envoy-compatibility
```

- For v1.15.0, there is a known issue where `consul acl token read -self` requires an `-accessor-id`. This is resolved in the uppcoming Consul v1.15.1 patch release.
- For v1.15.0, there is a known issue where `consul acl token read -self` requires an `-accessor-id`. This is resolved in Consul v1.15.1.

- For v1.15.0, there is a known issue where search filters produced errors and resulted in lists not showing full results until being interacted with. This is resolved in the upcoming Consul v1.15.1 patch release.
- For v1.15.0, there is a known issue where search filters produced errors and resulted in lists not showing full results until being interacted with. This is resolved in Consul v1.15.1.

## Changelogs

Expand Down
13 changes: 4 additions & 9 deletions website/content/docs/upgrading/upgrade-specific.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -16,21 +16,16 @@ upgrade flow.

## Consul 1.15.x

#### Service mesh known issue
#### Service mesh compatibility ((#service-mesh-compatibility-1-15))

To err on the side of caution,
service mesh deployments should not upgrade to Consul v1.15 at this time.
Upgrade to **Consul version 1.15.2 or later**.

We are currently investigating a not-consistently-reproducible issue that can cause
Consul versions 1.15.0 - 1.15.1 contain a race condition that can cause
some service instances to lose their ability to communicate in the mesh after
[72 hours (LeafCertTTL)](/consul/docs/connect/ca/consul#leafcertttl)
due to a problem with leaf certificate rotation.
We will update this section with more information as our investigation continues,
including the target availability for a fix.

If you are already operating Consul v1.15, refer to discussion of this issue on
[GH-16779](https://github.com/hashicorp/consul/issues/16779)
for potential workarounds and to share your observations.
This bug is fixed in Consul versions 1.15.2 and newer.

#### Removing configuration options

Expand Down