This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
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 2255264 - The build status still shows `Pending Installation` even after the Bootdisk provisioning is successful on VMware 8
Summary: The build status still shows `Pending Installation` even after the Bootdisk p...
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Compute Resources - VMWare
Version: 6.15.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: stream
Assignee: satellite6-bugs
QA Contact: sganar
URL:
Whiteboard:
Depends On: 2247345
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-12-19 18:35 UTC by sganar
Modified: 2024-06-20 14:09 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 2279384 (view as bug list)
Environment:
Last Closed: 2024-06-06 16:38:58 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker   SAT-22047 0 None Migrated None 2024-06-20 14:09:32 UTC

Description sganar 2023-12-19 18:35:47 UTC 
Description of problem:

The build status still shows `Pending Installation` even after the Bootdisk provisioning is successful and the host is registered and has content access for the repos through Activation key selected

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

How reproducible:
Always

Steps to Reproduce:
1. Configure a Satellite for provisioning
2. Create a VMware CR
3. Create a host on VMware using the bootdisk method

Actual results:
After successful host provisioning The build status still shows `Pending Installation`

Expected results:
After successful host provisioning The build status should show `Installed`

Additional info:
This is observed only on VMware 8 specifically for Bootdisk provisioning. Vmware 7 works as expected.
Comment 1 Marek Hulan 2023-12-20 10:32:58 UTC 
Well, if Pending Installation is displayed, that means the provisioning was not successful. Typically, the last step of calling home did not work for some reason. Can you please capture production.log from the provisioning process? Also any logs from the installation would be helpful, e.g. logs from Anaconda. Very often, it means the networking isn't configured correctly and the provisioned machine can't reach out to the Satellite/Capsule. Or DNS does not work correctly.
Comment 4 Gaurav Talreja 2024-03-14 12:20:44 UTC 
Upstream foreman_bootdisk PR for the fixing this issue has been merged along with fog-vsphere PR, we can now move this to POST
https://github.com/theforeman/foreman_bootdisk/pull/158
https://github.com/fog/fog-vsphere/pull/292
Comment 6 Eric Helms 2024-06-06 16:38:58 UTC 
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "SAT-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.
Note You need to log in before you can comment on or make changes to this bug.