-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: unable to close, unable to unref last: unable to cleanup component version, while unref last: closing component version #1243
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The technical version used at the backend should not be usable as OCM version (see my comment above). I would strongly recommend to provide an error instead of introducing this ambiguity.
which has been replaced by META_SEPARATOR to create OCI compliant tag
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
With the warning in place, we should be good to go not to break anyone while at the same time preparing to forbid this alltogether like suggested. For now, we need to avoid completely breaking here.
…nt version, while unref last: closing component version (open-component-model#1243) #### What this PR does / why we need it When calling ocm-cli with oci-tag-version like `0.0.1-20250108132333.build-af79499` e.g. ```bash ocm get cv ocm-oci-test.int.repositories.cloud.sap//docker.io/recmo/docker-hello-tiny:0.0.1-20250108132333.build-af79499 ``` It fails during the [finalize step](https://github.com/open-component-model/ocm/blob/releases/v0.19/api/utils/refmgmt/refcloser.go#L196), when [doing an update](https://github.com/open-component-model/ocm/blob/releases/v0.19/api/ocm/extensions/repositories/genericocireg/componentversion.go#L171), where [another round of version comparison](https://github.com/open-component-model/ocm/blob/releases/v0.19/api/ocm/extensions/repositories/genericocireg/componentversion.go#L99) happens. #### Which issue(s) this PR fixes Fixes: open-component-model#1235 Related: open-component-model#355
What this PR does / why we need it
When calling ocm-cli with oci-tag-version like
0.0.1-20250108132333.build-af79499
e.g.It fails during the finalize step, when doing an update, where another round of version comparison happens.
Which issue(s) this PR fixes
Fixes: #1235
Related: #355