Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1581590 - Provisioning discovered host from oVirt via Foreman doesn't work
Summary: Provisioning discovered host from oVirt via Foreman doesn't work
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Compute Resources - RHEV
Version: 6.2.12
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: Unspecified
Assignee: Nobody
QA Contact: Satellite QE Team
URL:
Whiteboard:
Depends On: 1506547
Blocks: 1537122
TreeView+ depends on / blocked
 
Reported: 2018-05-23 07:36 UTC by Moti Asayag
Modified: 2023-06-06 11:12 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1506547
Environment:
Last Closed: 2023-06-06 11:12:28 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github abenari rbovirt pull 124 0 None closed Replace unknown constant with string 2020-12-10 09:49:53 UTC
Github theforeman foreman-packaging pull 3382 0 None closed Update rubygem-ovirt_provision_plugin to 2.0.3 2020-12-10 09:49:55 UTC
Github theforeman ovirt_provision_plugin pull 14 0 None closed Fix missing method error 2020-12-10 09:49:56 UTC
Github theforeman ovirt_provision_plugin pull 15 0 None closed Fix missing method error 2020-12-10 09:49:56 UTC
Github theforeman ovirt_provision_plugin pull 21 0 None closed Fix provision for ovirtsdk4 2020-12-10 09:49:56 UTC
oVirt gerrit 84787 0 None MERGED core: fetch "puppet proxy id" and "puppet ca proxy id" from external hostgroup 2020-12-10 09:49:55 UTC
oVirt gerrit 85198 0 None MERGED core: fetch "puppet proxy id" and "puppet ca proxy id" from external hostgroup 2020-12-10 09:49:55 UTC

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
Note You need to log in before you can comment on or make changes to this bug.