Skip to content
This repository has been archived by the owner on Feb 7, 2024. It is now read-only.

RPM Validation notification email showing slatstack repo error. #469

Closed
shailesh-vaidya opened this issue Jun 21, 2021 · 0 comments · Fixed by #487
Closed

RPM Validation notification email showing slatstack repo error. #469

shailesh-vaidya opened this issue Jun 21, 2021 · 0 comments · Fixed by #487
Assignees
Labels
jenkins Jenkins related issues/PR's
Projects

Comments

@shailesh-vaidya
Copy link
Contributor

Error is as below,

<style> </style>
Component Name Naming Check License Check Instalation Directory Check Dependency Check
Motr          
cortx-motr-tests-ut Path Does Not Exists : conf, bin Error Log https://archive.repo.saltstack.com/py3/redhat/7.0/x86_64/archive/2019.2.1/repodata/repomd.xml: [Errno 14] HTTPS Error 404 - Not Found Trying other mirror. To address this issue please refer to the below wiki article https://wiki.centos.org/yum-errors If above article doesn't help to resolve this issue please use https://bugs.centos.org/. One of the configured repositories failed (SaltStack repo for RHEL/CentOS), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=saltstack-repo ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable saltstack-repo or subscription-manager repos --disable=saltstack-repo 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=saltstack-repo.skip_if_unavailable=true failure: repodata/repomd.xml from saltstack-repo: [Errno 256] No more mirrors to try. https://archive.repo.saltstack.com/py3/redhat/7.0/x86_64/archive/2019.2.1/repodata/repomd.xml: [Errno 14] HTTPS Error 404 - Not Found
cortx-motr-ivt Path Does Not Exists : conf, bin
cortx-motr-devel Path Does Not Exists : conf, bin
cortx-motr Error Log https://archive.repo.saltstack.com/py3/redhat/7.0/x86_64/archive/2019.2.1/repodata/repomd.xml: [Errno 14] HTTPS Error 404 - Not Found Trying other mirror. To address this issue please refer to the below wiki article https://wiki.centos.org/yum-errors If above article doesn't help to resolve this issue please use https://bugs.centos.org/. One of the configured repositories failed (SaltStack repo for RHEL/CentOS), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=saltstack-repo ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable saltstack-repo or subscription-manager repos --disable=saltstack-repo 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=saltstack-repo.skip_if_unavailable=true failure: repodata/repomd.xml from saltstack-repo: [Errno 256] No more mirrors to try. https://archive.repo.saltstack.com/py3/redhat/7.0/x86_64/archive/2019.2.1/repodata/repomd.xml: [Errno 14] HTTPS Error 404 - Not Found
S3          
cortx-s3iamcli-devel Path Does Not Exists : conf, bin Error Log https://archive.repo.saltstack.com/py3/redhat/7.0/x86_64/archive/2019.2.1/repodata/repomd.xml: [Errno 14] HTTPS Error 404 - Not Found Trying other mirror. To address this issue please refer to the below wiki article https://wiki.centos.org/yum-errors If above article doesn't help to resolve this issue please use https://bugs.centos.org/. One of the configured repositories failed (SaltStack repo for RHEL/CentOS), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=saltstack-repo ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable saltstack-repo or subscription-manager repos --disable=saltstack-repo 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=saltstack-repo.skip_if_unavailable=true failure: repodata/repomd.xml from saltstack-repo: [Errno 256] No more mirrors to try. https://archive.repo.saltstack.com/py3/redhat/7.0/x86_64/archive/2019.2.1/repodata/repomd.xml: [Errno 14] HTTPS Error 404 - Not Found
cortx-s3iamcli Path Does Not Exists : conf, bin Error Log https://archive.repo.saltstack.com/py3/redhat/7.0/x86_64/archive/2019.2.1/repodata/repomd.xml: [Errno 14] HTTPS Error 404 - Not Found Trying other mirror. To address this issue please refer to the below wiki article https://wiki.centos.org/yum-errors If above article doesn't help to resolve this issue please use https://bugs.centos.org/. One of the configured repositories failed (SaltStack repo for RHEL/CentOS), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=saltstack-repo ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable saltstack-repo or subscription-manager repos --disable=saltstack-repo 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=saltstack-repo.skip_if_unavailable=true failure: repodata/repomd.xml from saltstack-repo: [Errno 256] No more mirrors to try. https://archive.repo.saltstack.com/py3/redhat/7.0/x86_64/archive/2019.2.1/repodata/repomd.xml: [Errno 14] HTTPS Error 404 - Not Found
cortx-s3server Error Log https://archive.repo.saltstack.com/py3/redhat/7.0/x86_64/archive/2019.2.1/repodata/repomd.xml: [Errno 14] HTTPS Error 404 - Not Found Trying other mirror. To address this issue please refer to the below wiki article https://wiki.centos.org/yum-errors If above article doesn't help to resolve this issue please use https://bugs.centos.org/. One of the configured repositories failed (SaltStack repo for RHEL/CentOS), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=saltstack-repo ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable saltstack-repo or subscription-manager repos --disable=saltstack-repo 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=saltstack-repo.skip_if_unavailable=true failure: repodata/repomd.xml from saltstack-repo: [Errno 256] No more mirrors to try. https://archive.repo.saltstack.com/py3/redhat/7.0/x86_64/archive/2019.2.1/repodata/repomd.xml: [Errno 14] HTTPS Error 404 - Not Found
Hare          
cortx-hare Error Log https://archive.repo.saltstack.com/py3/redhat/7.0/x86_64/archive/2019.2.1/repodata/repomd.xml: [Errno 14] HTTPS Error 404 - Not Found Trying other mirror. To address this issue please refer to the below wiki article https://wiki.centos.org/yum-errors If above article doesn't help to resolve this issue please use https://bugs.centos.org/. One of the configured repositories failed (SaltStack repo for RHEL/CentOS), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=saltstack-repo ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable saltstack-repo or subscription-manager repos --disable=saltstack-repo 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=saltstack-repo.skip_if_unavailable=true failure: repodata/repomd.xml from saltstack-repo: [Errno 256] No more mirrors to try. https://archive.repo.saltstack.com/py3/redhat/7.0/x86_64/archive/2019.2.1/repodata/repomd.xml: [Errno 14] HTTPS Error 404 - Not Found
HA          
cortx-ha Path Does Not Exists : bin
CSM          
cortx-csm_web Path Does Not Exists : bin
cortx-csm_agent
Provisioner          
python36-cortx-prvsnr Error Log https://archive.repo.saltstack.com/py3/redhat/7.0/x86_64/archive/2019.2.1/repodata/repomd.xml: [Errno 14] HTTPS Error 404 - Not Found Trying other mirror. To address this issue please refer to the below wiki article https://wiki.centos.org/yum-errors If above article doesn't help to resolve this issue please use https://bugs.centos.org/. One of the configured repositories failed (SaltStack repo for RHEL/CentOS), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=saltstack-repo ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable saltstack-repo or subscription-manager repos --disable=saltstack-repo 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=saltstack-repo.skip_if_unavailable=true failure: repodata/repomd.xml from saltstack-repo: [Errno 256] No more mirrors to try. https://archive.repo.saltstack.com/py3/redhat/7.0/x86_64/archive/2019.2.1/repodata/repomd.xml: [Errno 14] HTTPS Error 404 - Not Found
cortx-prvsnr-cli Path Does Not Exists : conf, bin Error Log https://archive.repo.saltstack.com/py3/redhat/7.0/x86_64/archive/2019.2.1/repodata/repomd.xml: [Errno 14] HTTPS Error 404 - Not Found Trying other mirror. To address this issue please refer to the below wiki article https://wiki.centos.org/yum-errors If above article doesn't help to resolve this issue please use https://bugs.centos.org/. One of the configured repositories failed (SaltStack repo for RHEL/CentOS), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=saltstack-repo ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable saltstack-repo or subscription-manager repos --disable=saltstack-repo 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=saltstack-repo.skip_if_unavailable=true failure: repodata/repomd.xml from saltstack-repo: [Errno 256] No more mirrors to try. https://archive.repo.saltstack.com/py3/redhat/7.0/x86_64/archive/2019.2.1/repodata/repomd.xml: [Errno 14] HTTPS Error 404 - Not Found
cortx-prvsnr Path Does Not Exists : bin
SSPL          
cortx-sspl-test Path Check excluded : Error Log https://archive.repo.saltstack.com/py3/redhat/7.0/x86_64/archive/2019.2.1/repodata/repomd.xml: [Errno 14] HTTPS Error 404 - Not Found Trying other mirror. To address this issue please refer to the below wiki article https://wiki.centos.org/yum-errors If above article doesn't help to resolve this issue please use https://bugs.centos.org/. One of the configured repositories failed (SaltStack repo for RHEL/CentOS), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=saltstack-repo ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable saltstack-repo or subscription-manager repos --disable=saltstack-repo 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=saltstack-repo.skip_if_unavailable=true failure: repodata/repomd.xml from saltstack-repo: [Errno 256] No more mirrors to try. https://archive.repo.saltstack.com/py3/redhat/7.0/x86_64/archive/2019.2.1/repodata/repomd.xml: [Errno 14] HTTPS Error 404 - Not Found
cortx-sspl-cli Path Check excluded : Error Log https://archive.repo.saltstack.com/py3/redhat/7.0/x86_64/archive/2019.2.1/repodata/repomd.xml: [Errno 14] HTTPS Error 404 - Not Found Trying other mirror. To address this issue please refer to the below wiki article https://wiki.centos.org/yum-errors If above article doesn't help to resolve this issue please use https://bugs.centos.org/. One of the configured repositories failed (SaltStack repo for RHEL/CentOS), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=saltstack-repo ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable saltstack-repo or subscription-manager repos --disable=saltstack-repo 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=saltstack-repo.skip_if_unavailable=true failure: repodata/repomd.xml from saltstack-repo: [Errno 256] No more mirrors to try. https://archive.repo.saltstack.com/py3/redhat/7.0/x86_64/archive/2019.2.1/repodata/repomd.xml: [Errno 14] HTTPS Error 404 - Not Found
cortx-sspl Error Log https://archive.repo.saltstack.com/py3/redhat/7.0/x86_64/archive/2019.2.1/repodata/repomd.xml: [Errno 14] HTTPS Error 404 - Not Found Trying other mirror. To address this issue please refer to the below wiki article https://wiki.centos.org/yum-errors If above article doesn't help to resolve this issue please use https://bugs.centos.org/. One of the configured repositories failed (SaltStack repo for RHEL/CentOS), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=saltstack-repo ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable saltstack-repo or subscription-manager repos --disable=saltstack-repo 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=saltstack-repo.skip_if_unavailable=true failure: repodata/repomd.xml from saltstack-repo: [Errno 256] No more mirrors to try. https://archive.repo.saltstack.com/py3/redhat/7.0/x86_64/archive/2019.2.1/repodata/repomd.xml: [Errno 14] HTTPS Error 404 - Not Found
CORTX-utils          
stats_utils Path Does Not Exists : conf, bin Error Log https://archive.repo.saltstack.com/py3/redhat/7.0/x86_64/archive/2019.2.1/repodata/repomd.xml: [Errno 14] HTTPS Error 404 - Not Found Trying other mirror. To address this issue please refer to the below wiki article https://wiki.centos.org/yum-errors If above article doesn't help to resolve this issue please use https://bugs.centos.org/. One of the configured repositories failed (SaltStack repo for RHEL/CentOS), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=saltstack-repo ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable saltstack-repo or subscription-manager repos --disable=saltstack-repo 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=saltstack-repo.skip_if_unavailable=true failure: repodata/repomd.xml from saltstack-repo: [Errno 256] No more mirrors to try. https://archive.repo.saltstack.com/py3/redhat/7.0/x86_64/archive/2019.2.1/repodata/repomd.xml: [Errno 14] HTTPS Error 404 - Not Found
cortx-py-utils
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
jenkins Jenkins related issues/PR's
Projects
1 participant