-
Notifications
You must be signed in to change notification settings - Fork 9
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
Enable CRB and EPEL if we are running with the EPEL profile #41
Conversation
Fixes: OSCI-6783 Signed-off-by: Michal Srb <michal@redhat.com>
Signed-off-by: Michal Srb <michal@redhat.com>
Signed-off-by: Michal Srb <michal@redhat.com>
It seems like both CRB and EPEL are actually already enabled: https://artifacts.dev.testing-farm.io/7d43c63c-ac23-454d-9c43-8382d9fdf002/
|
Hm, interesting. For reference, here's a recent pull request and Testing Farm job which failed: |
Yeah, and this test pipeline failed as well :) Maybe there are actually some dependency problems (?) |
The installability job complains about missing
|
Could this be TF adding/enabling the EPEL repository automatically? And possibly using some older version/compose or something (?) |
Ah, I think I understand now. I think Let's see... |
Signed-off-by: Michal Srb <michal@redhat.com>
Meh...
So something is installing |
Signed-off-by: Michal Srb <michal@redhat.com>
I am looking at this |
@msrb not really, it should be installed and enabled (we do not disable it as in RHEL) |
Using the reproducer from https://artifacts.dev.testing-farm.io/7d43c63c-ac23-454d-9c43-8382d9fdf002/ the |
@martinhoyer that should not be the case for Testing Farm itself:
As you can see, |
@msrb I do not see a problem with Testing Farm, has to be installability, most probably |
Here's a fresh instance of the problem: @msrb, are you familiar with |
@msrb FTR, this is the state after TF hands over the execution to tmt:
As you can see, epel is enabled on the machines. |
@psss Nope, this is definitely mini-tps/pipeline issue. |
Fixes: OSCI-6783