OSDOCS-8693: add Getting Support assembly MicroShift

[ShaunaDiaz]

Version(s):
4.14+

Issue:
https://issues.redhat.com/browse/OSDOCS-8693

Link to docs preview:
Getting support
OCP Getting support

Support review:

• Support has approved this change.

Additional information:
Also replaces DDF with module that links to creating a Jira

[openshift-ci-robot]

@ShaunaDiaz: This pull request references OSDOCS-8693 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.15.0" version, but no target version was set.

In response to this:

Version(s):
4.14+

Issue:
https://issues.redhat.com/browse/OSDOCS-8693

Link to docs preview:

Support review:

• Support has approved this change.

Additional information:
Also replaces DDF with link to create a Jira

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.

[ocpdocs-previewbot]

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

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

[openshift-ci-robot]

@ShaunaDiaz: This pull request references OSDOCS-8693 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.15.0" version, but no target version was set.

In response to this:

Version(s):
4.14+

Issue:
https://issues.redhat.com/browse/OSDOCS-8693

Link to docs preview:
Getting support

Support review:

• Support has approved this change.

Additional information:
Also replaces DDF with link to create a Jira

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.

[vwalek]

/lgtm

[openshift-ci-robot]

@ShaunaDiaz: This pull request references OSDOCS-8693 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.15.0" version, but no target version was set.

In response to this:

Version(s):
4.14+

Issue:
https://issues.redhat.com/browse/OSDOCS-8693

Link to docs preview:
Getting support
OCP Getting support)[https://68476--docspreview.netlify.app/openshift-enterprise/latest/support/getting-support]

Support review:

• Support has approved this change.

Additional information:
Also replaces DDF with link to create a Jira

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-ci-robot]

@ShaunaDiaz: This pull request references OSDOCS-8693 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.15.0" version, but no target version was set.

In response to this:

Version(s):
4.14+

Issue:
https://issues.redhat.com/browse/OSDOCS-8693

Link to docs preview:
Getting support
OCP Getting support)[https://68476--docspreview.netlify.app/openshift-enterprise/latest/support/getting-support]

Support review:

• Support has approved this change.

Additional information:
Also replaces DDF with link to create a Jira

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-ci]

New changes are detected. LGTM label has been removed.

[ShaunaDiaz]

/label peer-review-needed

[openshift-ci-robot]

@ShaunaDiaz: This pull request references OSDOCS-8693 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.15.0" version, but no target version was set.

In response to this:

Version(s):
4.14+

Issue:
https://issues.redhat.com/browse/OSDOCS-8693

Link to docs preview:
Getting support
OCP Getting support

Support review:

• Support has approved this change.

Additional information:
Also replaces DDF with link to create a Jira

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-ci-robot]

@ShaunaDiaz: This pull request references OSDOCS-8693 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.15.0" version, but no target version was set.

In response to this:

Version(s):
4.14+

Issue:
https://issues.redhat.com/browse/OSDOCS-8693

Link to docs preview:
Getting support
OCP Getting support

Support review:

• Support has approved this change.

Additional information:
Also replaces DDF with module that links to creating a Jira

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.

[aldiazRH]

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

[aldiazRH]

LGTM!

[aldiazRH]

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

[ShaunaDiaz]

/label merge-review-needed

[jldohmann]

LGTM, nice work Shauna!

[jldohmann]

/cherrypick enterprise-4.15

[jldohmann]

/cherrypick enterprise-4.14

[openshift-cherrypick-robot]

@jldohmann: #68476 failed to apply on top of branch "enterprise-4.15":

Applying: OSDOCS-8693: add Getting Support assembly MicroShift
Using index info to reconstruct a base tree...
M	_attributes/attributes-microshift.adoc
M	modules/support.adoc
Falling back to patching base and 3-way merge...
Auto-merging modules/support.adoc
CONFLICT (content): Merge conflict in modules/support.adoc
Auto-merging _attributes/attributes-microshift.adoc
CONFLICT (content): Merge conflict in _attributes/attributes-microshift.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 OSDOCS-8693: add Getting Support assembly MicroShift
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]

@jldohmann: #68476 failed to apply on top of branch "enterprise-4.14":

Applying: OSDOCS-8693: add Getting Support assembly MicroShift
Using index info to reconstruct a base tree...
M	_attributes/attributes-microshift.adoc
M	_topic_maps/_topic_map_ms.yml
M	modules/support.adoc
Falling back to patching base and 3-way merge...
Auto-merging modules/support.adoc
CONFLICT (content): Merge conflict in modules/support.adoc
Auto-merging _topic_maps/_topic_map_ms.yml
Auto-merging _attributes/attributes-microshift.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 OSDOCS-8693: add Getting Support assembly MicroShift
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.

[jldohmann]

@ShaunaDiaz it looks like you'll have to manually CP to the 4.14 and 4.15 branches 🙃 feel free to ping me when those are up and i'll merge for you

[vwalek]

Hey, sorry, just read this sentence and do not understand what it means

Include data gathered using the sos tool or etcd as a starting point, 
plus any issue-specific data that is not collected in those logs.

There is no etcd tool, should be "inlcude data gathered using sos tool plus any issue-specific data."
I will report that as a new issue in jira.

[ShaunaDiaz]

Hey, sorry, just read this sentence and do not understand what it means

Include data gathered using the sos tool or etcd as a starting point, 
plus any issue-specific data that is not collected in those logs.

There is no etcd tool, should be "inlcude data gathered using sos tool plus any issue-specific data." I will report that as a new issue in jira.

See docs here: https://access.redhat.com/documentation/en-us/red_hat_build_of_microshift/4.14/html/support/microshift-etcd

[bergerhoffer]

@ShaunaDiaz @jldohmann It looks like this is failing because #67345 only went into 4.15. This should have gone into main too

@ShaunaDiaz Any time you are touching ANY files outside of the release notes file, it has to go into main first. Can you please get the necessary changes from that PR into main?

It also looks like this PR needs to get into main as well: #67051

I think you'll still need to do a manual cherrypick here though, because it's main where the items need to be resolved. But after all of this is resolved, then 4.15 and main should be in sync for these files currently in conflict.

The only file that should be out of sync is the actual release notes file.

[ShaunaDiaz]

@ShaunaDiaz @jldohmann It looks like this is failing because #67345 only went into 4.15. This should have gone into main too

@ShaunaDiaz Any time you are touching ANY files outside of the release notes file, it has to go into main first. Can you please get the necessary changes from that PR into main?

It also looks like this PR needs to get into main as well: #67051

I think you'll still need to do a manual cherrypick here though, because it's main where the items need to be resolved. But after all of this is resolved, then 4.15 and main should be in sync for these files currently in conflict.

The only file that should be out of sync is the actual release notes file.

@bergerhoffer #67345 is the placement of the release notes file in 4.15 and should not go in the main (this the actual adoc, not the build file that went in main)

#67051 isn't my PR, I'm not certain what I can do with this one?