Please use package versions when building rpms
Hi All, As some of you may have noticed, we have been having failures for some of the tests in master in the past 24 hours with the following yum error: https://pastebin.com/vqJCLgrP After some debugging we found that the issue is caused because the package which is failing had two different commits and no version set which caused two different packages with exactly the same name to be created. To solve this issue we would need the package to be re-build with a new version set. Here are the details on the package and how it failed. As you can see below we had two different commits creating two different packages by the same name: https://jenkins.ovirt.org/job/oVirt_ovirt-ansible-image- template_standard-on-ghpush/30/ which was triggered by push: 00f5ffd4-a06e-11e8-8fc7-fa3846728ab0 https://jenkins.ovirt.org/job/oVirt_ovirt-ansible-image- template_standard-on-ghpush/31/ which was triggered by push: 3dfc5996-a09b-11e8-856c-ec86908871c4 checking the packages that exist in the 4.2 and master tested repos I can see that we have the same exact name for two different packages: 4.2: ovirt-ansible-image-template-1.1.7-1.el7.noarch.rpm: Header SHA1 digest: OK (0033d83c3d8b6b0506767de3a4e44ffd64b2605c) MD5 digest: OK (2b6e87e53a51175aeac61662561c0e20) master: ovirt-ansible-image-template-1.1.7-1.el7.noarch.rpm: Header SHA1 digest: OK (597577a11775a7fc21207f3e76fe4df8a5030912) MD5 digest: OK (74bafadf2afae5f7797a90c982ad2767) This would cause yum to fail because we cannot have the same package name with different checksums. If anyone needs help in setting up versioning please contact myself or anyone from the CI team and we would be happy to assist. Thanks, Dafna
This script (that Barak wrote) does this check. Help yourself. https://gerrit.ovirt.org/gitweb?p=ovirt-engine-nodejs-modules.git;a=blob;f=a... Best wishes, Greg On Thu, Aug 16, 2018 at 3:55 AM Dafna Ron <dron@redhat.com> wrote:
Hi All,
As some of you may have noticed, we have been having failures for some of the tests in master in the past 24 hours with the following yum error: https://pastebin.com/vqJCLgrP
After some debugging we found that the issue is caused because the package which is failing had two different commits and no version set which caused two different packages with exactly the same name to be created.
To solve this issue we would need the package to be re-build with a new version set.
Here are the details on the package and how it failed. As you can see below we had two different commits creating two different packages by the same name:
https://jenkins.ovirt.org/job/oVirt_ovirt-ansible-image-template_standard-on... which was triggered by push: 00f5ffd4-a06e-11e8-8fc7-fa3846728ab0
https://jenkins.ovirt.org/job/oVirt_ovirt-ansible-image-template_standard-on... which was triggered by push: 3dfc5996-a09b-11e8-856c-ec86908871c4
checking the packages that exist in the 4.2 and master tested repos I can see that we have the same exact name for two different packages:
4.2:
ovirt-ansible-image-template-1.1.7-1.el7.noarch.rpm: Header SHA1 digest: OK (0033d83c3d8b6b0506767de3a4e44ffd64b2605c) MD5 digest: OK (2b6e87e53a51175aeac61662561c0e20)
master:
ovirt-ansible-image-template-1.1.7-1.el7.noarch.rpm: Header SHA1 digest: OK (597577a11775a7fc21207f3e76fe4df8a5030912) MD5 digest: OK (74bafadf2afae5f7797a90c982ad2767)
This would cause yum to fail because we cannot have the same package name with different checksums.
If anyone needs help in setting up versioning please contact myself or anyone from the CI team and we would be happy to assist.
Thanks, Dafna
_______________________________________________ Devel mailing list -- devel@ovirt.org To unsubscribe send an email to devel-leave@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/devel@ovirt.org/message/7PLZTACS2PBAXN...
-- GREG SHEREMETA SENIOR SOFTWARE ENGINEER - TEAM LEAD - RHV UX Red Hat NA <https://www.redhat.com/> gshereme@redhat.com IRC: gshereme <https://red.ht/sig>
On Thu, Aug 16, 2018 at 1:18 PM, Greg Sheremeta <gshereme@redhat.com> wrote:
This script (that Barak wrote) does this check. Help yourself. https://gerrit.ovirt.org/gitweb?p=ovirt-engine-nodejs- modules.git;a=blob;f=automation/check-version-release.sh
Best wishes, Greg
On Thu, Aug 16, 2018 at 3:55 AM Dafna Ron <dron@redhat.com> wrote:
Hi All,
As some of you may have noticed, we have been having failures for some of the tests in master in the past 24 hours with the following yum error: https://pastebin.com/vqJCLgrP
After some debugging we found that the issue is caused because the package which is failing had two different commits and no version set which caused two different packages with exactly the same name to be created.
To solve this issue we would need the package to be re-build with a new version set.
Here are the details on the package and how it failed. As you can see below we had two different commits creating two different packages by the same name:
https://jenkins.ovirt.org/job/oVirt_ovirt-ansible-image- template_standard-on-ghpush/30/ which was triggered by push: 00f5ffd4-a06e-11e8-8fc7-fa3846728ab0
https://jenkins.ovirt.org/job/oVirt_ovirt-ansible-image- template_standard-on-ghpush/31/ which was triggered by push: 3dfc5996-a09b-11e8-856c-ec86908871c4
checking the packages that exist in the 4.2 and master tested repos I can see that we have the same exact name for two different packages:
4.2:
ovirt-ansible-image-template-1.1.7-1.el7.noarch.rpm: Header SHA1 digest: OK (0033d83c3d8b6b0506767de3a4e44ffd64b2605c) MD5 digest: OK (2b6e87e53a51175aeac61662561c0e20)
master:
ovirt-ansible-image-template-1.1.7-1.el7.noarch.rpm: Header SHA1 digest: OK (597577a11775a7fc21207f3e76fe4df8a5030912) MD5 digest: OK (74bafadf2afae5f7797a90c982ad2767)
Ondro, could you please investigate what happened?
This would cause yum to fail because we cannot have the same package name
with different checksums.
If anyone needs help in setting up versioning please contact myself or anyone from the CI team and we would be happy to assist.
Thanks, Dafna
_______________________________________________ Devel mailing list -- devel@ovirt.org To unsubscribe send an email to devel-leave@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community- guidelines/ List Archives: https://lists.ovirt.org/archives/list/devel@ovirt.org/ message/7PLZTACS2PBAXNKDYZH6LZQK44XBF4VE/
--
GREG SHEREMETA
SENIOR SOFTWARE ENGINEER - TEAM LEAD - RHV UX
Red Hat NA
gshereme@redhat.com IRC: gshereme <https://red.ht/sig>
_______________________________________________ Devel mailing list -- devel@ovirt.org To unsubscribe send an email to devel-leave@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community- guidelines/ List Archives: https://lists.ovirt.org/archives/list/devel@ovirt.org/ message/AJG33QKRU25BXQKNMTE5W6NYGF4E3YVK/
-- Martin Perina Associate Manager, Software Engineering Red Hat Czech s.r.o.
participants (3)
-
Dafna Ron -
Greg Sheremeta -
Martin Perina