Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Re: [ovirt-devel] mom install error on fc29

Description

On Thu, Jun 20, 2019 at 5:35 PM Miguel Duarte de Mora Barroso <
mdbarroso@redhat.com> wrote:

> Hi,
>
> I'm seeing the following error when I try to install
> ovirt-provider-ovn-driver (which requires vdsm):
>
> [MIRROR] mom-0.5.12-0.0.master.fc29.noarch.rpm: Interrupted by header
> callback: Server reports Content-Length: 340 but expected size is:
> 133356
> 17:13:50 [FAILED] mom-0.5.12-0.0.master.fc29.noarch.rpm: No more
> mirrors to try - All mirrors were already tried without success
> 17:13:50 Error: Error downloading packages:
> 17:13:50 Cannot download
> noarch/mom-0.5.12-0.0.master.fc29.noarch.rpm: All mirrors were tried
>
> Any clue ?.. it can be seen in [0].
>
> Thanks in advance,
> Miguel
>
> [0] -
> https://jenkins.ovirt.org/job/ovirt-provider-ovn_standard-check-patch/2309/console
> _______________________________________________
> 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/OLLWGI4NKMZD2TDCYLMIK3KXXET4RP55/
>

Activity

Show:

Sandro Bonazzola July 23, 2019 at 6:10 AM

Sandro Bonazzola July 23, 2019 at 6:09 AM

Looking into this

Miguel Duarte de Mora Barroso July 14, 2019 at 9:18 AM

Thanks Barak/Evgheni; I should have updated the ticket owner to someone in mom or Sandro instead of adding fuel to the fire.

 

Barak Korren July 14, 2019 at 7:11 AM

This root cause for this is the mom is being rebuilt without bumping the package version, you can see this by looking at the package versions throughout the build history here:

https://jenkins.ovirt.org/job/mom_standard-on-merge/

This simply confuses yum/dnf, because when it downloads a package it would generally skip downloading when if finds a package file with the same version in the local cache but would still compare its checksum against the one in the repo metadata. In this case since we have a newer build with the same version, yum/dnf would find the checksum to be different and you declare the download to have failed.

This problem will generally "solve itself" over time as local caches expire, but the long term solution is to fix the mom build process so that it will issue a new version number on each merged commit using something like git describe.

For an immediate short-term solution, the mom maser branch should be patched to bump the version number. merging that patch would cause a new build to be done.

Since I don't know who the current mom maintainers are, I'm going to assing this to . Sandro - please reassign to the mom maintainers.

Thanks,
Barak.

Miguel Duarte de Mora Barroso July 12, 2019 at 4:21 PM

Fixed

Details

Assignee

Reporter

Components

Priority

Created July 1, 2019 at 12:51 PM
Updated August 29, 2019 at 2:12 PM
Resolved July 23, 2019 at 6:10 AM