Bug 2054758
| Summary: | Satellite 6.10 clone is failing with user pulp doesn't exist | |||
|---|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | Shravan Kumar Tiwari <shtiwari> | |
| Component: | Satellite Clone | Assignee: | Evgeni Golov <egolov> | |
| Status: | CLOSED ERRATA | QA Contact: | Lukas Pramuk <lpramuk> | |
| Severity: | high | Docs Contact: | ||
| Priority: | high | |||
| Version: | 6.10.0 | CC: | ahumbe, alex.bron, egolov, ehelms, fandrieu, mkalyat, mmccune, pcreech, sussen | |
| Target Milestone: | 6.11.0 | Keywords: | Triaged | |
| Target Release: | Unused | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | satellite-clone-3.0.0 | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | ||
| Clone Of: | ||||
| : | 2093413 (view as bug list) | Environment: | ||
| Last Closed: | 2022-07-05 14:33:19 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
Shravan Kumar Tiwari
2022-02-15 16:26:45 UTC
and to close the circle from an out-of-BZ mail thread we had: Just to be sure, the customer is using the procedure described in https://access.redhat.com/documentation/en-us/red_hat_satellite/6.10/html/upgrading_and_updating_red_hat_satellite/cloning_satellite_server and there using the alternative "rsync" way to get the pulp data over to the new system? If so, they can workaround the issue by pre-creating the pulp user like this: useradd --home-dir /var/lib/pulp --no-create-home --system --shell /sbin/nologin pulp We'll work on a proper fix, but at least the customer can be unblocked in the meantime. huh, seems I never answered the needinfos here: - yes, we can assume the cloned system is healthy (as long as there are no external capsules involved, which is the only step that was omitted) - yes, doc bug please, yum should be used in that case - if the certificate has old an new names, satellite-change-hostname should be able to rename the machine without re-registration of the clients. emphasis on *should* as that's not my primary knowledge domain. VERIFIED.
@Satellite 6.11.0 Snap20
satellite-clone-3.1.0-1.el8sat.noarch
1) Create/Have a 6.11.0 backup
2) Copy backup to target machine and remove pulp_data.tar to do clone without pulp data
# satellite-clone -y
...
TASK [satellite-clone : include_tasks] ***********************************************************************************************************************
Wednesday 18 May 2022 04:47:38 -0400 (0:02:04.423) 0:08:00.065 *********
included: /usr/share/satellite-clone/roles/satellite-clone/tasks/ensure_pulp_data_permissions.yml for sat.example.com
TASK [satellite-clone : Ensure pulp group exists] ************************************************************************************************************
Wednesday 18 May 2022 04:47:38 -0400 (0:00:00.079) 0:08:00.145 *********
changed: [sat.example.com]
TASK [satellite-clone : Ensure pulp user exists] *************************************************************************************************************
Wednesday 18 May 2022 04:47:39 -0400 (0:00:00.560) 0:08:00.705 *********
changed: [sat.example.com]
TASK [satellite-clone : Check /var/lib/pulp ownership] *******************************************************************************************************
Wednesday 18 May 2022 04:47:40 -0400 (0:00:00.614) 0:08:01.320 *********
ok: [sat.example.com]
TASK [satellite-clone : Correct ownership of /var/lib/pulp] **************************************************************************************************
Wednesday 18 May 2022 04:47:40 -0400 (0:00:00.379) 0:08:01.699 *********
skipping: [sat.example.com]
...
>>> satellite clone successfully ensures pulp user/group exist
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Moderate: Satellite 6.11 Release), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2022:5498 |