Bug 1995408

Summary:	RHV resources referenced on CRs by ID can be confused with provider not found in the inventory.
Product:	Migration Toolkit for Virtualization	Reporter:	Ilanit Stein <istein>
Component:	Documentation	Assignee:	Avital Pinnick <apinnick>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Ilanit Stein <istein>
Severity:	high	Docs Contact:	Avital Pinnick <apinnick>
Priority:	high
Version:	2.1.0	CC:	apinnick, fdupont, istein, jortel
Target Milestone:	---
Target Release:	2.1.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1994037	Environment:
Last Closed:	2021-09-02 20:57:08 UTC	Type:	---
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:	1994037
Bug Blocks:

Description Ilanit Stein 2021-08-19 03:19:01 UTC

Please document the below as a known issue for MTV-2.1. It is targeted to MTV-2.2.

+++ This bug was initially created as a clone of Bug #1994037 +++

Description of problem:

RHV resources referenced on CRs by ID can be confused with provider not found in the inventory.  For example: on the network map CR, if the ID (instead of Name) value is "fast/network123", this will result in the expected 404 (NotFound).  However, because of the X-Provider reply header is missing, the controller will interpret as - The provider has not been added to the inventory.

As a result, the CR is never fully reconciled.

Affects:
- Plan CR
- NetworkMap CR
- StorageMap CR
- Host CR

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

2.1.


How reproducible:

Always.


Steps to Reproduce:
1. Create a CR with the ref ID as described in the description.
2. Note: the CR: Generation and ObservedGeneration never match and the continuous reQ=3 in the controller log.
3.

Actual results:

CR never get reconciled.


Expected results:

CR is reconciled.


Additional info:

--- Additional comment from Fabien Dupont on 2021-08-16 16:38:11 UTC ---

This is kind of an edge case only when malforming the id string in the CR through the API.
Targeting to MTV 2.2.0.

Comment 2 Fabien Dupont 2021-09-02 20:57:08 UTC

The MTV 2.1 release notes include Bug 1994037 in the Known Issues section:
https://access.redhat.com/documentation/en-us/migration_toolkit_for_virtualization/2.1/html/release_notes/rn-21_release-notes#rhv-resource-uuid-causes-a-provider-not-found-error-21_release-notes

Marking this BZ as CLOSED/CURRENTRELEASE.