Loading...

XML

Word

Printable

Type: Bug
Resolution: Not a Bug
Priority: Normal
Fix Version/s: None
Affects Version/s: 4.20.0
Component/s: oc-mirror
Labels:
- naps-hackathon
- v2

Activity Type:
Quality / Stability / Reliability
Blocked:
False
Blocked Reason:

Hide

None

Show
None
Story Points:
None
Severity:
None
Regression:
None

Target Backport Versions:
None
Target Version:
None
Release Blocker:
None
Sprint:
None

SFDC Cases Counter:
SFDC Cases Open:
SFDC Cases Links:

PX Impact Score:

Release Note Status:
None
Release Note Type:
None
Release Note Text:
None

Escape Reason:
None
Escape Impact:
None
Corrective Measures:
None
SDLC stage when should've been found:
None

Description of problem:

    When oc-mirror creates the delete-imageset-config.yaml and delete-image.yaml they are not unique to that run.  A subsequent run of oc-mirror to generate a delete plan then overwrites the existing files as a result.  A user has no way to recall what images and operators were deleted in prior runs if they performed consecutive deletes.

Version-Release number of selected component (if applicable):

How reproducible:

    100%

Steps to Reproduce:

    1. Run oc-mirror to generate deletion plan with an imageset config
    2. Observe delete-images.yaml and delete-imageset-config.yaml
    3. Run oc-mirror to generate a new deletion plan with a different imageset config

Actual results:

    delete-images.yaml and delete-imageset-config.yaml have been overwritten with the latest deletion plan

Expected results:

A unique set of yaml files are generated (timestamped?) than allows for some sort of history of oc-mirrors delete operatations

Additional info:

Assignee:: Luigi Mario Zuccarelli

Reporter:: Keith Jackson

Need Info From:: None

Contributors:: None

QA Contact:: Nidan Gavali

Doc Contact:: None

Votes:: 0 Vote for this issue

Watchers:: 2 Start watching this issue

Created:: 2025/08/27 4:38 PM

Updated:: 2025/08/27 5:51 PM

Resolved:: 2025/08/27 5:51 PM