RFE The resulted ICSP should contain details for all operators not just for newly added

[stefanvasilic4]

Version

latest

What happened?

When adding a new operator or change maxVersion in imagesetconfiguration the resulting ICSP has only the new operator details.

What did you expect to happen?

I expect the new ICSP to contain details of existing operators plus the new operator's details, added to imagesetconfiguration

[pwcazenave]

This has caught me in the past - having only the details for the operators that were updated instead of all the requested operators means I have to manually merge my ICSP configs after mirroring.

[ChristianLoewel]

Same for me - I have set the --ignore-history parameter to always mirror the complete catalog to ensure that removed ICSP entries are not lost, although this unnecessarily increases the runtime of oc-mirror.

[sushil-telus]

Same here. Waiting on the feature to be implement.

I tried to make use of the --manifests-only option but it doesn't work if i am using the tool to copy images from image registry to image registry.

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[sushil-telus]

/remove-lifecycle stale

[mnorrsken]

I have the same problem, as we are using gitops to update the ICSPs in the cluster

[dadav]

We have the same problem. We run oc-mirror daily and therefore have dozens of results directory with manifests which same names (e.g. operator-0). So if I apply these manifests which only contain a subset of the needed informations, everything else is lost.

[sjbylo]

I have the same problem, as we are using gitops to update the ICSPs in the cluster

Same also.

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[sushil-telus]

Looks like this is implemented

Ref:

• https://issues.redhat.com/browse/RFE-3000
• https://docs.openshift.com/container-platform/4.16/release_notes/ocp-4-16-release-notes.html#ocp-4-16-openshift-cli_release-notes

Well I haven't tested it yet. (just in case anybody else is desperate for an update.)

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[openshift-bot]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale