Bug 1963682 - [RFE] Simplify MTV installation by creating the ForkliftController automatically
Summary: [RFE] Simplify MTV installation by creating the ForkliftController automatically
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Migration Toolkit for Virtualization
Classification: Red Hat
Component: Operator
Version: 2.0.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 2.2.0
Assignee: Franco Bladilo
QA Contact: Ilanit Stein
Avital Pinnick
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-05-23 13:36 UTC by Ilanit Stein
Modified: 2021-10-12 11:34 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-10-12 11:34:07 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github konveyor forklift-operator pull 126 0 None closed BZ 1963682 - Create the ForkliftController CR at install time 2021-06-08 18:26:44 UTC

Description Ilanit Stein 2021-05-23 13:36:42 UTC
Description of problem:
Currently MTV installation is composed of 2 steps:
1. Install MTV Operator
2. Create the ForkliftConstoller

would be good to have step 2 executed automatically, so that MTV installation would be a single step operation - That will ease the user.

Version-Release number of selected component (if applicable):
MTV-2.0.0

Comment 1 Fabien Dupont 2021-06-24 06:47:40 UTC
The change is not enough. The operator only tells the user that a ForkliftController CR is required, but doesn't create it. Moving back to POST.

Comment 2 Fabien Dupont 2021-07-05 19:55:49 UTC
Apparently, operator-sdk doesn't support creating CRs. And until the CR is created, the operator playbook will not run, so we cannot add a task in the Ansible role to create the CR.

Comment 3 Fabien Dupont 2021-10-12 11:34:07 UTC
Chicken and egg problem. All other operators have to create at least one CR to bootstrap any operation.
Closing as WONTFIX.


Note You need to log in before you can comment on or make changes to this bug.