3:24 p.m.
See[1]:
Cannot find a valid baseurl for repo: base/7/x86_64\
Y.
[1]
http://jenkins.ovirt.org/job/ovirt-system-tests_master_check-patch-el7-x8...
11:49 a.m.
'base' is the CentOS base repo that is preconfigured by the disro installer.
This is because we never finished good old:
https://ovirt-jira.atlassian.net/browse/OVIRT-1280
This kind of failure is to be expected once or twice on a weekly basis.
On 5 October 2017 at 15:24, Yaniv Kaul <ykaul(a)redhat.com> wrote:
See[1]:
Cannot find a valid baseurl for repo: base/7/x86_64\
Y.
[1] http://jenkins.ovirt.org/job/ovirt-system-tests_master_
check-patch-el7-x86_64/1930/testReport/junit/(root)/003_
00_metrics_bootstrap/configure_metrics/
_______________________________________________
Devel mailing list
Devel(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel
--
Barak Korren
RHV DevOps team , RHCE, RHCi
Red Hat EMEA
redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted
11:26 a.m.
On Fri, Oct 6, 2017 at 11:49 AM, Barak Korren <bkorren(a)redhat.com> wrote:
'base' is the CentOS base repo that is preconfigured by the
disro
installer.
This is because we never finished good old:
https://ovirt-jira.atlassian.net/browse/OVIRT-1280
The good news is that Daniel was able to make some progress on fixing this
during last week, so hopefully we'll able to disable external repos
soon and get rid of errors from external repos completely.
This kind of failure is to be expected once or twice on a weekly basis.
On 5 October 2017 at 15:24, Yaniv Kaul <ykaul(a)redhat.com> wrote:
> See[1]:
> Cannot find a valid baseurl for repo: base/7/x86_64\
>
>
>
> Y.
>
> [1] http://jenkins.ovirt.org/job/ovirt-system-tests_master_c
> heck-patch-el7-x86_64/1930/testReport/junit/(root)/003_00_
> metrics_bootstrap/configure_metrics/
>
> _______________________________________________
> Devel mailing list
> Devel(a)ovirt.org
> http://lists.ovirt.org/mailman/listinfo/devel
>
--
Barak Korren
RHV DevOps team , RHCE, RHCi
Red Hat EMEA
redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted
_______________________________________________
Devel mailing list
Devel(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel
--
Eyal edri
ASSOCIATE MANAGER
RHV DevOps
EMEA VIRTUALIZATION R&D
Red Hat EMEA <https://www.redhat.com/>
<https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
phone: +972-9-7692018
irc: eedri (on #tlv #rhev-dev #rhev-integ)
11:29 a.m.
On Oct 15, 2017 11:27 AM, "Eyal Edri" <eedri(a)redhat.com> wrote:
On Fri, Oct 6, 2017 at 11:49 AM, Barak Korren <bkorren(a)redhat.com> wrote:
'base' is the CentOS base repo that is preconfigured by the
disro
installer.
This is because we never finished good old:
https://ovirt-jira.atlassian.net/browse/OVIRT-1280
The good news is that Daniel was able to make some progress on fixing this
during last week, so hopefully we'll able to disable external repos
soon and get rid of errors from external repos completely.
But packages get updated here and there. How do we keep the internal repo
up-to-date?
Y.
This kind of failure is to be expected once or twice on a weekly basis.
On 5 October 2017 at 15:24, Yaniv Kaul <ykaul(a)redhat.com> wrote:
> See[1]:
> Cannot find a valid baseurl for repo: base/7/x86_64\
>
>
>
> Y.
>
> [1] http://jenkins.ovirt.org/job/ovirt-system-tests_master_c
> heck-patch-el7-x86_64/1930/testReport/junit/(root)/003_00_me
> trics_bootstrap/configure_metrics/
>
> _______________________________________________
> Devel mailing list
> Devel(a)ovirt.org
> http://lists.ovirt.org/mailman/listinfo/devel
>
--
Barak Korren
RHV DevOps team , RHCE, RHCi
Red Hat EMEA
redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted
_______________________________________________
Devel mailing list
Devel(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel
--
Eyal edri
ASSOCIATE MANAGER
RHV DevOps
EMEA VIRTUALIZATION R&D
Red Hat EMEA <https://www.redhat.com/>
<https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
phone: +972-9-7692018 <+972%209-769-2018>
irc: eedri (on #tlv #rhev-dev #rhev-integ)
11:47 a.m.
On 15 October 2017 at 11:29, Yaniv Kaul <ykaul(a)redhat.com> wrote:
On Oct 15, 2017 11:27 AM, "Eyal Edri" <eedri(a)redhat.com> wrote:
On Fri, Oct 6, 2017 at 11:49 AM, Barak Korren <bkorren(a)redhat.com> wrote:
> 'base' is the CentOS base repo that is preconfigured by the disro
> installer.
>
> This is because we never finished good old:
> https://ovirt-jira.atlassian.net/browse/OVIRT-1280
>
The good news is that Daniel was able to make some progress on fixing this
during last week, so hopefully we'll able to disable external repos
soon and get rid of errors from external repos completely.
But packages get updated here and there. How do we keep the internal repo
up-to-date?
Not sure I understand the question, the internal OST repo gets recreated
every time it runs.
--
Barak Korren
RHV DevOps team , RHCE, RHCi
Red Hat EMEA
redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted
12:12 p.m.
On Sun, Oct 15, 2017 at 11:47 AM, Barak Korren <bkorren(a)redhat.com> wrote:
On 15 October 2017 at 11:29, Yaniv Kaul <ykaul(a)redhat.com> wrote:
>
> On Oct 15, 2017 11:27 AM, "Eyal Edri" <eedri(a)redhat.com> wrote:
>
>
>
> On Fri, Oct 6, 2017 at 11:49 AM, Barak Korren <bkorren(a)redhat.com> wrote:
>
>> 'base' is the CentOS base repo that is preconfigured by the disro
>> installer.
>>
>> This is because we never finished good old:
>> https://ovirt-jira.atlassian.net/browse/OVIRT-1280
>>
>
> The good news is that Daniel was able to make some progress on fixing
> this during last week, so hopefully we'll able to disable external repos
> soon and get rid of errors from external repos completely.
>
>
> But packages get updated here and there. How do we keep the internal repo
> up-to-date?
>
Not sure I understand the question, the internal OST repo gets recreated
every time it runs.
It is created from the external resources (defined in reposync), so if
there's a new dep or anything (a packages moved from 'base' to
'updates' -
or the other way around), it'll fail (this is why we've re-enabled the
external repos - since we've failed to keep up with the changes).
Y.
--
Barak Korren
RHV DevOps team , RHCE, RHCi
Red Hat EMEA
redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted
1:59 p.m.
On 15 October 2017 at 12:12, Yaniv Kaul <ykaul(a)redhat.com> wrote:
It is created from the external resources (defined in reposync), so if
there's a new dep or anything (a packages moved from 'base' to
'updates' -
or the other way around), it'll fail (this is why we've re-enabled the
external repos - since we've failed to keep up with the changes).
This is due to white-listing, one way to handle that is just ensure the
include and exclude lists are always identical between 'base' and
'updates'.
In CI we have an extra layer of point-in-time mirrors we can use to
actually isolate upstream repo changes from the system, but we didn't
implement the code to consider changes to these repos as separate change
streams yet. This, of course will only become useful once we prevent the
VMs from bypassing this and going directly to the upstream repos.
--
Barak Korren
RHV DevOps team , RHCE, RHCi
Red Hat EMEA
redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted
2595
days inactive
2605
days old
6 comments
3 participants
participants (3)
-
Barak Korren -
Eyal Edri -
Yaniv Kaul