vagrant-projects: Metadata file does not match checksum - 12.2c, 18c, ol7 etc

Hi, im trying to setup a 18c database, but no matter what setup i try and run i get the following. In this example i even removed and added the repo as part of the install.sh:

    oracle-18c-vagrant: INSTALLER: Started up
    oracle-18c-vagrant: --2020-03-31 10:18:30--  https://yum.oracle.com/public-yum-ol7.repo
    oracle-18c-vagrant: Resolving yum.oracle.com (yum.oracle.com)...
    oracle-18c-vagrant: 104.78.177.163
    oracle-18c-vagrant: Connecting to yum.oracle.com (yum.oracle.com)|104.78.177.163|:443...
    oracle-18c-vagrant: connected.
    oracle-18c-vagrant: HTTP request sent, awaiting response...
    oracle-18c-vagrant: 200 OK
    oracle-18c-vagrant: Length:
    oracle-18c-vagrant: 16402
    oracle-18c-vagrant:  (16K)
    oracle-18c-vagrant:  [text/plain]
    oracle-18c-vagrant: Saving to: ‘public-yum-ol7.repo’
    oracle-18c-vagrant:
    oracle-18c-vagrant:      0K .......... ......                                     100% 41.1M=0s
    oracle-18c-vagrant:
    oracle-18c-vagrant: 2020-03-31 10:18:31 (41.1 MB/s) - ‘public-yum-ol7.repo’ saved [16402/16402]
    oracle-18c-vagrant: Repository ol7_latest is listed more than once in the configuration
    oracle-18c-vagrant: Repository ol7_u0_base is listed more than once in the configuration
    oracle-18c-vagrant: Repository ol7_u1_base is listed more than once in the configuration
    oracle-18c-vagrant: Repository ol7_u2_base is listed more than once in the configuration
    oracle-18c-vagrant: Repository ol7_u3_base is listed more than once in the configuration
    oracle-18c-vagrant: Repository ol7_u4_base is listed more than once in the configuration
    oracle-18c-vagrant: Repository ol7_u5_base is listed more than once in the configuration
    oracle-18c-vagrant: Repository ol7_u6_base is listed more than once in the configuration
    oracle-18c-vagrant: Repository ol7_u7_base is listed more than once in the configuration
    oracle-18c-vagrant: Repository ol7_security_validation is listed more than once in the configuration
    oracle-18c-vagrant: Repository ol7_optional_latest is listed more than once in the configuration
    oracle-18c-vagrant: Repository ol7_addons is listed more than once in the configuration
    oracle-18c-vagrant: Repository ol7_software_collections is listed more than once in the configuration
    oracle-18c-vagrant: Repository ol7_MODRHCK is listed more than once in the configuration
    oracle-18c-vagrant: Repository ol7_developer is listed more than once in the configuration
    oracle-18c-vagrant: Repository ol7_developer_EPEL is listed more than once in the configuration
    oracle-18c-vagrant: Repository ol7_developer_UEKR5 is listed more than once in the configuration
    oracle-18c-vagrant: Repository ol7_developer_kvm_utils is listed more than once in the configuration
    oracle-18c-vagrant: Repository ol7_latest_archive is listed more than once in the configuration
    oracle-18c-vagrant: Repository ol7_optional_archive is listed more than once in the configuration
    oracle-18c-vagrant: Repository ol7_UEKR5 is listed more than once in the configuration
    oracle-18c-vagrant: Repository ol7_UEKR4 is listed more than once in the configuration
    oracle-18c-vagrant: Repository ol7_UEKR3 is listed more than once in the configuration
    oracle-18c-vagrant: Repository ol7_UEKR3_OFED20 is listed more than once in the configuration
    oracle-18c-vagrant: Repository ol7_UEKR5_RDMA is listed more than once in the configuration
    oracle-18c-vagrant: Repository ol7_UEKR4_OFED is listed more than once in the configuration
    oracle-18c-vagrant: Repository ol7_UEKR4_archive is listed more than once in the configuration
    oracle-18c-vagrant: Repository ol7_UEKR5_archive is listed more than once in the configuration
    oracle-18c-vagrant: Repository ol7_kvm_utils is listed more than once in the configuration
    oracle-18c-vagrant: http://yum.oracle.com/repo/OracleLinux/OL7/SoftwareCollections/x86_64/repodata/f01d11894ee11aa626df6db24c136cdd9665e12b-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
    oracle-18c-vagrant: Trying other mirror.
    oracle-18c-vagrant: https://yum.oracle.com/repo/OracleLinux/OL7/UEKR5/x86_64/repodata/f98315a4653f3f28a0e137c02112c28f3ff8253f-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
    oracle-18c-vagrant: Trying other mirror.
    oracle-18c-vagrant: http://yum.oracle.com/repo/OracleLinux/OL7/SoftwareCollections/x86_64/repodata/f01d11894ee11aa626df6db24c136cdd9665e12b-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
    oracle-18c-vagrant: Trying other mirror.
    oracle-18c-vagrant: https://yum.oracle.com/repo/OracleLinux/OL7/UEKR5/x86_64/repodata/f98315a4653f3f28a0e137c02112c28f3ff8253f-primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum
    oracle-18c-vagrant: Trying other mirror.
    oracle-18c-vagrant:
    oracle-18c-vagrant:
    oracle-18c-vagrant:  One of the configured repositories failed (Unknown),
    oracle-18c-vagrant:  and yum doesn't have enough cached data to continue. At this point the only
    oracle-18c-vagrant:  safe thing yum can do is fail. There are a few ways to work "fix" this:
    oracle-18c-vagrant:
    oracle-18c-vagrant:      1. Contact the upstream for the repository and get them to fix the problem.
    oracle-18c-vagrant:
    oracle-18c-vagrant:      2. Reconfigure the baseurl/etc. for the repository, to point to a working
    oracle-18c-vagrant:         upstream. This is most often useful if you are using a newer
    oracle-18c-vagrant:         distribution release than is supported by the repository (and the
    oracle-18c-vagrant:         packages for the previous distribution release still work).
    oracle-18c-vagrant:
    oracle-18c-vagrant:      3. Run the command with the repository temporarily disabled
    oracle-18c-vagrant:             yum --disablerepo=<repoid> ...
    oracle-18c-vagrant:
    oracle-18c-vagrant:      4. Disable the repository permanently, so yum won't use it by default. Yum
    oracle-18c-vagrant:         will then just ignore the repository until you permanently enable it
    oracle-18c-vagrant:         again or use --enablerepo for temporary usage:
    oracle-18c-vagrant:
    oracle-18c-vagrant:             yum-config-manager --disable <repoid>                                                   oracle-18c-vagrant:         or                                                                                          oracle-18c-vagrant:             subscription-manager repos --disable=<repoid>                                           oracle-18c-vagrant:                                                                                                     oracle-18c-vagrant:      5. Configure the failing repository to be skipped, if it is unavailable.
    oracle-18c-vagrant:         Note that yum will try to contact the repo. when it runs most commands,
    oracle-18c-vagrant:         so will have to try and fail each time (and thus. yum will be be much
    oracle-18c-vagrant:         slower). If it is a very temporary problem though, this is often a nice
    oracle-18c-vagrant:         compromise:
    oracle-18c-vagrant:
    oracle-18c-vagrant:             yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
    oracle-18c-vagrant:
    oracle-18c-vagrant: ol7_UEKR5: Check uncompressed DB failed
The SSH command responded with a non-zero exit status. Vagrant
assumes that this means the command failed. The output for this command
should be in the log above. Please read the output to determine what
went wrong.

Same error is appearing if i do a 12.2.0.1 database, and also if i just do an ol7 install.

OL8 has the following ol8-vagrant: Failed to download metadata for repo 'ol8_baseos_latest' ol8-vagrant: Error: Failed to download metadata for repo 'ol8_baseos_latest'

This has been happening yesterday (30th March) and today (31st March).

About this issue

Original URL
State: closed
Created 4 years ago
Comments: 52 (28 by maintainers)

Most upvoted comments

Just to update - not sure what the cause of this is - I reverted back to version 6 of Oracle VM on Saturday - and undid all the changes from this. The vm was built successfully. I upgraded back to 6.1 and kept the original build - again the vm’s were built successfully…

I have also noticed a number of packages in the repo’s have been updated over that time period too - so not sure if the repo’s did have issues or my config! however all now seems to be working correctly!

Thanks for your persistence and help on this!

harvybob on Apr 6, 2020

Can you also ensure once you have updated the Vagrant box that all the baseurl values in the /etc/yum.repos.d/*.repo files within the VM use https://? I’m now wondering if you had a really old image that used http:// instead and your ISP is doing some transparent proxying. By switching to https:// you can prevent that sort of thing from occurring.

Djelibeybi on Apr 1, 2020