Skip to content

Conversation

@ShaunaDiaz
Copy link
Contributor

@ShaunaDiaz ShaunaDiaz commented Aug 13, 2025

Version(s):
4.17+

Issue:
OSDOCS-15831

Link to docs preview:
microshift_install_get_ready

QE review:

  • N/A internal docs work

Additional information:
This work includes removing L3 headings that are not supported in DITA migration.
Included workarounds for indeterminate issues are: 1) replacing certain xrefs with hard links in modules; 2) moving other xrefs to Additional resources; 3) removing words attached to links (that aren't the titles of the links). The linking strategy is in place here to have a passing build (and in a way that is easy for a doc user to digest).

@openshift-ci openshift-ci bot added the size/XL Denotes a PR that changes 500-999 lines, ignoring generated files. label Aug 13, 2025
@openshift-ci openshift-ci bot added size/L Denotes a PR that changes 100-499 lines, ignoring generated files. and removed size/XL Denotes a PR that changes 500-999 lines, ignoring generated files. labels Aug 13, 2025
@ShaunaDiaz ShaunaDiaz changed the title Osdocs 15831 OSDOCS-15831: modularize install get ready assembly MicroShift Aug 13, 2025
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Aug 13, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Aug 13, 2025

@ShaunaDiaz: This pull request references OSDOCS-15831 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.20.0" version, but no target version was set.

In response to this:

Version(s):
4.17+

Issue:
OSDOCS-15831

Link to docs preview:

QE review:

  • N/A internal docs work

Additional information:
This work includes removing L3 headings that are not supported in DITA migration. Included workaround are replacing certain xrefs with hard links in modules; and moving other xrefs to Additional resources.

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.

@ocpdocs-previewbot
Copy link

ocpdocs-previewbot commented Aug 13, 2025

🤖 Thu Aug 14 13:15:32 - Prow CI generated the docs preview:

https://97534--ocpdocs-pr.netlify.app/microshift/latest/microshift_install_get_ready/microshift-install-get-ready.html


For most installation types, you must also take the following steps:

* Download the pull secret from the Red{nbsp}Hat Hybrid Cloud Console using the following link:

This comment was marked as off-topic.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

MicroShift does not have this attribute.

@openshift-ci
Copy link

openshift-ci bot commented Aug 14, 2025

@ShaunaDiaz: 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.

@openshift-ci-robot
Copy link

openshift-ci-robot commented Aug 14, 2025

@ShaunaDiaz: This pull request references OSDOCS-15831 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target either version "4.20." or "openshift-4.20.", but it targets "aem-migration" instead.

In response to this:

Version(s):
4.17+

Issue:
OSDOCS-15831

Link to docs preview:
microshift_install_get_ready

QE review:

  • N/A internal docs work

Additional information:
This work includes removing L3 headings that are not supported in DITA migration.
Included workarounds for indeterminate issues are: 1) replacing certain xrefs with hard links in modules; 2) moving other xrefs to Additional resources; 3) removing words attached to links (that aren't the titles of the links). The linking strategy is in place here to have a passing build.

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 Aug 14, 2025

@ShaunaDiaz: This pull request references OSDOCS-15831 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target either version "4.20." or "openshift-4.20.", but it targets "aem-migration" instead.

In response to this:

Version(s):
4.17+

Issue:
OSDOCS-15831

Link to docs preview:
microshift_install_get_ready

QE review:

  • N/A internal docs work

Additional information:
This work includes removing L3 headings that are not supported in DITA migration.
Included workarounds for indeterminate issues are: 1) replacing certain xrefs with hard links in modules; 2) moving other xrefs to Additional resources; 3) removing words attached to links (that aren't the titles of the links). The linking strategy is in place here to have a passing build (and in a way that is easy for a doc user to digest).

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.

@ShaunaDiaz ShaunaDiaz added the merge-review-needed Signifies that the merge review team needs to review this PR label Aug 14, 2025
@lpettyjo lpettyjo 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 merge-review-in-progress Signifies that the merge review team is reviewing this PR labels Aug 14, 2025
@lpettyjo lpettyjo merged commit 5f46424 into openshift:main Aug 14, 2025
2 checks passed
@lpettyjo
Copy link
Contributor

/cherrypick enterprise-4.20

@lpettyjo
Copy link
Contributor

/cherrypick enterprise-4.19

@lpettyjo
Copy link
Contributor

/cherrypick enterprise-4.18

@openshift-cherrypick-robot

@lpettyjo: new pull request created: #97605

In response to this:

/cherrypick enterprise-4.20

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

@lpettyjo: new pull request created: #97606

In response to this:

/cherrypick enterprise-4.19

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

@lpettyjo: #97534 failed to apply on top of branch "enterprise-4.18":

Applying: OSDOCS-15831: mod get ready to install assembly MicroShift
Using index info to reconstruct a base tree...
M	microshift_install_get_ready/microshift-install-get-ready.adoc
Falling back to patching base and 3-way merge...
Auto-merging microshift_install_get_ready/microshift-install-get-ready.adoc
CONFLICT (content): Merge conflict in microshift_install_get_ready/microshift-install-get-ready.adoc
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config advice.mergeConflict false"
Patch failed at 0001 OSDOCS-15831: mod get ready to install assembly MicroShift

In response to this:

/cherrypick enterprise-4.18

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.

@lpettyjo
Copy link
Contributor

/cherrypick enterprise-4.17

@openshift-cherrypick-robot

@lpettyjo: #97534 failed to apply on top of branch "enterprise-4.17":

Applying: OSDOCS-15831: mod get ready to install assembly MicroShift
Using index info to reconstruct a base tree...
M	microshift_install_get_ready/microshift-install-get-ready.adoc
Falling back to patching base and 3-way merge...
Auto-merging microshift_install_get_ready/microshift-install-get-ready.adoc
CONFLICT (content): Merge conflict in microshift_install_get_ready/microshift-install-get-ready.adoc
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config advice.mergeConflict false"
Patch failed at 0001 OSDOCS-15831: mod get ready to install assembly MicroShift

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

branch/enterprise-4.17 branch/enterprise-4.18 branch/enterprise-4.19 branch/enterprise-4.20 jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. ok-to-merge size/L Denotes a PR that changes 100-499 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants