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

[INTERNAL FIX] ibm-name-clean-up #67323

Merged
merged 1 commit into from
Nov 14, 2023
Merged

Conversation

dfitzmau
Copy link
Contributor

@dfitzmau dfitzmau commented Nov 2, 2023

Version(s):
main, 4.14, and 4.15

Issue:
INTERNAL FIXES + specific update as per https://issues.redhat.com/browse/OCPBUGS-19804

Link to docs preview:

Building applications

Authentication and authorization

Backup and restore

Distributed tracing

Installing (IBM Cloud)

Installing (IBM Power)

Installing (IBM Power VS)

Installing (IBM Z and LinuxOne)

Installing (single-node)

Machine management

Networking

Post install

Registry

Scalability and performance

Security and compliance

Service mesh

Storage

Virt

Welcome page

Additional information:

IBM naming conventions

@openshift-ci openshift-ci bot added the size/S Denotes a PR that changes 10-29 lines, ignoring generated files. label Nov 2, 2023
@ocpdocs-previewbot
Copy link

ocpdocs-previewbot commented Nov 2, 2023

🤖 Updated build preview is available at:
https://67323--docspreview.netlify.app

Build log: https://circleci.com/gh/ocpdocs-previewbot/openshift-docs/33177

@dfitzmau dfitzmau force-pushed the ibm-name-clean-up branch 2 times, most recently from c800c8e to 090bd78 Compare November 2, 2023 16:51
@openshift-ci openshift-ci bot added size/L Denotes a PR that changes 100-499 lines, ignoring generated files. and removed size/S Denotes a PR that changes 10-29 lines, ignoring generated files. labels Nov 2, 2023
@dfitzmau dfitzmau force-pushed the ibm-name-clean-up branch 9 times, most recently from 1cc548f to acc0b7f Compare November 3, 2023 10:11
@openshift-ci openshift-ci bot added size/XL Denotes a PR that changes 500-999 lines, ignoring generated files. and removed size/L Denotes a PR that changes 100-499 lines, ignoring generated files. labels Nov 3, 2023
@dfitzmau dfitzmau force-pushed the ibm-name-clean-up branch 7 times, most recently from def660a to c23a93b Compare November 3, 2023 15:06
@SNiemann15
Copy link
Contributor

@dfitzmau From an IBM Z perspective looks good. Fingers crossed that the Portal resolves everything correctly.

_attributes/common-attributes.adoc Outdated Show resolved Hide resolved
@dfitzmau dfitzmau force-pushed the ibm-name-clean-up branch 2 times, most recently from 7229920 to 160962b Compare November 7, 2023 17:06
@@ -331,7 +331,7 @@ Available Commands:
azure Manage credentials objects for Azure
gcp Manage credentials objects for Google cloud
help Help about any command
ibmcloud Manage credentials objects for IBM Cloud
ibmcloud Manage credentials objects for {ibm-cloud-name}
Copy link
Contributor

Choose a reason for hiding this comment

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

This looks like CLI output that you have put a variable in, and it's not displaying IBM Cloud (I guess because you can't have variables in an example output?). But probably the CLI just has "IBM Cloud" and I think the example should just reflect what is displayed to the user.
Screenshot 2023-11-13 at 3 31 51 PM

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Reverted. Good catch!

@@ -81,17 +81,17 @@ You can also deploy a cluster on AWS infrastructure that you provisioned yoursel
ifndef::openshift-origin[]
- **xref:../installing/installing_ibm_cloud_public/preparing-to-install-on-ibm-cloud.adoc#preparing-to-install-on-ibm-cloud[Install a cluster on IBM Cloud VPC]**: You can install {product-title} on IBM Cloud VPC on installer-provisioned infrastructure.
Copy link
Contributor

Choose a reason for hiding this comment

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

I might not understand all the nuances but should this be "IBM Cloud(R)" by using the new variable {ibm-cloud-name} and not "IBM Cloud VPC"?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Excellent catch. I missed this. Updated.

@kcarmichael08
Copy link
Contributor

Does IBM need the (R) here?

Screenshot 2023-11-13 at 4 37 00 PM

@kcarmichael08
Copy link
Contributor

Nice job! I think I managed to look at all the files and skim/search to see if the replacements were correct. Had a few questions/comments, tried to mark inline and/or provide screen caps.

@kcarmichael08
Copy link
Contributor

And, sorry, some of my comments are showing up multiple times - I guess because of the way that I commented on files. :( Please disregard multiple comments for the same thing....

@kcarmichael08 kcarmichael08 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 Nov 13, 2023
@dfitzmau
Copy link
Contributor Author

I think this one got missed? I don't see this file in the PR as being changed either.

https://67323--docspreview.netlify.app/openshift-enterprise/latest/storage/understanding-persistent-storage#types-of-persistent-volumes_understanding-persistent-storage

Yeah, it gets confusing here as "IBM VPC Block" is OK to keep but any references to "IBM Cloud VPC" need to change to "IBM Cloud". I updated any "IBM" references in this file to "{IBM-name}.

@dfitzmau dfitzmau force-pushed the ibm-name-clean-up branch 2 times, most recently from 418b9c8 to 5666ccf Compare November 14, 2023 09:50
@dfitzmau
Copy link
Contributor Author

Thanks, @kcarmichael08 , for the excellent review.

@dfitzmau
Copy link
Contributor Author

/label merge-review-needed

@openshift-ci openshift-ci bot added the merge-review-needed Signifies that the merge review team needs to review this PR label Nov 14, 2023
@sheriff-rh sheriff-rh added merge-review-in-progress Signifies that the merge review team is reviewing this PR and removed merge-review-needed Signifies that the merge review team needs to review this PR labels Nov 14, 2023
Copy link
Contributor

@sheriff-rh sheriff-rh left a comment

Choose a reason for hiding this comment

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

One question for now!

modules/installation-bare-metal-config-yaml.adoc Outdated Show resolved Hide resolved
Copy link
Contributor

@sheriff-rh sheriff-rh left a comment

Choose a reason for hiding this comment

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

Once again, this is overall great work, Darragh! My suggestions primarily focus on plain-text IBM Power, IBM Z systems, IBM LinuxONE, etc as opportunities for improvement with attributes.

modules/op-release-notes-1-2.adoc Outdated Show resolved Hide resolved
modules/op-release-notes-1-2.adoc Outdated Show resolved Hide resolved
modules/op-release-notes-1-2.adoc Outdated Show resolved Hide resolved
modules/op-release-notes-1-4.adoc Outdated Show resolved Hide resolved
modules/op-release-notes-1-4.adoc Outdated Show resolved Hide resolved
modules/op-release-notes-1-6.adoc Outdated Show resolved Hide resolved
modules/op-release-notes-1-7.adoc Outdated Show resolved Hide resolved
modules/op-release-notes-1-8.adoc Outdated Show resolved Hide resolved
modules/ossm-rn-new-features.adoc Outdated Show resolved Hide resolved
modules/serverless-rn-1-28-0.adoc Outdated Show resolved Hide resolved
Copy link
Contributor

@sheriff-rh sheriff-rh left a comment

Choose a reason for hiding this comment

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

Changes LGTM! Merging.

@sheriff-rh sheriff-rh merged commit 30a7fc7 into openshift:main Nov 14, 2023
@sheriff-rh
Copy link
Contributor

/cherrypick enterprise-4.15

@sheriff-rh sheriff-rh added this to the Continuous Release milestone Nov 14, 2023
@sheriff-rh
Copy link
Contributor

/cherrypick enterprise-4.14

@openshift-cherrypick-robot

@sheriff-rh: #67323 failed to apply on top of branch "enterprise-4.15":

Applying: ibm-name-clean-up
Using index info to reconstruct a base tree...
M	_attributes/common-attributes.adoc
M	_topic_maps/_topic_map.yml
M	modules/installation-obtaining-installer.adoc
M	modules/nw-egress-ips-about.adoc
M	security/file_integrity_operator/file-integrity-operator-release-notes.adoc
M	storage/container_storage_interface/persistent-storage-csi-ibm-vpc-block.adoc
M	welcome/index.adoc
Falling back to patching base and 3-way merge...
Auto-merging welcome/index.adoc
CONFLICT (content): Merge conflict in welcome/index.adoc
Auto-merging storage/container_storage_interface/persistent-storage-csi-ibm-vpc-block.adoc
Auto-merging security/file_integrity_operator/file-integrity-operator-release-notes.adoc
Auto-merging modules/nw-egress-ips-about.adoc
Auto-merging modules/installation-obtaining-installer.adoc
Auto-merging _topic_maps/_topic_map.yml
Auto-merging _attributes/common-attributes.adoc
CONFLICT (content): Merge conflict in _attributes/common-attributes.adoc
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 ibm-name-clean-up
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

In response to this:

/cherrypick enterprise-4.15

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.

@openshift-cherrypick-robot

@sheriff-rh: #67323 failed to apply on top of branch "enterprise-4.14":

Applying: ibm-name-clean-up
Using index info to reconstruct a base tree...
M	_attributes/common-attributes.adoc
M	_topic_maps/_topic_map.yml
M	modules/installation-obtaining-installer.adoc
M	modules/nw-egress-ips-about.adoc
M	security/compliance_operator/compliance-operator-release-notes.adoc
M	security/file_integrity_operator/file-integrity-operator-release-notes.adoc
M	storage/container_storage_interface/persistent-storage-csi-ibm-vpc-block.adoc
M	welcome/index.adoc
Falling back to patching base and 3-way merge...
Auto-merging welcome/index.adoc
CONFLICT (content): Merge conflict in welcome/index.adoc
Auto-merging storage/container_storage_interface/persistent-storage-csi-ibm-vpc-block.adoc
Auto-merging security/file_integrity_operator/file-integrity-operator-release-notes.adoc
Auto-merging security/compliance_operator/compliance-operator-release-notes.adoc
Auto-merging modules/nw-egress-ips-about.adoc
Auto-merging modules/installation-obtaining-installer.adoc
Auto-merging _topic_maps/_topic_map.yml
Auto-merging _attributes/common-attributes.adoc
CONFLICT (content): Merge conflict in _attributes/common-attributes.adoc
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 ibm-name-clean-up
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

In response to this:

/cherrypick enterprise-4.14

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.

@sheriff-rh
Copy link
Contributor

Manual cherrypicks complete. Thanks @dfitzmau !

#67916
#67914

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
branch/enterprise-4.14 branch/enterprise-4.15 merge-review-in-progress Signifies that the merge review team is reviewing this PR peer-review-done Signifies that the peer review team has reviewed this PR size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

9 participants