openshift
TELCODOCS-1985: Day-2 upgrades for telco core clusters
Adding docs for Day-2 upgrades for telco core clusters
Version(s): 4.17+
Issue: https://issues.redhat.com/browse/TELCODOCS-1985
Link to docs preview: https://83448--ocpdocs-pr.netlify.app/openshift-enterprise/latest/edge_computing/day_2_core_cnf_clusters/upgrading/telco-upgrade-welcome
QE review:
- [ ] QE has approved this change.
@aireilly: This pull request references TELCODOCS-1985 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.18.0" version, but no target version was set.
In response to this:
Adding docs for Day-2 upgrades for telco core clusters
Version(s): 4.17+
Issue: https://issues.redhat.com/browse/TELCODOCS-1985
Link to docs preview:
QE review:
- [ ] QE has approved this change.
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.
🤖 Thu Oct 31 11:28:55 - Prow CI generated the docs preview:
https://83448--ocpdocs-pr.netlify.app/ https://83448--ocpdocs-pr.netlify.app/openshift-enterprise/latest/backup_and_restore/control_plane_backup_and_restore/backing-up-etcd.html https://83448--ocpdocs-pr.netlify.app/openshift-enterprise/latest/edge_computing/day_2_core_cnf_clusters/updating/telco-update-api.html https://83448--ocpdocs-pr.netlify.app/openshift-enterprise/latest/edge_computing/day_2_core_cnf_clusters/updating/telco-update-before-the-update.html https://83448--ocpdocs-pr.netlify.app/openshift-enterprise/latest/edge_computing/day_2_core_cnf_clusters/updating/telco-update-cnf-update-prep.html https://83448--ocpdocs-pr.netlify.app/openshift-enterprise/latest/edge_computing/day_2_core_cnf_clusters/updating/telco-update-completing-the-control-plane-only-update.html https://83448--ocpdocs-pr.netlify.app/openshift-enterprise/latest/edge_computing/day_2_core_cnf_clusters/updating/telco-update-completing-the-y-stream-update.html https://83448--ocpdocs-pr.netlify.app/openshift-enterprise/latest/edge_computing/day_2_core_cnf_clusters/updating/telco-update-completing-the-z-stream-update.html https://83448--ocpdocs-pr.netlify.app/openshift-enterprise/latest/edge_computing/day_2_core_cnf_clusters/updating/telco-update-ocp-update-prep.html https://83448--ocpdocs-pr.netlify.app/openshift-enterprise/latest/edge_computing/day_2_core_cnf_clusters/updating/telco-update-welcome.html
@aireilly: This pull request references TELCODOCS-1985 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.18.0" version, but no target version was set.
In response to this:
Adding docs for Day-2 upgrades for telco core clusters
Version(s): 4.17+
Issue: https://issues.redhat.com/browse/TELCODOCS-1985
Link to docs preview: https://83448--ocpdocs-pr.netlify.app/openshift-enterprise/latest/edge_computing/day_2_core_cnf_clusters/upgrading/telco-upgrade-welcome
QE review:
- [ ] QE has approved this change.
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.
/label peer-review-done /remove-label peer-review-needed /remove-label peer-review-in-progress
@aireilly: This pull request references TELCODOCS-1985 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.18.0" version, but no target version was set.
In response to this:
Adding docs for Day-2 upgrades for telco core clusters
Version(s): 4.17+
Issue: https://issues.redhat.com/browse/TELCODOCS-1985
Link to docs preview: https://83448--ocpdocs-pr.netlify.app/openshift-enterprise/latest/edge_computing/day_2_core_cnf_clusters/updating/telco-update-welcome
QE review:
- [ ] QE has approved this change.
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.
@aireilly: 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[bot] avatar](https://avatars.githubusercontent.com/in/91280?v=4 "Published by a pub.dev verified publisher"){kind=small}
@aireilly: This pull request references TELCODOCS-1985 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.18.0" version, but no target version was set.
In response to this:
Adding docs for Day-2 upgrades for telco core clusters
Version(s): 4.17+
Issue: https://issues.redhat.com/browse/TELCODOCS-1985
Link to docs preview: https://83448--ocpdocs-pr.netlify.app/openshift-enterprise/latest/edge_computing/day_2_core_cnf_clusters/updating/telco-update-welcome
QE review:
- [x] QE has approved this change.
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.
@aireilly: #83448 failed to apply on top of branch "enterprise-4.17":
Applying: Adding docs for TELCODOCS-1985: Day-2 upgrades for telco core CNF clusters
Using index info to reconstruct a base tree...
M .vale/styles/config/vocabularies/OpenShiftDocs/accept.txt
M _topic_maps/_topic_map.yml
Falling back to patching base and 3-way merge...
Auto-merging _topic_maps/_topic_map.yml
CONFLICT (content): Merge conflict in _topic_maps/_topic_map.yml
Auto-merging .vale/styles/config/vocabularies/OpenShiftDocs/accept.txt
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 Adding docs for TELCODOCS-1985: Day-2 upgrades for telco core CNF clusters
In response to this:
/cherry-pick 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.
@aireilly: new pull request created: #84299
In response to this:
/cherry-pick 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.
@aireilly: #83448 failed to apply on top of branch "enterprise-4.16":
Applying: Adding docs for TELCODOCS-1985: Day-2 upgrades for telco core CNF clusters
Using index info to reconstruct a base tree...
M .vale/styles/config/vocabularies/OpenShiftDocs/accept.txt
M _topic_maps/_topic_map.yml
Falling back to patching base and 3-way merge...
Auto-merging _topic_maps/_topic_map.yml
CONFLICT (content): Merge conflict in _topic_maps/_topic_map.yml
Auto-merging .vale/styles/config/vocabularies/OpenShiftDocs/accept.txt
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 Adding docs for TELCODOCS-1985: Day-2 upgrades for telco core CNF clusters
In response to this:
/cherry-pick 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.