mirror of
https://github.com/openshift/openshift-docs.git
synced 2026-02-05 12:46:18 +01:00
62 lines
4.6 KiB
Plaintext
62 lines
4.6 KiB
Plaintext
// Module included in the following assemblies:
|
|
//
|
|
// * migration_toolkit_for_containers/release_notes/mtc-release-notes-1-7.adoc
|
|
:_mod-docs-content-type: REFERENCE
|
|
[id="migration-mtc-release-notes-1-7-02_{context}"]
|
|
= {mtc-full} 1.7.2 release notes
|
|
|
|
[id="resolved-issues-1-7-02_{context}"]
|
|
== Resolved issues
|
|
|
|
This release has the following major resolved issues:
|
|
|
|
.MTC UI does not display logs correctly
|
|
In previous releases, the {mtc-first} UI did not display logs correctly. (link:https://bugzilla.redhat.com/show_bug.cgi?id=2062266[*BZ#2062266*])
|
|
|
|
.StorageClass conversion plan adding migstorage reference in migplan
|
|
In previous releases, StorageClass conversion plans had a `migstorage` reference even though it was not being used. (link:https://bugzilla.redhat.com/show_bug.cgi?id=2078459[*BZ#2078459*])
|
|
|
|
.Velero pod log missing from downloaded logs
|
|
In previous releases, when downloading a compressed (.zip) folder for all logs, the velero pod was missing. (link:https://bugzilla.redhat.com/show_bug.cgi?id=2076599[*BZ#2076599*])
|
|
|
|
.Velero pod log missing from UI drop down
|
|
In previous releases, after a migration was performed, the velero pod log was not included in the logs provided in the dropdown list. (link:https://bugzilla.redhat.com/show_bug.cgi?id=2076593[*BZ#2076593*])
|
|
|
|
.Rsync options logs not visible in log-reader pod
|
|
In previous releases, when trying to set any valid or invalid rsync options in the `migrationcontroller`, the log-reader was not showing any logs regarding the invalid options or about the rsync command being used. (link:https://bugzilla.redhat.com/show_bug.cgi?id=2079252[*BZ#2079252*])
|
|
|
|
.Default CPU requests on Velero/Restic are too demanding and fail in certain environments
|
|
In previous releases, the default CPU requests on Velero/Restic were too demanding and fail in certain environments. Default CPU requests for Velero and Restic Pods are set to 500m. These values were high. (link:https://bugzilla.redhat.com/show_bug.cgi?id=2088022[*BZ#2088022*])
|
|
|
|
|
|
|
|
|
|
[id="known-issues-1-7-02_{context}"]
|
|
== Known issues
|
|
|
|
This release has the following known issues:
|
|
|
|
.Updating the replication repository to a different storage provider type is not respected by the UI
|
|
After updating the replication repository to a different type and clicking *Update Repository*, it shows connection successful, but the UI is not updated with the correct details. When clicking on the *Edit* button again, it still shows the old replication repository information.
|
|
|
|
Furthermore, when trying to update the replication repository again, it still shows the old replication details. When selecting the new repository, it also shows all the information you entered previously and the *Update repository* is not enabled, as if there are no changes to be submitted. (link:https://bugzilla.redhat.com/show_bug.cgi?id=2102020[*BZ#2102020*])
|
|
|
|
.Migrations fails because the backup is not found
|
|
Migration fails at the restore stage because of initial backup has not been found. (link:https://bugzilla.redhat.com/show_bug.cgi?id=2104874[*BZ#2104874*])
|
|
|
|
.Update Cluster button is not enabled when updating Azure resource group
|
|
When updating the remote cluster, selecting the *Azure resource group* checkbox, and adding a resource group does not enable the *Update cluster* option. (link:https://bugzilla.redhat.com/show_bug.cgi?id=2098594[*BZ#2098594*])
|
|
|
|
.Error pop-up in UI on deleting migstorage resource
|
|
When creating a `backupStorage` credential secret in {OCP}, if the `migstorage` is removed from the UI, a 404 error is returned and the underlying secret is not removed. (link:https://bugzilla.redhat.com/show_bug.cgi?id=2100828[*BZ#2100828*])
|
|
|
|
.Miganalytic resource displaying resource count as 0 in UI
|
|
After creating a migplan from backend, the Miganalytic resource displays the resource count as `0` in UI. (link:https://bugzilla.redhat.com/show_bug.cgi?id=2102139[*BZ#2102139*])
|
|
|
|
.Registry validation fails when two trailing slashes are added to the Exposed route host to image registry
|
|
After adding two trailing slashes, meaning `//`, to the exposed registry route, the MigCluster resource is showing the status as `connected`. When creating a migplan from backend with DIM, the plans move to the `unready` status. (link:https://bugzilla.redhat.com/show_bug.cgi?id=2104864[*BZ#2104864*])
|
|
|
|
.Service Account Token not visible while editing source cluster
|
|
When editing the source cluster that has been added and is in *Connected* state, in the UI, the service account token is not visible in the field. To save the wizard, you have to fetch the token again and provide details inside the field. (link:https://bugzilla.redhat.com/show_bug.cgi?id=2097668[*BZ#2097668*])
|
|
|