-
Notifications
You must be signed in to change notification settings - Fork 124
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
Module's NSVCA cannot be used as uniqueness constraint #3241
Comments
ipanova
added a commit
to ipanova/pulp_rpm
that referenced
this issue
Sep 4, 2023
closes pulp#3241 It no longer holds true to rely on NSVCA module's uniqueness, add the hash of the document snippet to it.
ipanova
added a commit
to ipanova/pulp_rpm
that referenced
this issue
Sep 4, 2023
closes pulp#3241 It no longer holds true to rely on NSVCA module's uniqueness, add the hash of the document snippet to it.
ipanova
added a commit
to ipanova/pulp_rpm
that referenced
this issue
Sep 4, 2023
closes pulp#3241 It no longer holds true to rely on NSVCA module's uniqueness, add the hash of the document snippet to it.
ipanova
added a commit
to ipanova/pulp_rpm
that referenced
this issue
Sep 6, 2023
closes pulp#3241 It no longer holds true to rely on NSVCA module's uniqueness, add the hash of the document snippet to it.
dralley
pushed a commit
that referenced
this issue
Sep 8, 2023
closes #3241 It no longer holds true to rely on NSVCA module's uniqueness, add the hash of the document snippet to it.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Version
all
Describe the bug
Description of problem:
If synchronizing Oracle Linux 9 AppStream (after RHEL9 AppStream synced, or viceversa) Pulp will show just one
ruby
module based on what todays' uniqueness allows.RHEL9 released this snippet for ruby 3.1 module stream:
document: modulemd
version: 2
data:
name: ruby
stream: "3.1"
version: 9010020220623124214
context: 9
static_context: true
arch: x86_64
..
artifacts:
rpms:
- ruby-0:3.1.2-141.module+el9.1.0+15737+76195479.i686
- ruby-0:3.1.2-141.module+el9.1.0+15737+76195479.src
- ruby-0:3.1.2-141.module+el9.1.0+15737+76195479.x86_64
- ruby-bundled-gems-0:3.1.2-141.module+el9.1.0+15737+76195479.i686
..
Few months later on, Oracle Linux 9 AppStream was released, with ruby 3.1 module stream:
document: modulemd
version: 2
data:
name: ruby
stream: "3.1"
version: 9010020220623124214
context: 9
static_context: true
arch: x86_64
..
artifacts:
rpms:
- ruby-0:3.1.2-141.module+el9.1.0+20815+286161bd.i686
- ruby-0:3.1.2-141.module+el9.1.0+20815+286161bd.x86_64
- ruby-bundled-gems-0:3.1.2-141.module+el9.1.0+20815+286161bd.i686
To Reproduce
Sync these 2 repos.
Expected behavior
Observe that pulp has just one ruby module with unique NSVCA instead of 2 modules with same NSVCA but different snippet content.
Additional context
https://bugzilla.redhat.com/show_bug.cgi?id=2232500
The text was updated successfully, but these errors were encountered: