Replace Molecule Proxmox component placeholder assertions with real tests
User Story:
As a developer, I want real test assertions for Proxmox component so that Proxmox operator functionality is validated
Problem Statement:
Proxmox component Molecule tests have placeholder assertions that don't validate VM operations, network configuration, or Ceph storage integration.
Acceptance Criteria:
-
Proxmox CRD creation validated with correct spec -
VM creation and deletion operations verified -
Network bridge configuration tested (vmbr0, vmbr1) -
Ceph storage pool integration validated -
Resource allocation limits enforced. -
Template cloning operations verified -
Idempotency verified (no changes on second run)
Implementation Details:
Files to Modify:
-
molecule/default/tasks/proxmox_test.yml
- Replace placeholder assertions with real tests -
molecule/default/vars/proxmox_test_vars.yml
- Test data for Proxmox scenarios
Dependencies:
- proxmoxer Python library for API testing
- kubernetes Python client.
Additional Notes:
Test should verify Proxmox API connectivity, validate VM lifecycle operations, check network interface configurations (PELI, QSFP templates), and ensure proper resource cleanup.
Edited by Lam Do