MIG-1507_ MTC 1.8.3 Release Notes

[HagayVider1]

trafficstars

IN PROGRESS - DO NOT MERGE

JIRA

• MIG-1507

PREVIEW

• ---

OCP VERSIONS

• OCP 4.12 → branch/enterprise-4.12
• 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

MTC 1.8.3 release notes

Version(s): 1.8.3

Issue: MIG-1507

Link to docs preview:

QE review:

• [ ] QE has approved this change.

Additional information:

[ocpdocs-previewbot]

🤖 Mon Apr 15 19:23:10 - Prow CI generated the docs preview:

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

[anarnold97]

@HagayVider1 please seen build errors

 asciidoctor: WARNING: modules/migration-mtc-release-notes-1-7-14.adoc: line 9: id assigned to section already in use: resolved-issues-1-7-14_mtc-release-notes
asciidoctor: WARNING: modules/migration-mtc-release-notes-1-7-14.adoc: line 47: id assigned to section already in use: known-issues-1-7-14_mtc-release-notes

You have duplicate IDs

[openshift-ci[bot]]

@HagayVider1: 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/test-infra repository. I understand the commands that are listed here.

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close. Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[openshift-merge-robot]

PR needs rebase.

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

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten. Rotten issues close after an additional 30d of inactivity. Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten /remove-lifecycle stale

[openshift-bot]

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen. Mark the issue as fresh by commenting /remove-lifecycle rotten. Exclude this issue from closing again by commenting /lifecycle frozen.

/close

[openshift-ci[bot]]

@openshift-bot: Closed this PR.

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen. Mark the issue as fresh by commenting /remove-lifecycle rotten. Exclude this issue from closing again by commenting /lifecycle frozen.

/close

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.