search

RedHatSatellite / satellite-clone

Utility to assist cloning an existing Satellite 6 server to a new host
GNU General Public License v3.0
37 stars 31 forks source link

Fixes #29871 - Fix Hammer deprecation warning with lce #372

Closed chris1984 closed 4 years ago

chris1984 commented 4 years ago

Before on 6.5 below:

TASK [satellite-clone : Disassociate capsules with lifecycle environments (to avoid the cloned Satellite server talking with live capsules)] **********************************************************************
Friday 15 May 2020  12:35:40 -0400 (0:00:00.234)       1:07:09.580 ************ 
changed: [localhost]

stdout: All Capsules are unassociated with any lifecycle environments. This is to avoid any syncing errors with your original Satellite and any interference with existing infrastructure. To reverse these changes, run the following commands, making sure to replace the credentials with your own.
hammer -u admin -p changeme --csv capsule content add-lifecycle-environment --id 2 --environment-id 2

stderr: Warning: Option --environment-id is deprecated. Use --lifecycle-environment-id instead

After:

6.6:

TASK [satellite-clone : Disassociate capsules with lifecycle environments (to avoid the cloned Satellite server talking with live capsules)] *****************************************************************
Wednesday 20 May 2020  14:54:35 +0000 (0:00:00.076)       1:03:04.322 *********
changed: [localhost]

stdout: All Capsules are unassociated with any lifecycle environments. This is to avoid any syncing errors with your original Satellite and any interference with existing infrastructure. To reverse these changes, run the following commands, making sure to replace the credentials with your own.
hammer -u admin -p changeme --csv capsule content add-lifecycle-environment --id 2 --lifecycle-environment-id 2

6.5:

TASK [satellite-clone : Disassociate capsules with lifecycle environments (to avoid the cloned Satellite server talking with live capsules)] **********************************************************************
Monday 18 May 2020  16:00:31 -0400 (0:00:00.228)       1:08:06.776 ************ 
changed: [localhost]

stdout: All Capsules are unassociated with any lifecycle environments. This is to avoid any syncing errors with your original Satellite and any interference with existing infrastructure. To reverse these changes, run the following commands, making sure to replace the credentials with your own.
hammer -u admin -p changeme --csv capsule content add-lifecycle-environment --id 2 --environment-id 2

Starting to kick off tests on Dolly

chris1984 commented 4 years ago

@johnpmitsch Dolly passed with updated changes and manual tests are still good:

PLAY RECAP *********************************************************************
192.168.121.192            : ok=21   changed=16   unreachable=0    failed=0
192.168.121.22             : ok=21   changed=16   unreachable=0    failed=0
192.168.121.39             : ok=21   changed=16   unreachable=0    failed=0
192.168.121.91             : ok=21   changed=16   unreachable=0    failed=0

Wednesday 03 June 2020  15:08:54 -0400 (3:53:20.851)       4:11:57.110 ********

6.6:

TASK [satellite-clone : Disassociate capsules with lifecycle environments (to avoid the cloned Satellite server talking with live capsules)] *******************************************************************************************Wednesday 03 June 2020  11:09:35 -0400 (0:00:00.075)       1:12:16.294 ******** 
changed: [localhost] => {"changed": true, "rc": 0, "stderr": "", "stderr_lines": [], "stdout": "All Capsules are unassociated with any lifecycle environments. This is to avoid any syncing errors with your original Satellite and any interference with existing infrastructure. To reverse these changes, run the following commands, making sure to replace the credentials with your own.\nhammer -u admin -p changeme --csv capsule content add-lifecycle-environment --id 2 --lifecycle-environment-id 2\n", "stdout_lines": ["All Capsules are unassociated with any lifecycle environments. This is to avoid any syncing errors with your original Satellite and any interference with existing infrastructure. To reverse these changes, run the following commands, making sure to replace the credentials with your own.", "hammer -u admin -p changeme --csv capsule content add-lifecycle-environment --id 2 --lifecycle-environment-id 2"]}

stdout: All Capsules are unassociated with any lifecycle environments. This is to avoid any syncing errors with your original Satellite and any interference with existing infrastructure. To reverse these changes, run the following commands, making sure to replace the credentials with your own.
hammer -u admin -p changeme --csv capsule content add-lifecycle-environment --id 2 --lifecycle-environment-id 2

6.5:

TASK [satellite-clone : Disassociate capsules with lifecycle environments (to avoid the cloned Satellite server talking with live capsules)] **************************************************************Thursday 04 June 2020  18:24:48 -0400 (0:00:00.089)       1:06:43.992 ********* 
changed: [localhost] => {"changed": true, "rc": 0, "stderr": "", "stderr_lines": [], "stdout": "All Capsules are unassociated with any lifecycle environments. This is to avoid any syncing errors with your original Satellite and any interference with existing infrastructure. To reverse these changes, run the following commands, making sure to replace the credentials with your own.\nhammer -u admin -p changeme --csv capsule content add-lifecycle-environment --id 2 --environment-id 2\n", "stdout_lines": ["All Capsules are unassociated with any lifecycle environments. This is to avoid any syncing errors with your original Satellite and any interference with existing infrastructure. To reverse these changes, run the following commands, making sure to replace the credentials with your own.", "hammer -u admin -p changeme --csv capsule content add-lifecycle-environment --id 2 --environment-id 2"]}

stdout: All Capsules are unassociated with any lifecycle environments. This is to avoid any syncing errors with your original Satellite and any interference with existing infrastructure. To reverse these changes, run the following commands, making sure to replace the credentials with your own.
hammer -u admin -p changeme --csv capsule content add-lifecycle-environment --id 2 --environment-id 2