Bug 1581590

Summary:	Provisioning discovered host from oVirt via Foreman doesn't work
Product:	Red Hat Satellite	Reporter:	Moti Asayag <masayag>
Component:	Compute Resources - RHEV	Assignee:	Nobody <nobody>
Status:	CLOSED WONTFIX	QA Contact:	Satellite QE Team <sat-qe-bz-list>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	6.2.12	CC:	bbuckingham, bkearney, bugs, inecas, lhellebr, lstejska, lveyde, mperina, pkubica, rlavi, zhunting
Target Milestone:	Unspecified	Keywords:	Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1506547	Environment:
Last Closed:	2023-06-06 11:12:28 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Infra	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1506547
Bug Blocks:	1537122

Comment 3 Lukáš Hellebrandt 2019-09-04 11:43:16 UTC

FailedQA with Sat 6.6 snap 18, ovirt-engine 4.3.4.3-0.1.

Whatever I try, I can't get over InstallingOS phase.

1) Have a Satellite with forman-provider plugin installed, create all necessary entities.
2) Add Satellite as a provider to RHEV.
3) Add RHEV (in the same network as the Satellite) as a CR to Satellite (tried both APIv3 and APIv4).
4) Create new Host from the Foreman provider.

-> Machine provisioned successfully, status in the Satellite becomes "Installed". However, Host state in RHEV stays "InstallingOS" indefinitely. No error, no traceback.

It is possible there is some mistake on my side (doing this for the first time) but I really can't see it. If that's the case, we can transfer this to UX BZ.

Comment 4 Moti Asayag 2019-09-04 12:30:11 UTC

(In reply to Lukáš Hellebrandt from comment #3)
> FailedQA with Sat 6.6 snap 18, ovirt-engine 4.3.4.3-0.1.
> 
> Whatever I try, I can't get over InstallingOS phase.
> 
> 1) Have a Satellite with forman-provider plugin installed, create all
> necessary entities.
> 2) Add Satellite as a provider to RHEV.
> 3) Add RHEV (in the same network as the Satellite) as a CR to Satellite
> (tried both APIv3 and APIv4).
> 4) Create new Host from the Foreman provider.

That isn't the correct flow. The creation of the host should be executed from the engine's side.
See steps 6 and 7 in bug's description:

6. Boot undiscovered machine, wait for discovering in satellite
7. In Engine try to add host from external provider (satellite/foreman) and check discovered host.

step 7 is done by:
- Go to RHV web-admin --> Hosts --> New
- Check the "Use external provider" and choose the satellite provider
- Check discovered host
- Fill the missing parameter (password should be the host root password)

> 
> -> Machine provisioned successfully, status in the Satellite becomes
> "Installed". However, Host state in RHEV stays "InstallingOS" indefinitely.
> No error, no traceback.
> 
> It is possible there is some mistake on my side (doing this for the first
> time) but I really can't see it. If that's the case, we can transfer this to
> UX BZ.

Comment 5 Lukáš Hellebrandt 2019-09-04 13:11:55 UTC

Moti, that is exactly what I do.

Comment 11 Ron Lavi 2022-06-26 13:10:30 UTC

Hello, is this bug still reproducible in the latest Satellite?

Comment 12 Martin Perina 2022-06-27 06:56:24 UTC

Foreman integration has been deprecated and in RHV 4.4.7 completely removed:

https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.4/html/release_notes/removed_features_rhv#doc-wrapper

So hosts can be added into RHVM using RHV RESTAPI only, meaning you need to specify the same parameters (for example FQDN, root password, ...) regardless if the host is managed by Satellite or not.

Comment 14 Leos Stejskal 2023-06-06 11:12:28 UTC

As per Martin's comment [0], I'm closing the BZ as won't fix.

[0] https://bugzilla.redhat.com/show_bug.cgi?id=1581590#c12