anthony.wen/cds-ai
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Remove relocated REIP discovery test plan

Browse Source
This commit is contained in:
Anthony Wen
2026-06-29 14:53:17 -04:00
parent 9d8f91dbe3
commit 744b28affe
1 changed files with 0 additions and 185 deletions
Download Patch File Download Diff File Expand all files Collapse all files
tests/reip-discovery-test.md
-185
View File
@@ -1,185 +0,0 @@
# REIP Discovery Test
## Purpose
Validate CMC REIP discovery behavior across the ATVM inventory by installing CMC on one VM at a time, collecting REIP and OS network-discovery output, recording the results, uninstalling CMC, and powering the VM off before moving to the next VM.
## Scope
- Inventory source: `/home/cirrus/cds/atvm/inventory/vm-inventory.md`
- Results file: `/home/cirrus/cds/tests/reip-discovery-test-results.md`
- CDC project: `Skidamarink`
- Include Linux and Windows ATVM entries.
- Skip only inventory rows whose Notes column contains `BLACKLISTED`.
- Run one VM from start to cleanup completion before starting the next VM.
- Do not clone, delete, unregister, snapshot, or otherwise modify ATVM VM inventory.
## Credentials And Tools
- Source credentials from `/home/cirrus/cds/.env.credentials.local` before vCenter, SSH, Windows remote shell, or CMC actions.
- Do not print or store secret values in the test plan or results.
- Required credential variables:
- `VCENTER_HOST`, `VCENTER_USER`, `VCENTER_PASSWORD`
- `ATVM_TARGET_USER`, `ATVM_TARGET_PASSWORD`
- `ATVM_WINDOWS_TARGET_USER`, `ATVM_WINDOWS_TARGET_PASSWORD`
- `CMC_GCSTAGE_REGISTRATION_CODE`
- `CIRRUS_API_TOKEN`
- Use `govc` for vCenter power state and VMware Tools IP checks.
- Use the Cirrus Data Cloud CLI/skill for CMC install verification, host lookup, and project checks.
- Use direct SSH where possible. For Windows, prefer SSH into PowerShell. If SSH is unavailable but VMware guest operations work, record the fallback method.
## CMC Commands
### Linux Install
```bash
curl https://get.cirrusdata.cloud/install-cmc | bash -s -- -rgc "$CMC_GCSTAGE_REGISTRATION_CODE" -gce portal.gcstage.cloud.nonprod.cirrusdata.com:443 -pkg-mode PRE_RELEASE
```
### Linux Uninstall
```bash
curl https://get.cirrusdata.cloud/install-cmc | bash -s -- -uninstall
```
### Windows Install
```powershell
iex "& { $(irm https://get.cirrusdata.cloud/install-cmc-win) } -rgc $env:CMC_GCSTAGE_REGISTRATION_CODE -gce portal.gcstage.cloud.nonprod.cirrusdata.com:443 -pkg-mode PRE_RELEASE"
```
### Windows Uninstall
```powershell
iex "& { $(irm https://get.cirrusdata.cloud/install-cmc-win) } -uninstall"
```
## Per-VM Execution Checklist
Run this checklist fully for one VM before starting the next VM.
- [ ] 1. Source `/home/cirrus/cds/.env.credentials.local` and verify required variables are present without printing values.
- [ ] 2. Read the next eligible row from `/home/cirrus/cds/atvm/inventory/vm-inventory.md`; skip rows with `BLACKLISTED` in Notes.
- [ ] 3. Record the inventory values for OS, vCenter VM name, inventory kernel/build, and Notes.
- [ ] 4. Confirm from vCenter that the previous VM processed by this test, if any, is `poweredOff`.
- [ ] 5. Confirm the target VM exists in vCenter by exact inventory VM name.
- [ ] 6. Power on the target VM from vCenter.
- [ ] 7. Wait for VMware Tools to report a live guest IP address.
- [ ] 8. Connect to the guest:
- Linux: SSH with `ATVM_TARGET_USER` / `ATVM_TARGET_PASSWORD`.
- Windows: SSH or PowerShell with `ATVM_WINDOWS_TARGET_USER` / `ATVM_WINDOWS_TARGET_PASSWORD`.
- [ ] 9. Record hostname, OS version, kernel version or Windows build, VMware Tools IP, and connection method.
- [ ] 10. Uninstall any existing CMC using the OS-appropriate uninstall command.
- [ ] 11. Confirm CMC is not installed or no longer running:
- Linux: check `galaxy-migrate`, `mtdi-daemon`, `mtdi-driver`, and package/service presence where applicable.
- Windows: check CMC service/process/program presence where applicable.
- [ ] 12. Install CMC into `Skidamarink` using the OS-appropriate install command.
- [ ] 13. Confirm CMC is installed locally and the host appears connected in `Skidamarink`.
- [ ] 14. Run the REIP discovery commands.
- [ ] 15. Run OS network-discovery commands.
- [ ] 16. Append a complete result section for this VM to `/home/cirrus/cds/tests/reip-discovery-test-results.md`.
- [ ] 17. Uninstall CMC again using the OS-appropriate uninstall command.
- [ ] 18. Confirm CMC is uninstalled locally.
- [ ] 19. Power off the VM from vCenter.
- [ ] 20. Confirm vCenter reports the VM as `poweredOff`.
- [ ] 21. Only after step 20 passes, proceed to the next eligible inventory VM.
## REIP And Network Commands
### Linux
Collect full output from:
```bash
galaxy-migrate support reip which
galaxy-migrate support reip discover
hostname
cat /etc/os-release
uname -a
ip addr show
ip route
nmcli device show
ifconfig -a
```
If a command is unavailable, record the command, exit code, and error output. Continue with the remaining commands.
Also collect relevant network configuration files when present:
```bash
find /etc/netplan -maxdepth 1 -type f -print -exec sed -n '1,200p' {} \;
find /etc/sysconfig/network-scripts -maxdepth 1 -type f -name 'ifcfg-*' -print -exec sed -n '1,200p' {} \;
find /etc/NetworkManager/system-connections -maxdepth 1 -type f -print -exec sed -n '1,200p' {} \;
```
### Windows
Collect full output from PowerShell:
```powershell
galaxy-migrate.exe support reip which
galaxy-migrate.exe support reip discover
hostname
Get-ComputerInfo | Select-Object OsName, OsVersion, OsBuildNumber, WindowsVersion
Get-NetAdapter
Get-NetIPConfiguration
ipconfig /all
route print
```
If `galaxy-migrate.exe` is not in `PATH`, locate it under the CMC install directory and run the command with the full executable path. Record the path used.
## Results Format
Append one section per VM to `/home/cirrus/cds/tests/reip-discovery-test-results.md`.
````md
## <VM name> - <PASS|FAIL|PARTIAL>
- Test start time:
- Test end time:
- Duration:
- Inventory OS:
- Inventory kernel/build:
- Inventory notes:
- vCenter VM name:
- VMware Tools IP:
- Connection method:
- Hostname:
- Runtime OS version:
- Runtime kernel/build:
- CMC uninstall before test: <PASS|FAIL|SKIPPED> - notes
- CMC install: <PASS|FAIL> - notes
- CDC Skidamarink connected host confirmation: <PASS|FAIL> - notes
- REIP discovery: <PASS|FAIL> - notes
- Network discovery: <PASS|FAIL> - notes
- CMC uninstall cleanup: <PASS|FAIL> - notes
- vCenter power-off cleanup: <PASS|FAIL> - notes
### REIP Command Output
```text
<full command transcript>
```
### Network Discovery Output
```text
<full command transcript>
```
### Final Notes
- <concise notes, blockers, fallbacks, or unexpected behavior>
````
## Failure Handling
- A per-VM command failure does not stop the full sweep unless cleanup cannot be made safe.
- If VMware Tools never reports an IP, record `FAIL`, power off the VM, confirm `poweredOff`, then continue.
- If guest login fails, record `FAIL`, power off the VM, confirm `poweredOff`, then continue.
- If CMC install succeeds but REIP discovery fails, still uninstall CMC, power off the VM, confirm `poweredOff`, then continue.
- If CMC uninstall cleanup fails, record `FAIL` or `PARTIAL`, then attempt to power off the VM.
- If vCenter power-off confirmation fails, stop the sweep immediately and report a blocker; do not start another VM while the current VM may still be powered on.
- If any VM is not found by exact inventory name, record `FAIL` and continue to the next inventory row.
## Red Hat Subscription Preflight
Apply this only to actual Red Hat Enterprise Linux inventory rows when manually running this test. Do not apply to CentOS, Oracle Linux, Rocky Linux, AlmaLinux, Fedora, Debian, Ubuntu, SUSE, or Windows unless explicitly directed.
Before CMC install on an actual Red Hat VM, run:
```bash
subscription-manager remove --all
subscription-manager unregister
subscription-manager clean
subscription-manager register --username "$REDHAT_SUBSCRIPTION_USER" --password "$REDHAT_SUBSCRIPTION_PASSWORD"
```
Record whether this preflight was `PASS`, `FAIL`, or `SKIPPED`.
## Completion Criteria
- Every eligible inventory VM was processed or recorded as skipped/fail with a reason.
- No processed VM remains powered on at the end of the run.
- CMC is uninstalled from every processed VM unless cleanup failure is explicitly recorded.
- `/home/cirrus/cds/tests/reip-discovery-test-results.md` contains one appended result section per processed VM.