Skip to content

Commit

Permalink
Disable REX on install
Browse files Browse the repository at this point in the history
Fixes #234
  • Loading branch information
John Mitsch committed Oct 24, 2017
1 parent 0c58206 commit 09387bf
Show file tree
Hide file tree
Showing 2 changed files with 3 additions and 2 deletions.
3 changes: 2 additions & 1 deletion docs/satellite-clone.md
Expand Up @@ -3,13 +3,14 @@
#### Important Notes ####

- The playbook will update the cloned Satellite hostname to match the hostname of the original Satellite from which the backup is generated.
- DHCP, DNS, and TFTP will be disabled during the install to avoid configuration errors. If you want to use provisioning on the cloned Satellite, you will have to manually re-enable these settings after the playbook run.
- DHCP, DNS, TFTP, and remote execution will be disabled during the install to avoid configuration errors. If you want to use provisioning on the cloned Satellite, you will have to manually re-enable these settings after the playbook run.
- The playbook will reset the admin password to "changeme".
- The playbook run may may take a while to complete.
- You can clone RHEL 6 backup data to a RHEL 7 machine. In this case, you must update the variable `rhel_migration` to true as explained later in this document. Please note that this scenario is supported only for *Satellite 6.2*.
- If you are using NFS for storage and your pulp backup tar file is large (>150 gb), you might see memory errors while untaring pulp data. In this case you can optionally choose to skip pulp restore (by setting `include_pulp_data` to `false` in `satellite-clone-vars.yml`).
- After running the playbook, existing manifests may have to be refreshed.
- Capsules will be unassociated with Lifecycle environments to avoid any interference with existing infrastructure. Instructions to reverse these changes can be found in `logs/reassociate_capsules.txt` under Satellite Clone's root directory
- It is recommended to clone to an environment that is isolated from your original Satellite's network. We take steps to disable communication from the cloned Satellite to existing capsules and hosts, but the only way to ensure this is in an isolated environment.

#### Prerequisites ####

Expand Down
2 changes: 1 addition & 1 deletion roles/satellite-clone/tasks/main.yml
Expand Up @@ -139,7 +139,7 @@
command: katello-installer --capsule-dns false --capsule-dhcp false --capsule-tftp false
when: satellite_version == 6.1
- name: run Satellite 6.2 installer
command: satellite-installer --scenario satellite --foreman-proxy-dns false --foreman-proxy-dhcp false --foreman-proxy-tftp false
command: satellite-installer --scenario satellite --foreman-proxy-dns false --foreman-proxy-dhcp false --foreman-proxy-tftp false --no-enable-foreman-plugin-remote-execution --no-enable-foreman-proxy-plugin-remote-execution-ssh
when: satellite_version == 6.2

- block:
Expand Down

0 comments on commit 09387bf

Please sign in to comment.