GA: Eject/Inject CD-ROM Support

[guyoron1]

Source: CNV-68916 | Epic | Priority: Major | Component: Storage Platform | Status: In Progress

Goal

GA CD-ROM eject/inject via declarative hotplug

User Stories

• As a VM owner I want to change the CD-ROM media without needing to restart my VM

Non-Requirements

• List of things not included in this epic, to alleviate any doubt raised during the grooming process.

Notes

• Feature will be GA but will remain opt-in at least for 4.22
• Only one partner was using ephemeral hotplug. On track.

Acceptance Criteria

• De-quarantine Declarative Hotplug tests (tier1 downstream)
• Automated tests for CD-ROM eject/inject
• Test plans in Polarion
• Upstream design and documentation
• Downstream documentation merged
• Tier-2 comprehensive UI testing for CD-ROM media change functionality
• Update documentation to reflect CD-ROM eject/inject as GA feature but still must be enabled
• Develop customer communication and migration plan for ephemeral volume removal
• CNV QE DevOps Requirement/Enablement

Child Issues

Key	Summary	Status
CNV-67296	De-quarantine Declarative Hotplug tests - tier1 downstream	Closed
CNV-68922	Automated tests	Closed
CNV-68921	Test plans in polarion	Closed
CNV-68918	Upstream design	Closed
CNV-68919	Upstream documentation	Closed
CNV-68923	Downstream documentation merged	Closed
CNV-68920	Upgrade consideration	Closed
CNV-68924	CNV QE DevOps Requirement/Enablement	Closed
CNV-78861	Update documentation to reflect CD-ROM eject/inject as GA feature	In Progress
CNV-78862	Develop customer communication and migration plan for ephemeral volume removal	Closed
CNV-78863	Tier-2 comprehensive UI testing for CD-ROM media change functionality	Closed
CNV-81708	Report on customer usage of ephemeral hotplug disks	Closed

---

Sourced from Jira CNV-68916

---

Re-triggered after mint enrollment.

[fullsend-ai-triage]

🤖 Finished Triage · ✅ Success · Started 5:44 AM UTC · Completed 5:46 AM UTC
Commit: b906834 · View workflow run →

[fullsend-ai-triage]

Thanks for filing this issue. It appears to be a Jira epic (CNV-68916) tracking CD-ROM eject/inject GA support for a virtualization platform, synced into this repository after mint enrollment.

However, this repository (fullsend) is a platform for autonomous agentic development for GitHub-hosted organizations — it doesn't contain any virtualization or CD-ROM-related code. The issue content doesn't map to any component or feature in this codebase.

Could you clarify what action you expect to be taken on this issue within this repository? Specifically:

• Was this issue synced here intentionally, or is it a test of the fullsend issue ingestion pipeline?
• If intentional, what work in this codebase does this epic correspond to?

Without this context, it's not possible to determine whether this issue is actionable here.