New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RHEL CI is failing #155
Comments
|
The thing that looks weird to me there is the 'rhui-rhel-7-server-rhui-eus-rpms' - the 'eus' is the very very very very very long term stable support where nothing gets new versions. |
|
Besides docker, we have other packages that are failing |
|
@jodh-intel and @chavafg , right now I disabled the CI as we got many failures in the repositories |
|
It looks like glibc-static-2.17-260.el7_6.5 is hot off the press and only just been released, and your mirror/update/azure rhui thing has got that but doesn't yet have the -devel equivalents. I guess if we just wait for the mirror to refresh it should sort itself out; so try again tomorrow; if it's still fighting give me another ping and I'll poke at our package people. |
|
@dagrh yes, I will try tomorrow thanks for the help |
|
Would you please show us the output of I wonder if you have the optional channels enabled. Since |
|
|
You have the optional repos enabled, and that's expected. You see it in your error message:
Yum wouldn't know anything about We only just shipped "2.17-260.el7_6.5" 23 hours ago, I don't know if that's long enough for your cloud provider to synchronize that content? It really depends on your cloud providers RHUI configuration. |
|
I filed an RFE with the RHUI team to see what they say about this situation: |
|
@codonell thanks |
|
This looks outdated: Please try running I do not think this is related to atomic updates, given the repository age displayed in the debug output. And Red Hat's internal CDN mirror has the 2.17-260.el7_6.6 packages in the optional channel. |
|
@fweimer this is the output |
|
This looks good: I believe |
Currently, we have issues in the RHEL CI, while we are trying to install docker.
The way that we are doing the docker installation is by doing
I saw that the
container-selinuxwe can grab it from theextras-repobut I am having an issue thereThis issue is happening in our RHEL Azure Images, any ideas of how can I solve that @dagrh? thanks
The text was updated successfully, but these errors were encountered: