Bug 1840226

Summary: [MIG-UI] Empty playbook hooks break the migration plan
Product: OpenShift Container Platform Reporter: Sergio <sregidor>
Component: Migration ToolingAssignee: Erik Nelson <ernelson>
Status: CLOSED ERRATA QA Contact: Xin jiang <xjiang>
Severity: medium Docs Contact:
Priority: medium    
Version: 4.4CC: chezhang, ernelson, mberube, rjohnson, rpattath, whu, xjiang
Target Milestone: ---   
Target Release: 4.5.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1840286 (view as bug list) 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:
Bug Depends On:    
Bug Blocks: 1840286    

Description Sergio 2020-05-26 15:15:51 UTC
Description of problem:
When we configure an empty playbook when we add a hook to a migration plan, the migration plan is left in a state where we cannot edit it in order to fix the empty playbook

Version-Release number of selected component (if applicable):
CAM 1.2 stage

How reproducible:
Always

Steps to Reproduce:
1. Create a migration plan
2. In hooks screen add a hook to the migration plan
3. Leave the field "Ansible playbook" empty. Do not introduce any playbook.

Actual results:
The migration plan is broken and in "Not Ready" status. When we try to edit the migration plan in order to fix the problem, the edit screen is broken before we can reach the hook that we need to edit.

Expected results:
Probably empty playbooks should not be allowed.

Additional info:

Comment 2 Erik Nelson 2020-05-26 17:01:55 UTC
https://github.com/konveyor/mig-ui/pull/878 accidentally added the bz link

Comment 7 Xin jiang 2020-05-27 07:02:39 UTC
Verified. once the field "Ansible playbook" is  empty. It will prompt that "Ansible file upload required"

Comment 8 Xin jiang 2020-05-27 13:41:05 UTC
Since Target Release is 4.5.0, we have to wait for ON_QA at 4.5.0. Reset it to ON_QA.

Comment 10 errata-xmlrpc 2020-05-28 11:10:47 UTC
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