Skip to content

OBSDOCS-1843: Logging Z-Stream Release Notes - 6.2.1 #92143

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

Merged
merged 1 commit into from
Apr 17, 2025

Conversation

theashiot
Copy link
Contributor

@theashiot theashiot commented Apr 14, 2025

Version(s): 4.18, 4.17, 4.16

Issue: https://issues.redhat.com/browse/OBSDOCS-1843

Link to docs preview: https://92143--ocpdocs-pr.netlify.app/openshift-enterprise/latest/observability/logging/logging-6.2/log6x-release-notes-6.2.html

QE review:

  • QE has approved this change.

Additional information:

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Apr 14, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Apr 14, 2025

@theashiot: This pull request references OBSDOCS-1843 which is a valid jira issue.

In response to this:

Version(s): 4.18, 4.17

Issue: https://issues.redhat.com/browse/OBSDOCS-1843

Link to docs preview:

QE review:

  • QE has approved this change.

Additional information:

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci openshift-ci bot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Apr 14, 2025
@ocpdocs-previewbot
Copy link

ocpdocs-previewbot commented Apr 14, 2025

@openshift-ci-robot
Copy link

openshift-ci-robot commented Apr 14, 2025

@theashiot: This pull request references OBSDOCS-1843 which is a valid jira issue.

In response to this:

Version(s): 4.18, 4.17

Issue: https://issues.redhat.com/browse/OBSDOCS-1843

Link to docs preview: https://92143--ocpdocs-pr.netlify.app/openshift-enterprise/latest/observability/logging/logging-6.2/log6x-release-notes-6.2.html

QE review:

  • QE has approved this change.

Additional information:

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@theashiot
Copy link
Contributor Author

/label peer-review-needed

@openshift-ci openshift-ci bot added the peer-review-needed Signifies that the peer review team needs to review this PR label Apr 15, 2025
[id="logging-release-notes-6-2-1-CVEs_{context}"]
== CVEs

* link:https://access.redhat.com/security/cve/CVE-2022-49043[CVE-2022-49043]

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There isn't any CVEs in 6.2.1 after I attached the new build. can you update this?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thanks, removed

[id="logging-release-notes-6-2-1_{context}"]
= Logging 6.2.1 Release Notes

This release includes link:https://access.redhat.com/errata/RHBA-2025:3908[{logging-uc} {for} Bug Fix Release 6.2.1].
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we use the advisory name for the link instead? I don't know what makes more sense, but for me just looking at the document and seeing the "advisory identifier" provides more information than repeating that this is about 6.2.1

We mixed this in the past a bit, but looking at the other PRs for this z-stream cycle I think we have settled on the identifier now.

Suggested change
This release includes link:https://access.redhat.com/errata/RHBA-2025:3908[{logging-uc} {for} Bug Fix Release 6.2.1].
This release includes link:https://access.redhat.com/errata/RHBA-2025:3908[RHBA-2025:3908].

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

done


* Before this update, Loki ingesters that got into an unhealthy state due to networking issues stayed in that state even after the network recovered. With this update, you can configure the {loki-op} to perform service discovery more often so that unhealthy ingesters can rejoin the group. (link:https://issues.redhat.com/browse/LOG-6992[LOG-6992])

* Before this update, the Vector collector could not forward Open Virtual Network (OVN) and Auditd logs. With this update, the Vector collector can forward OVN and Auditd logs. (link:https://issues.redhat.com/browse/LOG-6997[LOG-6997])
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

added

Copy link

openshift-ci bot commented Apr 15, 2025

@theashiot: all tests passed!

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@tmalove
Copy link
Contributor

tmalove commented Apr 15, 2025

/remove-label peer-review-needed
/label peer-review-in-progress

@openshift-ci openshift-ci bot added peer-review-in-progress Signifies that the peer review team is reviewing this PR and removed peer-review-needed Signifies that the peer review team needs to review this PR labels Apr 15, 2025
@tmalove
Copy link
Contributor

tmalove commented Apr 15, 2025

/remove-label peer-review-in-progress
/label peer-review-done
/lgtm

@openshift-ci openshift-ci bot added peer-review-done Signifies that the peer review team has reviewed this PR and removed peer-review-in-progress Signifies that the peer review team is reviewing this PR labels Apr 15, 2025
@anpingli
Copy link

LGTM

@openshift-ci-robot
Copy link

openshift-ci-robot commented Apr 16, 2025

@theashiot: This pull request references OBSDOCS-1843 which is a valid jira issue.

In response to this:

Version(s): 4.18, 4.17

Issue: https://issues.redhat.com/browse/OBSDOCS-1843

Link to docs preview: https://92143--ocpdocs-pr.netlify.app/openshift-enterprise/latest/observability/logging/logging-6.2/log6x-release-notes-6.2.html

QE review:

  • QE has approved this change.

Additional information:

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci-robot
Copy link

openshift-ci-robot commented Apr 16, 2025

@theashiot: This pull request references OBSDOCS-1843 which is a valid jira issue.

In response to this:

Version(s): 4.18, 4.17, 4.16

Issue: https://issues.redhat.com/browse/OBSDOCS-1843

Link to docs preview: https://92143--ocpdocs-pr.netlify.app/openshift-enterprise/latest/observability/logging/logging-6.2/log6x-release-notes-6.2.html

QE review:

  • QE has approved this change.

Additional information:

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@theashiot
Copy link
Contributor Author

Thanks, @tmalove for the review!

best,
ashwin

@theashiot
Copy link
Contributor Author

/label merge-review-needed

Please note: to be merged only after the release goes live.

@openshift-ci openshift-ci bot added the merge-review-needed Signifies that the merge review team needs to review this PR label Apr 16, 2025
@skopacz1 skopacz1 added the merge-review-in-progress Signifies that the merge review team is reviewing this PR label Apr 16, 2025
Copy link
Contributor

@skopacz1 skopacz1 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Merge review LGTM!

That said, I am not sure what indication I am supposed to look at to determine whether this release goes live (maybe once the errata link goes live?), so I will wait for you to respond on Slack.

Just in case it goes live while I am not online, and you want to merge it ASAP, I am adding an ok-to-merge label to it. That way, you could either wait for me to come back online or put it back in the queue to be merged as soon as someone looks at the PR.

@theashiot
Copy link
Contributor Author

Thanks, @skopacz1 for the review! The release is now live and this can be merged.

best,
ashwin

@skopacz1
Copy link
Contributor

Sounds good, will attempt auto cherry picks to the other versions to see if they work

@skopacz1 skopacz1 merged commit 8e9870e into openshift:enterprise-4.18 Apr 17, 2025
2 checks passed
@skopacz1
Copy link
Contributor

/cherrypick enterprise-4.16

@skopacz1
Copy link
Contributor

/cherrypick enterprise-4.17

@openshift-cherrypick-robot

@skopacz1: new pull request created: #92328

In response to this:

/cherrypick enterprise-4.16

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@openshift-cherrypick-robot

@skopacz1: new pull request created: #92329

In response to this:

/cherrypick enterprise-4.17

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@skopacz1 skopacz1 removed merge-review-in-progress Signifies that the merge review team is reviewing this PR merge-review-needed Signifies that the merge review team needs to review this PR labels Apr 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. ok-to-merge peer-review-done Signifies that the peer review team has reviewed this PR size/M Denotes a PR that changes 30-99 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8 participants