Skip to content

MIG-1687: Release notes for MTC 1.8.6 #91067

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.

Sign up for GitHub

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

Jump to bottom
Merged
merged 1 commit into from
Apr 22, 2025
Merged

MIG-1687: Release notes for MTC 1.8.6 #91067

merged 1 commit into from
Apr 22, 2025

Conversation

anarnold97
Copy link
Contributor

@anarnold97 anarnold97 commented Mar 25, 2025 •
edited
Loading

JIRA

Version(s):

  • OCP 4.13 → branch/enterprise-4.13
  • OCP 4.14 → branch/enterprise-4.14
  • OCP 4.15 → branch/enterprise-4.15
  • OCP 4.16 → branch/enterprise-4.16
  • OCP 4.17 → branch/enterprise-4.17
  • OCP 4.18 → branch/enterprise-4.18
  • OCP 4.19 → branch/enterprise-4.19

Link to docs preview:

QE review:

  • QE has approved this change.

Additional information:

@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Mar 25, 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 Mar 25, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Mar 25, 2025 •
edited by openshift-ci bot
Loading

@anarnold97: This pull request references MIG-1687 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 task to target the "4.19.0" version, but no target version was set.

In response to this:

JIRA

Version(s):

Issue:

Link to docs preview:

QE review:

  • QE has approved this change.

Additional information:

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/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Mar 25, 2025
@ocpdocs-previewbot
Copy link

ocpdocs-previewbot commented Mar 25, 2025 •
edited
Loading

🤖 Thu Apr 17 17:57:40 - Prow CI generated the docs preview:

https://91067--ocpdocs-pr.netlify.app/openshift-enterprise/latest/migration_toolkit_for_containers/release_notes/mtc-release-notes.html

@openshift-ci-robot
Copy link

openshift-ci-robot commented Apr 5, 2025 •
edited by openshift-ci bot
Loading

@anarnold97: This pull request references MIG-1687 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 task to target the "4.19.0" version, but no target version was set.

In response to this:

JIRA

Version(s):

  • OCP 4.13 → branch/enterprise-4.13
  • OCP 4.14 → branch/enterprise-4.14
  • OCP 4.15 → branch/enterprise-4.15
  • OCP 4.16 → branch/enterprise-4.16
  • OCP 4.17 → branch/enterprise-4.17
  • OCP 4.18 → branch/enterprise-4.18
  • OCP 4.19 → branch/enterprise-4.19

Link to docs preview:

QE review:

  • QE has approved this change.

Additional information:

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 Apr 5, 2025 •
edited by openshift-ci bot
Loading

@anarnold97: This pull request references MIG-1687 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 task to target the "4.19.0" version, but no target version was set.

In response to this:

JIRA

Version(s):

  • OCP 4.13 → branch/enterprise-4.13
  • OCP 4.14 → branch/enterprise-4.14
  • OCP 4.15 → branch/enterprise-4.15
  • OCP 4.16 → branch/enterprise-4.16
  • OCP 4.17 → branch/enterprise-4.17
  • OCP 4.18 → branch/enterprise-4.18
  • OCP 4.19 → branch/enterprise-4.19

Link to docs preview:

QE review:

  • QE has approved this change.

Additional information:

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.

@anarnold97 anarnold97 changed the title WIP - MIG-1687: Release notes for MTC 1.8.6 MIG-1687: Release notes for MTC 1.8.6 Apr 16, 2025
@openshift-ci openshift-ci bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Apr 16, 2025
@anarnold97
Copy link
Contributor Author

@midays & @rayfordj - updated, please re-review
Thanks

@rayfordj
Copy link

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Apr 16, 2025
@rayfordj
Copy link

/unassign @rayfordj

@anarnold97 anarnold97 closed this Apr 16, 2025
@anarnold97 anarnold97 reopened this Apr 16, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Apr 16, 2025 •
edited by openshift-ci bot
Loading

@anarnold97: This pull request references MIG-1687 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 task to target the "4.19.0" version, but no target version was set.

In response to this:

JIRA

Version(s):

  • OCP 4.13 → branch/enterprise-4.13
  • OCP 4.14 → branch/enterprise-4.14
  • OCP 4.15 → branch/enterprise-4.15
  • OCP 4.16 → branch/enterprise-4.16
  • OCP 4.17 → branch/enterprise-4.17
  • OCP 4.18 → branch/enterprise-4.18
  • OCP 4.19 → branch/enterprise-4.19

Link to docs preview:

QE review:

  • QE has approved this change.

Additional information:

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.

@anarnold97 anarnold97 force-pushed the MIG-1687-Release-notes-for-MTC-1.8.6 branch from d70ed1e to d46ce9c Compare April 16, 2025 19:47
@anarnold97 anarnold97 force-pushed the MIG-1687-Release-notes-for-MTC-1.8.6 branch from 8bc4c14 to a31f27e Compare April 17, 2025 17:44
@anarnold97
Copy link
Contributor Author

@lpettyjo - thanks

@openshift-ci OpenShift CI
Copy link

openshift-ci bot commented Apr 17, 2025

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

@anarnold97
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 Apr 22, 2025
@jab-rh jab-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 Apr 22, 2025
@jab-rh jab-rh merged commit 60f9a2c into openshift:main Apr 22, 2025
2 checks passed
@jab-rh
Copy link
Contributor

jab-rh commented Apr 22, 2025

/cherry-pick enterprise-4.19

@jab-rh
Copy link
Contributor

jab-rh commented Apr 22, 2025

/cherry-pick enterprise-4.18

@jab-rh
Copy link
Contributor

jab-rh commented Apr 22, 2025

/cherry-pick enterprise-4.17

@jab-rh
Copy link
Contributor

jab-rh commented Apr 22, 2025

/cherry-pick enterprise-4.16

@openshift-cherrypick-robot
Copy link

@jab-rh: new pull request created: #92497

In response to this:

/cherry-pick 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 openshift-cherrypick-robot mentioned this pull request Apr 22, 2025
Merged
@jab-rh
Copy link
Contributor

jab-rh commented Apr 22, 2025

/cherry-pick enterprise-4.15

@openshift-cherrypick-robot openshift-cherrypick-robot mentioned this pull request Apr 22, 2025
Merged
@openshift-cherrypick-robot
Copy link

@jab-rh: new pull request created: #92498

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.

@jab-rh
Copy link
Contributor

jab-rh commented Apr 22, 2025

/cherry-pick enterprise-4.14

@openshift-cherrypick-robot
Copy link

@jab-rh: new pull request created: #92499

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.

@openshift-cherrypick-robot openshift-cherrypick-robot mentioned this pull request Apr 22, 2025
Merged
@jab-rh
Copy link
Contributor

jab-rh commented Apr 22, 2025

/cherry-pick enterprise-4.13

@openshift-cherrypick-robot
Copy link

@jab-rh: new pull request created: #92500

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.

@openshift-cherrypick-robot openshift-cherrypick-robot mentioned this pull request Apr 22, 2025
Merged
@openshift-cherrypick-robot
Copy link

@jab-rh: new pull request created: #92501

In response to this:

/cherry-pick 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-sigs/prow repository.

@openshift-cherrypick-robot openshift-cherrypick-robot mentioned this pull request Apr 22, 2025
Merged
@openshift-cherrypick-robot
Copy link

@jab-rh: new pull request created: #92502

In response to this:

/cherry-pick 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-sigs/prow repository.

@openshift-cherrypick-robot openshift-cherrypick-robot mentioned this pull request Apr 22, 2025
Merged
@openshift-cherrypick-robot
Copy link

@jab-rh: #91067 failed to apply on top of branch "enterprise-4.13":

Applying: WIP - MIG-1687: Release notes for MTC 1.8.6
.git/rebase-apply/patch:62: trailing whitespace.
After running a migration using {mtc-short}, the UI incorrectly indicates that the migration was successful, with the status shown as *Migration succeeded*. However, the Direct Volume Migration (DVM) phase failed. This misleading status appears on both the *Migration* and the *Migration Details* pages. This issue has been resolved in {mtc-short} 1.8.6. link:https://issues.redhat.com/browse/MIG-1711[(MIG-1711)] 
warning: 1 line adds whitespace errors.
Using index info to reconstruct a base tree...
M	migration_toolkit_for_containers/release_notes/mtc-release-notes.adoc
Falling back to patching base and 3-way merge...
Auto-merging migration_toolkit_for_containers/release_notes/mtc-release-notes.adoc
CONFLICT (content): Merge conflict in migration_toolkit_for_containers/release_notes/mtc-release-notes.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 WIP - MIG-1687: Release notes for MTC 1.8.6

In response to this:

/cherry-pick enterprise-4.13

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
Reviewers

@rayfordj rayfordj rayfordj left review comments

@lpettyjo lpettyjo lpettyjo left review comments

@ocpdocs-vale-bot ocpdocs-vale-bot ocpdocs-vale-bot left review comments

@midays midays midays approved these changes

Assignees
No one assigned
Labels
branch/enterprise-4.13 branch/enterprise-4.14 branch/enterprise-4.15 branch/enterprise-4.16 branch/enterprise-4.17 branch/enterprise-4.18 branch/enterprise-4.19 jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. merge-review-in-progress Signifies that the merge review team is reviewing this PR MTC Label for all MTC PRs peer-review-done Signifies that the peer review team has reviewed this PR size/M Denotes a PR that changes 30-99 lines, ignoring generated files.
Projects
None yet
Milestone
Continuous Release
Development

Successfully merging this pull request may close these issues.
9 participants
@anarnold97 @openshift-ci-robot @ocpdocs-previewbot @rayfordj @jab-rh @openshift-cherrypick-robot @lpettyjo @midays @ocpdocs-vale-bot