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.

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

release-23.1: server: server identity returns nodeID for system tenant #103798

Merged
merged 1 commit into from
Jun 2, 2023

Conversation

blathers-crl[bot]
Copy link

@blathers-crl blathers-crl bot commented May 23, 2023

Backport 1/1 commits from #103148 on behalf of @dhartunian.

/cc @cockroachdb/release


Previously, the server identity object would hide the nodeID from identity objects that contained a set tenantID. This was done to create separation of concerns between a secondary tenant and the rest of the cluster. However, this identity is used in populating log payloads with contextual metadata. That led to #103112 due to the fact that the system tenant sets its tenantId to 1 which led to a hidden nodeID.

We now always emit the nodeID when the tenantID is set to the system tenant.

Fixes #103112

Release note (bug fix): 23.1.0 contained a bug where the node_id field would be omitted in logs. This fix restores that value.


Release justification: important bugfix for logs

Previously, the server identity object would hide the nodeID from
identity objects that contained a set tenantID. This was done to
create separation of concerns between a secondary tenant and the
rest of the cluster. However, this identity is used in populating log
payloads with contextual metadata. That led to #103112 due to the fact
that the system tenant sets its tenantId to 1 which led to a hidden
nodeID.

We now always emit the nodeID when the tenantID is set to the system
tenant.

Fixes #103112

Release note (bug fix): 23.1.0 contained a bug where the `node_id`
field would be omitted in logs. This fix restores that value.
@blathers-crl blathers-crl bot requested a review from a team as a code owner May 23, 2023 17:21
@blathers-crl blathers-crl bot force-pushed the blathers/backport-release-23.1-103148 branch from 810d4f2 to 0e733a7 Compare May 23, 2023 17:21
@blathers-crl blathers-crl bot added blathers-backport This is a backport that Blathers created automatically. O-robot Originated from a bot. labels May 23, 2023
@blathers-crl blathers-crl bot force-pushed the blathers/backport-release-23.1-103148 branch from 8f1b10c to 3053977 Compare May 23, 2023 17:21
@blathers-crl
Copy link
Author

blathers-crl bot commented May 23, 2023

Thanks for opening a backport.

Please check the backport criteria before merging:

  • Patches should only be created for serious issues or test-only changes.
  • Patches should not break backwards-compatibility.
  • Patches should change as little code as possible.
  • Patches should not change on-disk formats or node communication protocols.
  • Patches should not add new functionality.
  • Patches must not add, edit, or otherwise modify cluster versions; or add version gates.
If some of the basic criteria cannot be satisfied, ensure that the exceptional criteria are satisfied within.
  • There is a high priority need for the functionality that cannot wait until the next release and is difficult to address in another way.
  • The new functionality is additive-only and only runs for clusters which have specifically “opted in” to it (e.g. by a cluster setting).
  • New code is protected by a conditional check that is trivial to verify and ensures that it only runs for opt-in clusters.
  • The PM and TL on the team that owns the changed code have signed off that the change obeys the above rules.

Add a brief release justification to the body of your PR to justify this backport.

Some other things to consider:

  • What did we do to ensure that a user that doesn’t know & care about this backport, has no idea that it happened?
  • Will this work in a cluster of mixed patch versions? Did we test that?
  • If a user upgrades a patch version, uses this feature, and then downgrades, what happens?

@cockroach-teamcity
Copy link
Member

This change is Reviewable

@dhartunian dhartunian merged commit 305392c into release-23.1 Jun 2, 2023
2 checks passed
@dhartunian dhartunian deleted the blathers/backport-release-23.1-103148 branch June 2, 2023 19:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
blathers-backport This is a backport that Blathers created automatically. O-robot Originated from a bot.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants