Bug 1829494
Summary: | [MIG-UI] To edit an existing hook breaks the migplan | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Sergio <sregidor> |
Component: | Migration Tooling | Assignee: | Ian <ibolton> |
Status: | CLOSED ERRATA | QA Contact: | Xin jiang <xjiang> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 4.4 | CC: | chezhang, dymurray, ernelson, jmatthew, jmontleo, pvauter, rjohnson, rpattath, whu, xjiang |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2020-05-28 11:10:47 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Sergio
2020-04-29 15:59:18 UTC
Using CAM 1.2 stage Following the steps described in this BZ we still get the executionNamespace and the serviceAccount fields empty. spec: destMigClusterRef: name: host namespace: openshift-migration hooks: - executionNamespace: "" phase: PreBackup reference: name: hook namespace: openshift-migration serviceAccount: "" migStorageRef: name: automatic namespace: openshift-migration namespaces: - mssql-example srcMigClusterRef: name: source-cluster namespace: openshift-migration We move the status to ASSIGNED. As an extra information, if we edit the service account and we change from source service account to target service account, the request fails and an error is prompted on the UI. Do you need this to be another BZ? or can we consider it as a part of this one since the hooks update is not working properly? We can open a new BZ for this behavior is necessary. Verified with CAM 1.2 Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2020:2326 |