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

RHDEVDOCS-5627: Adds missing 4.15 release note for builds #73708

Merged
merged 1 commit into from
May 2, 2024

Conversation

opayne1
Copy link
Contributor

@opayne1 opayne1 commented Mar 25, 2024

Adds missing 4.15 release note for builds

Version(s):
4.15

Issue:
https://issues.redhat.com/browse/RHDEVDOCS-5627

Link to docs preview:
https://73708--ocpdocs-pr.netlify.app/openshift-enterprise/latest/release_notes/ocp-4-15-release-notes#ocp-4-15-administrator-perspective

QE review:

  • QE has approved this change.

Additional information:
This will need change management
@invincibleJai @jerolimov @Preeticp @joaedwar

@opayne1 opayne1 added this to the Continuous Release milestone Mar 25, 2024
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Mar 25, 2024
@openshift-ci-robot
Copy link

openshift-ci-robot commented Mar 25, 2024

@opayne1: This pull request references RHDEVDOCS-5627 which is a valid jira issue.

In response to this:

Adds missing 4.15 release note for builds

Version(s):
4.15

Issue:
https://issues.redhat.com/browse/RHDEVDOCS-5627

Link to docs preview:

QE review:

  • QE has approved this change.

Additional information:
This will need change management
@invincibleJai @jerolimov @Preeticp @joaedwar

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/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label Mar 25, 2024
@ocpdocs-previewbot
Copy link

ocpdocs-previewbot commented Mar 25, 2024

🤖 Tue Apr 30 18:29:06 - Prow CI generated the docs preview:

https://73708--ocpdocs-pr.netlify.app/openshift-enterprise/latest/release_notes/ocp-4-15-release-notes.html

@openshift-ci-robot
Copy link

openshift-ci-robot commented Mar 25, 2024

@opayne1: This pull request references RHDEVDOCS-5627 which is a valid jira issue.

In response to this:

Adds missing 4.15 release note for builds

Version(s):
4.15

Issue:
https://issues.redhat.com/browse/RHDEVDOCS-5627

Link to docs preview:
https://73708--ocpdocs-pr.netlify.app/openshift-enterprise/latest/release_notes/ocp-4-15-release-notes#ocp-4-15-administrator-perspective

QE review:

  • QE has approved this change.

Additional information:
This will need change management
@invincibleJai @jerolimov @Preeticp @joaedwar

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.

@@ -184,6 +184,7 @@ This release introduces the following updates to the *Administrator* perspective

* Enable and disable the tailing to Pod log viewer to minimize load time.
* View recommended values for `VerticalPodAutoscaler` on the *Deployment* page.
* Opt-out of `BuildConfig` and `DeploymentConfigs` when a cluster does not have v1 builds.
Copy link
Contributor

Choose a reason for hiding this comment

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

I don't think I fully understand this.

Are we asking users to disable BuildConfig and DeploymentConfigs if the cluster lacks support for builds for Red Hat OpenShift 1.0?

Is "v1 builds" how we officially refer to it? Sorry, can't seem to find an example in the docs. I probably missed something.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Honestly I am not really sure I understand this completely either @joaedwar can you help weigh in on this?

Copy link
Contributor

Choose a reason for hiding this comment

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

Yeah @opayne1 I think I will ask/follow up with eng about this when they are back online. Would you have a screenshot of this handy?

Copy link
Contributor

Choose a reason for hiding this comment

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

Also, I think from the we should probably us enable or disable rather than opt-out , but I'll check if that is the case in the IBM style guide.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@joaedwar I just added a few updates to this. I am still not 100% on it. I do not have a screenshot on it at the moment.

Copy link
Contributor

Choose a reason for hiding this comment

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

Thanks @opayne1. That seems clear . I am just checking with QE to see what they say. Thank you for working on this :)

@@ -184,6 +184,7 @@ This release introduces the following updates to the *Administrator* perspective

* Enable and disable the tailing to Pod log viewer to minimize load time.
* View recommended values for `VerticalPodAutoscaler` on the *Deployment* page.
* Disable `BuildConfig` and `DeploymentConfigs` when a cluster does not have a `build.openshift.io/v1` API version.
Copy link
Contributor

Choose a reason for hiding this comment

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

DeploymentConfig is a separate API, controlled by a separate cluster capability (DeploymentConfig). If DeploymentConfig web console components are removed simply because the build.openshift.io API group is not present, this is a bug.

Copy link
Contributor

Choose a reason for hiding this comment

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

Thank you for reviewing @adambkaplan. So should this be added as a known issue, instead? I am not sure why we should disable these components.

Choose a reason for hiding this comment

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

@adambkaplan Just to elaborate the issue, we observed that when there is no build.openshift.io/v1` API version in the cluster, the DeployConfig does not work properly. We did a small spike to see that although the ReplicationController for the DC is getting created, still DC is not starting the pods. This hinted some underlining connection b/w the BC and DC.
But surely it may also be a bug. It would be great if we can ask someone from the respective team.

Copy link
Contributor

Choose a reason for hiding this comment

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

But surely it may also be a bug. It would be great if we can ask someone from the respective team.

This is absolutely a bug. Potentially related to (or fixed by) OCPBUGS-22956

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Looks like someone wrote up text for that bug, but it didn't make it into the release notes. I have reached out to the writer working in this area for more information.

I will most likely update this PR with a note for OCPBUGS-22956 in the bug fixes section of the release notes based on what I find out.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Updated to include the bug fix.

@adambkaplan
Copy link
Contributor

/assign @Lucifergene

Avik is the owner of the respective epic, ODC-7352

@opayne1
Copy link
Contributor Author

opayne1 commented Apr 5, 2024

@joaedwar @Preeticp could you ack this PR? I am going to put it through the change management process and try and get this merged as soon as possible.

@mwerner2113
Copy link

LGTM

1 similar comment
@cbippley
Copy link
Contributor

cbippley commented Apr 8, 2024

LGTM

@opayne1
Copy link
Contributor Author

opayne1 commented Apr 9, 2024

Hi @sferich888 and @xltian! This PR adds a bug to the release notes that was missed when batching in bugs to the 4.15 release. Could you provide an ack for change management? Thanks!

Copy link
Contributor

@buildbricks buildbricks left a comment

Choose a reason for hiding this comment

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

lgtm

@sferich888
Copy link
Contributor

/lgtm

With that said we don't use ConfigObserver anywhere in our docs; but in this location (or update) so it may not be something customer understand or can parse if they read this update. In short it may be better to explain that the ConfigObserver is the CVO.

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Apr 15, 2024
@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Apr 26, 2024
Copy link

openshift-ci bot commented Apr 26, 2024

New changes are detected. LGTM label has been removed.

@psrna
Copy link

psrna commented Apr 29, 2024

lgtm

@opayne1 opayne1 added the peer-review-needed Signifies that the peer review team needs to review this PR label Apr 29, 2024
@dfitzmau
Copy link
Contributor

/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 29, 2024
@dfitzmau
Copy link
Contributor

Hi @opayne1 . WOuld you be OK to tick the QE Approved box? I think QE approved the PR?

Also, is a CM needed for this? The OCP Docs Manual is not very clear. The Peer-review checklist states:

Screenshot from 2024-04-29 15-29-34

@openshift-ci-robot
Copy link

openshift-ci-robot commented Apr 29, 2024

@opayne1: This pull request references RHDEVDOCS-5627 which is a valid jira issue.

In response to this:

Adds missing 4.15 release note for builds

Version(s):
4.15

Issue:
https://issues.redhat.com/browse/RHDEVDOCS-5627

Link to docs preview:
https://73708--ocpdocs-pr.netlify.app/openshift-enterprise/latest/release_notes/ocp-4-15-release-notes#ocp-4-15-administrator-perspective

QE review:

  • QE has approved this change.

Additional information:
This will need change management
@invincibleJai @jerolimov @Preeticp @joaedwar

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.

@dfitzmau
Copy link
Contributor

/remove-label peer-review-in-progress

/label peer-review-done

@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 29, 2024
Copy link

openshift-ci bot commented Apr 30, 2024

@opayne1: 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/test-infra repository. I understand the commands that are listed here.

@opayne1 opayne1 merged commit a2e8b6f into openshift:enterprise-4.15 May 2, 2024
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
branch/enterprise-4.15 jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. peer-review-done Signifies that the peer review team has reviewed this PR size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet