[JIRA] (OVIRT-1395) CI on 4.1 engine patch fails on FC24 due to yum not finding the right mirror
by Gil Shinar (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1395?page=com.atlassian.jir... ]
Gil Shinar commented on OVIRT-1395:
-----------------------------------
You check-patch.repos file in ovirt-4.1 branch contains the following:
ovirt-snapshot,http://resources.ovirt.org/pub/ovirt-master-snapshot/rpm/$...
ovirt-snapshot-static,http://resources.ovirt.org/pub/ovirt-master-snapsho...
ci-tools,http://resources.ovirt.org/repos/ci-tools/$distro
Why are you using ovirt-master-snapshot-static and not ovirt-4.1-snapshot-static?
http://resources.ovirt.org/pub/ovirt-4.1-snapshot-static/rpm/
> CI on 4.1 engine patch fails on FC24 due to yum not finding the right mirror
> ----------------------------------------------------------------------------
>
> Key: OVIRT-1395
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1395
> Project: oVirt - virtualization made easy
> Issue Type: Outage
> Components: Jenkins
> Reporter: Allon Mureinik
> Assignee: infra
>
> CI on patch https://gerrit.ovirt.org/#/c/77074/ failed due to yum missing a mirror(?). The error:
> 04:13:13 ERROR: Command failed:
> 04:13:13 # /usr/bin/yum-deprecated --installroot /var/lib/mock/fedora-24-x86_64-6b7e112425ed139d649817c1e6d666bb-20792/root/ --releasever 24 install @buildsys-build autoconf git java-1.8.0-openjdk-devel make maven net-tools otopi postgresql-jdbc postgresql-server pyflakes python2-mock python-psycopg2 python2-pytest python-devel python-isort python-pep8 yum-utils --setopt=tsflags=nocontexts
> 04:13:13 Yum command has been deprecated, use dnf instead.
> 04:13:13 See 'man dnf' and 'man yum2dnf' for more information.
> 04:13:13
> 04:13:13 http://resources.ovirt.org/pub/ovirt-master-snapshot-static/rpm/fc24/repo...: [Errno 14] HTTP Error 404 - Not Found
> 04:13:13 Trying other mirror.
> 04:13:13
> 04:13:13
> 04:13:13 One of the configured repositories failed ("Custom ovirt-snapshot-static"),
> 04:13:13 and yum doesn't have enough cached data to continue. At this point the only
> 04:13:13 safe thing yum can do is fail. There are a few ways to work "fix" this:
> 04:13:13
> 04:13:13 1. Contact the upstream for the repository and get them to fix the problem.
> 04:13:13
> 04:13:13 2. Reconfigure the baseurl/etc. for the repository, to point to a working
> 04:13:13 upstream. This is most often useful if you are using a newer
> 04:13:13 distribution release than is supported by the repository (and the
> 04:13:13 packages for the previous distribution release still work).
> 04:13:13
> 04:13:13 3. Disable the repository, so yum won't use it by default. Yum will then
> 04:13:13 just ignore the repository until you permanently enable it again or use
> 04:13:13 --enablerepo for temporary usage:
> 04:13:13
> 04:13:13 yum-config-manager --disable ovirt-snapshot-static
> 04:13:13
> 04:13:13 4. Configure the failing repository to be skipped, if it is unavailable.
> 04:13:13 Note that yum will try to contact the repo. when it runs most commands,
> 04:13:13 so will have to try and fail each time (and thus. yum will be be much
> 04:13:13 slower). If it is a very temporary problem though, this is often a nice
> 04:13:13 compromise:
> 04:13:13
> 04:13:13 yum-config-manager --save --setopt=ovirt-snapshot-static.skip_if_unavailable=true
> 04:13:13
> 04:13:13 failure: repodata/repomd.xml from ovirt-snapshot-static: [Errno 256] No more mirrors to try.
> 04:13:13 http://resources.ovirt.org/pub/ovirt-master-snapshot-static/rpm/fc24/repo...: [Errno 14] HTTP Error 404 - Not Found
> Link to the jenkins output: http://jenkins.ovirt.org/job/ovirt-engine_4.1_check-patch-fc24-x86_64/108...
--
This message was sent by Atlassian JIRA
(v1000.990.2#100044)
8 years, 1 month
[JIRA] (OVIRT-1396) Add a new 'test-system-artifacts' Standard-CI stage
by Barak Korren (oVirt JIRA)
Barak Korren created OVIRT-1396:
-----------------------------------
Summary: Add a new 'test-system-artifacts' Standard-CI stage
Key: OVIRT-1396
URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1396
Project: oVirt - virtualization made easy
Issue Type: New Feature
Components: Jenkins
Reporter: Barak Korren
Assignee: infra
This is a part of [containers CI/CD|https://docs.google.com/a/redhat.com/document/d/1mEo3E0kRvlUWT9VaSP...] flow implementation process.
An order to allow building and testing processes for containers to be triggered after package that are needed for them are built, we will introduce the "{{test-system-artifacts}}" standard-CI stage.
This stage will be invoked from the 'experimental' or 'change-queue-tester' pipelines jost like the existing OST-based flows.
In order to provide package and repo information to the std-CI script invoked by this stage we well need to implement OVIRT-1391
--
This message was sent by Atlassian JIRA
(v1000.990.2#100044)
8 years, 1 month
[JIRA] (OVIRT-1395) CI on 4.1 engine patch fails on FC24 due to yum not finding the right mirror
by Allon Mureinik (oVirt JIRA)
Allon Mureinik created OVIRT-1395:
-------------------------------------
Summary: CI on 4.1 engine patch fails on FC24 due to yum not finding the right mirror
Key: OVIRT-1395
URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1395
Project: oVirt - virtualization made easy
Issue Type: Outage
Components: Jenkins
Reporter: Allon Mureinik
Assignee: infra
CI on patch https://gerrit.ovirt.org/#/c/77074/ failed due to yum missing a mirror(?). The error:
04:13:13 ERROR: Command failed:
04:13:13 # /usr/bin/yum-deprecated --installroot /var/lib/mock/fedora-24-x86_64-6b7e112425ed139d649817c1e6d666bb-20792/root/ --releasever 24 install @buildsys-build autoconf git java-1.8.0-openjdk-devel make maven net-tools otopi postgresql-jdbc postgresql-server pyflakes python2-mock python-psycopg2 python2-pytest python-devel python-isort python-pep8 yum-utils --setopt=tsflags=nocontexts
04:13:13 Yum command has been deprecated, use dnf instead.
04:13:13 See 'man dnf' and 'man yum2dnf' for more information.
04:13:13
04:13:13 http://resources.ovirt.org/pub/ovirt-master-snapshot-static/rpm/fc24/repo...: [Errno 14] HTTP Error 404 - Not Found
04:13:13 Trying other mirror.
04:13:13
04:13:13
04:13:13 One of the configured repositories failed ("Custom ovirt-snapshot-static"),
04:13:13 and yum doesn't have enough cached data to continue. At this point the only
04:13:13 safe thing yum can do is fail. There are a few ways to work "fix" this:
04:13:13
04:13:13 1. Contact the upstream for the repository and get them to fix the problem.
04:13:13
04:13:13 2. Reconfigure the baseurl/etc. for the repository, to point to a working
04:13:13 upstream. This is most often useful if you are using a newer
04:13:13 distribution release than is supported by the repository (and the
04:13:13 packages for the previous distribution release still work).
04:13:13
04:13:13 3. Disable the repository, so yum won't use it by default. Yum will then
04:13:13 just ignore the repository until you permanently enable it again or use
04:13:13 --enablerepo for temporary usage:
04:13:13
04:13:13 yum-config-manager --disable ovirt-snapshot-static
04:13:13
04:13:13 4. Configure the failing repository to be skipped, if it is unavailable.
04:13:13 Note that yum will try to contact the repo. when it runs most commands,
04:13:13 so will have to try and fail each time (and thus. yum will be be much
04:13:13 slower). If it is a very temporary problem though, this is often a nice
04:13:13 compromise:
04:13:13
04:13:13 yum-config-manager --save --setopt=ovirt-snapshot-static.skip_if_unavailable=true
04:13:13
04:13:13 failure: repodata/repomd.xml from ovirt-snapshot-static: [Errno 256] No more mirrors to try.
04:13:13 http://resources.ovirt.org/pub/ovirt-master-snapshot-static/rpm/fc24/repo...: [Errno 14] HTTP Error 404 - Not Found
Link to the jenkins output: http://jenkins.ovirt.org/job/ovirt-engine_4.1_check-patch-fc24-x86_64/108...
--
This message was sent by Atlassian JIRA
(v1000.990.2#100044)
8 years, 1 month
[JIRA] (OVIRT-1394) Remove STD-CI cleanup function cleanup_var
by Gil Shinar (oVirt JIRA)
Gil Shinar created OVIRT-1394:
---------------------------------
Summary: Remove STD-CI cleanup function cleanup_var
Key: OVIRT-1394
URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1394
Project: oVirt - virtualization made easy
Issue Type: Task
Reporter: Gil Shinar
Assignee: infra
We do not remember why /var/tmp is being cleaned on each STD-CI job.
/var/tmp is good place for caching stuff (maven for example).
I'll remove the /var/tmp cleanup function and will monitor /var/tmp on slaves to make sure it does not use too much disk space.
--
This message was sent by Atlassian JIRA
(v1000.990.2#100044)
8 years, 1 month
[JIRA] (OVIRT-1381) Re: Findbugs issues not reported correctly on Jenkins master jobs?
by Daniel Belenky (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1381?page=com.atlassian.jir... ]
Daniel Belenky commented on OVIRT-1381:
---------------------------------------
I can't find any files that are being generated by findbugs that are not being processed by Jenkins.
[~tnisan(a)redhat.com] can you run this check again and paste here the list of files being processed in your local run?
> Re: Findbugs issues not reported correctly on Jenkins master jobs?
> ------------------------------------------------------------------
>
> Key: OVIRT-1381
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1381
> Project: oVirt - virtualization made easy
> Issue Type: By-EMAIL
> Reporter: Gil Shinar
> Assignee: Daniel Belenky
>
> Adding infra-support
> On Mon, May 15, 2017 at 3:55 PM, Tal Nisan <tnisan(a)redhat.com> wrote:
> > Just a regular "mvn findbugs:findbugs" run on master, you can revert this
> > patch and run it manually yourself: https://gerrit.ovirt.org/#/c/76820/
> >
> > On Mon, May 15, 2017 at 2:15 PM, Daniel Belenky <dbelenky(a)redhat.com>
> > wrote:
> >
> >> Hi Tal,
> >> I'm checking this right now.
> >> Can you provide the log from your local run? which files were exported on
> >> your local run?
> >>
> >> On Mon, May 15, 2017 at 11:51 AM Tal Nisan <tnisan(a)redhat.com> wrote:
> >>
> >>> I've pushed this patch to master:
> >>> https://gerrit.ovirt.org/#/c/75994/
> >>> Jenkins showed no findbugs error and I moved on to merging it
> >>>
> >>> Then I've pushed the same patch to 4.1:
> >>> https://gerrit.ovirt.org/#/c/76803/
> >>> And it resulted in two findbugs errors (though minor and style related):
> >>> http://jenkins.ovirt.org/job/ovirt-engine_4.1_find-bugs_crea
> >>> ted/898/findbugsResult/new/
> >>>
> >>> Running findbugs manually in my environment on master did report these
> >>> two issues so I'd expect the master jobs to report them as well.
> >>>
> >>> _______________________________________________
> >>> Infra mailing list
> >>> Infra(a)ovirt.org
> >>> http://lists.ovirt.org/mailman/listinfo/infra
> >>>
> >> --
> >>
> >> DANIEL BELENKY
> >>
> >> RHV DEVOPS
> >>
> >> Red Hat EMEA <https://www.redhat.com/>
> >>
> >> IRC: #rhev-integ #rhev-dev
> >> <https://red.ht/sig>
> >>
> >
> >
> > _______________________________________________
> > Infra mailing list
> > Infra(a)ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/infra
> >
> >
--
This message was sent by Atlassian JIRA
(v1000.990.2#100044)
8 years, 1 month
[oVirt Jenkins] ovirt_4.1_hc-system-tests - Build # 72 - Failure!
by jenkins＠jenkins.phx.ovirt.org
------=_Part_99_746776734.1495337671794
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Project: http://jenkins.ovirt.org/job/ovirt_4.1_hc-system-tests/
Build: http://jenkins.ovirt.org/job/ovirt_4.1_hc-system-tests/72/
Build Number: 72
Build Status: Failure
Triggered By: Started by timer
-------------------------------------
Changes Since Last Success:
-------------------------------------
Changes for Build #72
[Gal Ben Haim] Adding the ability to export images
-----------------
Failed Tests:
-----------------
1 tests failed.
FAILED: 002_bootstrap.add_hosts
Error Message:
status: 409
reason: Conflict
detail: Server 192.168.200.4 is already part of another cluster.
-------------------- >> begin captured logging << --------------------
lago.utils: ERROR: Error while running thread
Traceback (most recent call last):
File "/usr/lib/python2.7/site-packages/lago/utils.py", line 58, in _ret_via_queue
queue.put({'return': func()})
File "/home/jenkins/workspace/ovirt_4.1_hc-system-tests/ovirt-system-tests/hc-basic-suite-4.1/test-scenarios/002_bootstrap.py", line 141, in _add_host
return api.hosts.add(p)
File "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/brokers.py", line 18306, in add
headers={"Correlation-Id":correlation_id, "Expect":expect}
File "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/proxy.py", line 79, in add
return self.request('POST', url, body, headers, cls=cls)
File "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/proxy.py", line 122, in request
persistent_auth=self.__persistent_auth
File "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/connectionspool.py", line 79, in do_request
persistent_auth)
File "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/connectionspool.py", line 162, in __do_request
raise errors.RequestError(response_code, response_reason, response_body)
RequestError:
status: 409
reason: Conflict
detail: Server 192.168.200.4 is already part of another cluster.
--------------------- >> end captured logging << ---------------------
Stack Trace:
File "/usr/lib64/python2.7/unittest/case.py", line 369, in run
testMethod()
File "/usr/lib/python2.7/site-packages/nose/case.py", line 197, in runTest
self.test(*self.arg)
File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 129, in wrapped_test
test()
File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 59, in wrapper
return func(get_test_prefix(), *args, **kwargs)
File "/home/jenkins/workspace/ovirt_4.1_hc-system-tests/ovirt-system-tests/hc-basic-suite-4.1/test-scenarios/002_bootstrap.py", line 160, in add_hosts
nt.assert_true(all(vt.join_all()))
File "/usr/lib/python2.7/site-packages/lago/utils.py", line 58, in _ret_via_queue
queue.put({'return': func()})
File "/home/jenkins/workspace/ovirt_4.1_hc-system-tests/ovirt-system-tests/hc-basic-suite-4.1/test-scenarios/002_bootstrap.py", line 141, in _add_host
return api.hosts.add(p)
File "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/brokers.py", line 18306, in add
headers={"Correlation-Id":correlation_id, "Expect":expect}
File "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/proxy.py", line 79, in add
return self.request('POST', url, body, headers, cls=cls)
File "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/proxy.py", line 122, in request
persistent_auth=self.__persistent_auth
File "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/connectionspool.py", line 79, in do_request
persistent_auth)
File "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/connectionspool.py", line 162, in __do_request
raise errors.RequestError(response_code, response_reason, response_body)
status: 409
reason: Conflict
detail: Server 192.168.200.4 is already part of another cluster.
-------------------- >> begin captured logging << --------------------
lago.utils: ERROR: Error while running thread
Traceback (most recent call last):
File "/usr/lib/python2.7/site-packages/lago/utils.py", line 58, in _ret_via_queue
queue.put({'return': func()})
File "/home/jenkins/workspace/ovirt_4.1_hc-system-tests/ovirt-system-tests/hc-basic-suite-4.1/test-scenarios/002_bootstrap.py", line 141, in _add_host
return api.hosts.add(p)
File "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/brokers.py", line 18306, in add
headers={"Correlation-Id":correlation_id, "Expect":expect}
File "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/proxy.py", line 79, in add
return self.request('POST', url, body, headers, cls=cls)
File "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/proxy.py", line 122, in request
persistent_auth=self.__persistent_auth
File "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/connectionspool.py", line 79, in do_request
persistent_auth)
File "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/connectionspool.py", line 162, in __do_request
raise errors.RequestError(response_code, response_reason, response_body)
RequestError:
status: 409
reason: Conflict
detail: Server 192.168.200.4 is already part of another cluster.
--------------------- >> end captured logging << ---------------------
------=_Part_99_746776734.1495337671794--
8 years, 1 month
[JIRA] (OVIRT-1393) Make mirror injection process remove “skip_if_unavailable” settings
by Barak Korren (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1393?page=com.atlassian.jir... ]
Barak Korren updated OVIRT-1393:
--------------------------------
Description:
This is a part of [containers CI/CD|https://docs.google.com/a/redhat.com/document/d/1mEo3E0kRvlUWT9VaSP...] flow implementation process.
In order to allow having stub repository configuration files as specified in OVIRT-1391, we need to be able to use the "{{skip_if_unavailable}}" yum setting. But we don't want this setting to still be in affect once mirror injection happens and the repo configuration points to a real repo. Therefore we need to make the mirror injection process remove this setting for repo configurations into which mirror URLs are injected.
was:
This is a part of [containers CI/CD|https://docs.google.com/a/redhat.com/document/d/1mEo3E0kRvlUWT9VaSP...] flow implementation process.
In order to allow having stub repository configuration files as specified in OVIRT-1391, we need to be able to use the "{skip_if_unavailable}" yum setting. But we don't want this setting to still be in affect once mirror injection happens and the repo configuration points to a real repo. Therefore we need to make the mirror injection process remove this setting for repo configurations into which mirror URLs are injected.
> Make mirror injection process remove “skip_if_unavailable” settings
> -------------------------------------------------------------------
>
> Key: OVIRT-1393
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1393
> Project: oVirt - virtualization made easy
> Issue Type: New Feature
> Components: Jenkins
> Reporter: Barak Korren
> Assignee: infra
> Labels: containers, mirrors, mock_runner.sh
>
> This is a part of [containers CI/CD|https://docs.google.com/a/redhat.com/document/d/1mEo3E0kRvlUWT9VaSP...] flow implementation process.
> In order to allow having stub repository configuration files as specified in OVIRT-1391, we need to be able to use the "{{skip_if_unavailable}}" yum setting. But we don't want this setting to still be in affect once mirror injection happens and the repo configuration points to a real repo. Therefore we need to make the mirror injection process remove this setting for repo configurations into which mirror URLs are injected.
--
This message was sent by Atlassian JIRA
(v1000.990.2#100044)
8 years, 1 month