Bug 2185575
| Summary: | Allow rebuilding of host that were imported from other satellite using bootstrap script / Global registration template. | ||
|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | Satyajit Das <sadas> |
| Component: | Provisioning | Assignee: | satellite6-bugs <satellite6-bugs> |
| Status: | CLOSED MIGRATED | QA Contact: | Satellite QE Team <sat-qe-bz-list> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.12.0 | CC: | aubin.guillemette, lstejska, sshtein |
| Target Milestone: | Unspecified | Keywords: | MigratedToJIRA, 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: | Environment: | ||
| Last Closed: | 2024-06-06 16:12:43 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Satyajit Das
2023-04-10 11:02:55 UTC
> As the host is successfully migrated using global registration, so the host should be rebuilt without any issues. Global registration is not for the managed hosts, it's for unmanaged hosts primarily. > 2. Manage and associate the VM under the compute resource configured in the new satellite. If the VM is managed by compute resource, why not use the Import hosts feature from the compute resource? Not sure what "Global registration" means. We migrated the hosts to a new Satellite using the bootstrap.py script. After doing this, the host is associated with the right organization/location/hostgroup/activation key, but it does not have a "build id" visible on the host detail page. We can click the "rebuild" button and from the web interface it appears that the host is in rebuild mode and can be reinstalled, but this is not the case. The hosts are not managed by a compute resource. After further tests, I am not seeing this behavior consistently. Some hosts that have been imported can be rebuilt successfully. At this time I am not sure what the pattern is. 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. |