Description of problem: 'dnf makecache' doesn't report bogus repository metadata, it either * passes without any error message; this happens for bogus <size>, <open-size> and <open-checksum> with proper length * reports 'Failed to synchronize cache for repo ... disabling'; this happens for bogus <checksum> and <location> * fails with traceback; this happens for bogus <open-checksum> with improper length (even for other.xml that is not cached) Note: yum reports bogus metadata (for .sqlite files that it caches) see also /CoreOS/yum/Sanity/yum-metadata-errors Version-Release number of selected component (if applicable): dnf-2.7.5-2.fc27.noarch How reproducible: always Steps to Reproduce: 1. create an empty dir, run 'createrepo_c .' in it, create relevant /etc/yum.repos.d/*.repo file pointing to that repo 2. ./repodata/repomd.xml: sequentially do changes described above (i.e. change <size>, <open-checksum> etc.) for *.xml related data 3. after every change run 'dnf clean metadata; dnf makecache' 4. undo the change, continue with next change (step 2.) Actual results: for bogus <size>: # dnf makecache testrepo 251 kB/s | 257 B 00:00 Last metadata expiration check: 0:00:00 ago on Thu 15 Feb 2018 04:58:09 AM EST. Metadata cache created. for bogus <checksum>: # dnf makecache Failed to synchronize cache for repo 'testrepo', disabling.| 0 B --:-- ETA Metadata cache created. for bogus <open-checksum> with improper length: # dnf makecache testrepo 251 kB/s | 257 B 00:00 Traceback (most recent call last): File "/usr/bin/dnf", line 58, in <module> main.user_main(sys.argv[1:], exit_code=True) File "/usr/lib/python3.6/site-packages/dnf/cli/main.py", line 179, in user_main errcode = main(args) File "/usr/lib/python3.6/site-packages/dnf/cli/main.py", line 64, in main return _main(base, args, cli_class, option_parser_class) File "/usr/lib/python3.6/site-packages/dnf/cli/main.py", line 99, in _main return cli_run(cli, base) File "/usr/lib/python3.6/site-packages/dnf/cli/main.py", line 115, in cli_run cli.run() File "/usr/lib/python3.6/site-packages/dnf/cli/cli.py", line 1014, in run return self.command.run() File "/usr/lib/python3.6/site-packages/dnf/cli/commands/makecache.py", line 55, in run return self.base.update_cache(self.opts.timer is not None) File "/usr/lib/python3.6/site-packages/dnf/base.py", line 324, in update_cache self.fill_sack(load_system_repo=False, load_available_repos=True) # performs the md sync File "/usr/lib/python3.6/site-packages/dnf/base.py", line 353, in fill_sack self._add_repo_to_sack(r) File "/usr/lib/python3.6/site-packages/dnf/base.py", line 135, in _add_repo_to_sack load_updateinfo=True) _hawkey.Exception: repo_add_repomdxml/rpmmd() has failed. Expected results: metadata mismatch reported for all cases, no traceback for <open-checksum>
*** This bug has been marked as a duplicate of bug 1544359 ***
This message is a reminder that Fedora 27 is nearing its end of life. On 2018-Nov-30 Fedora will stop maintaining and issuing updates for Fedora 27. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '27'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 27 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
This bug appears to have been reported against 'rawhide' during the Fedora 30 development cycle. Changing version to '30.
This message is a reminder that Fedora 30 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 30 on 2020-05-26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '30'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 30 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
This bug appears to have been reported against 'rawhide' during the Fedora 33 development cycle. Changing version to 33.
This message is a reminder that Fedora 33 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '33'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 33 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 33 changed to end-of-life (EOL) status on 2021-11-30. Fedora 33 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.