Re: ovirt-guest-agent is not building on EL7
by Barak Korren
On 3 April 2018 at 17:01, Sandro Bonazzola <sbonazzo(a)redhat.com> wrote:
>
>
> 2018-04-03 15:47 GMT+02:00 Barak Korren <bkorren(a)redhat.com>:
>
>> Please note,
>>
>> ovirt-guest-agent has been failing to build in CI on El7 ever since
>> the following patch:
>>
>> https://gerrit.ovirt.org/c/89631 - automation: drop aclocal from
>> check-patch.packages
>>
>> We are investigating why this wasn't reported to Gerrit, but in the
>> meantime please fix the build process. As things stand, all the recent
>> (6) merged patches are not being build and are therefore not passing
>> change-queue, not being released to 'tested' and will not pe published
>> in the nightly build.
>>
>
> Please note the failure has nothing to do with this patch.
> Issue here is:
>
> + pushd /home/jenkins/workspace/ovirt-guest-agent_master_build-artifacts-el7-x86_64/ovirt-guest-agent/tmp.repos/BUILD/ovirt-guest-agent-1.0.14/wineprefix/drive_c/Python27/Lib/site-packages/
> ~/tmp.repos/BUILD/ovirt-guest-agent-1.0.14/wineprefix/drive_c/Python27/Lib/site-packages ~/tmp.repos/BUILD/ovirt-guest-agent-1.0.14
> + wine python pywin32_postinstall.py -install -silent -quiet
> wine: Bad EXE format for C:\Python27\python.exe.
>
> And it's probably due to wrong wine being installed.
> I will probably need to rebuild wine on el7 for adding 32 bit and 64 bit
> recent wine.
>
>
Adding Dafna and infra for tracking.
--
Barak Korren
RHV DevOps team , RHCE, RHCi
Red Hat EMEA
redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted
6 years, 1 month
Build failed in Jenkins: system-sync_mirrors-centos-updates-el7-x86_64 #1431
by jenkins＠jenkins.phx.ovirt.org
See <http://jenkins.ovirt.org/job/system-sync_mirrors-centos-updates-el7-x86_6...>
------------------------------------------
Started by timer
[EnvInject] - Loading node environment variables.
Building remotely on mirrors.phx.ovirt.org (mirrors) in workspace <http://jenkins.ovirt.org/job/system-sync_mirrors-centos-updates-el7-x86_6...>
> git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
> git config remote.origin.url http://gerrit.ovirt.org/jenkins.git # timeout=10
Cleaning workspace
> git rev-parse --verify HEAD # timeout=10
Resetting working tree
> git reset --hard # timeout=10
> git clean -fdx # timeout=10
Pruning obsolete local branches
Fetching upstream changes from http://gerrit.ovirt.org/jenkins.git
> git --version # timeout=10
> git fetch --tags --progress http://gerrit.ovirt.org/jenkins.git +refs/heads/*:refs/remotes/origin/* --prune
> git rev-parse origin/master^{commit} # timeout=10
Checking out Revision 8265612b17ebc6f1414c6dba129d5f968817b9cd (origin/master)
> git config core.sparsecheckout # timeout=10
> git checkout -f 8265612b17ebc6f1414c6dba129d5f968817b9cd
Commit message: "Build container on changes to docker_cleanup"
> git rev-list --no-walk 8265612b17ebc6f1414c6dba129d5f968817b9cd # timeout=10
[system-sync_mirrors-centos-updates-el7-x86_64] $ /bin/bash -xe /tmp/jenkins1630288848112138082.sh
+ jenkins/scripts/mirror_mgr.sh resync_yum_mirror centos-updates-el7 x86_64 jenkins/data/mirrors-reposync.conf
Checking if mirror needs a resync
Traceback (most recent call last):
File "/usr/bin/reposync", line 343, in <module>
main()
File "/usr/bin/reposync", line 175, in main
my.doRepoSetup()
File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 681, in doRepoSetup
return self._getRepos(thisrepo, True)
File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 721, in _getRepos
self._repos.doSetup(thisrepo)
File "/usr/lib/python2.7/site-packages/yum/repos.py", line 157, in doSetup
self.retrieveAllMD()
File "/usr/lib/python2.7/site-packages/yum/repos.py", line 88, in retrieveAllMD
dl = repo._async and repo._commonLoadRepoXML(repo)
File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1474, in _commonLoadRepoXML
if self._latestRepoXML(local):
File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1443, in _latestRepoXML
oxml = self._saveOldRepoXML(local)
File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1300, in _saveOldRepoXML
shutil.copy2(local, old_local)
File "/usr/lib64/python2.7/shutil.py", line 131, in copy2
copystat(src, dst)
File "/usr/lib64/python2.7/shutil.py", line 98, in copystat
os.utime(dst, (st.st_atime, st.st_mtime))
OSError: [Errno 2] No such file or directory: '/home/jenkins/mirrors_cache/fedora-updates-fc24/repomd.xml.old.tmp'
Build step 'Execute shell' marked build as failure
6 years, 1 month
[JIRA] (OST-99) new ui_sanity scenario for basic_suite -- need multiple firefoxes and chromium
by Greg Sheremeta (oVirt JIRA)
This is a multi-part message in MIME format...
------------=_1522780386-19863-450
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
[ https://ovirt-jira.atlassian.net/browse/OST-99?page=com.atlassian.jira.pl... ]
Greg Sheremeta updated OST-99:
------------------------------
Description:
I'm writing a suite that does headless UI testing. One goal is to open headless firefox and actually open the UI, perform a login, make sure things look good, make sure there are no ui.log errors, etc. I'll also eventually add chromium, which can run headless now too.
The suite requires several firefox versions to be installed on the test machine, along with chromium. There are also some binary components required, geckodriver and chromedriver. These are not packaged.
Ideally the browsers can be installed to /opt/firefox55, /opt/firefox56, /opt/chromium62, etc. on the machine running the suite. So I think it makes sense to maintain a custom rpm with all of this.
Where can this rpm live? What is a reliable way to do this? (I know we want to avoid copr.)
...
Update for posterity (Mar 11 2018): we decided in the comments below to use [Selenium Grid|https://www.seleniumhq.org/docs/07_selenium_grid.jsp] and [docker-compose|https://github.com/SeleniumHQ/docker-selenium/wiki/Getting...]. Since Selenium Grid provides preconfigured containers, we're not maintaining anything other than docker-compose yaml files. No need to worry about packaging browsers ourselves.
---
Update for posterity (Apr 3 2018):
docker-compose doesn't work, but using a network and passing the hub IP (not container name) to the nodes does.
---
https://gerrit.ovirt.org/#/c/67166
was:
I'm writing a suite that does headless UI testing. One goal is to open headless firefox and actually open the UI, perform a login, make sure things look good, make sure there are no ui.log errors, etc. I'll also eventually add chromium, which can run headless now too.
The suite requires several firefox versions to be installed on the test machine, along with chromium. There are also some binary components required, geckodriver and chromedriver. These are not packaged.
Ideally the browsers can be installed to /opt/firefox55, /opt/firefox56, /opt/chromium62, etc. on the machine running the suite. So I think it makes sense to maintain a custom rpm with all of this.
Where can this rpm live? What is a reliable way to do this? (I know we want to avoid copr.)
...
Update for posterity (Mar 11 2018): we decided in the comments below to use [Selenium Grid|https://www.seleniumhq.org/docs/07_selenium_grid.jsp] and [docker-compose|https://github.com/SeleniumHQ/docker-selenium/wiki/Getting...]. Since Selenium Grid provides preconfigured containers, we're not maintaining anything other than docker-compose yaml files. No need to worry about packaging browsers ourselves.
---
https://gerrit.ovirt.org/#/c/67166
> new ui_sanity scenario for basic_suite -- need multiple firefoxes and chromium
> ------------------------------------------------------------------------------
>
> Key: OST-99
> URL: https://ovirt-jira.atlassian.net/browse/OST-99
> Project: oVirt system tests
> Issue Type: Improvement
> Reporter: Greg Sheremeta
> Assignee: infra
>
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100082)
------------=_1522780386-19863-450
Content-Type: text/html; charset="UTF-8"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
<html><body>
<pre>[ https://ovirt-jira.atlassian.net/browse/OST-99?page=com.atlassian.jira.pl... ]</pre>
<h3>Greg Sheremeta updated OST-99:</h3>
<pre>Description:</pre>
<p>I'm writing a suite that does headless UI testing. One goal is to open headless firefox and actually open the UI, perform a login, make sure things look good, make sure there are no ui.log errors, etc. I'll also eventually add chromium, which can run headless now too.</p>
<p>The suite requires several firefox versions to be installed on the test machine, along with chromium. There are also some binary components required, geckodriver and chromedriver. These are not packaged.</p>
<p>Ideally the browsers can be installed to /opt/firefox55, /opt/firefox56, /opt/chromium62, etc. on the machine running the suite. So I think it makes sense to maintain a custom rpm with all of this.</p>
<p>Where can this rpm live? What is a reliable way to do this? (I know we want to avoid copr.)</p>
<p>…</p>
<p>Update for posterity (Mar 11 2018): we decided in the comments below to use [Selenium Grid|<a href="https://www.seleniumhq.org/docs/07_selenium_grid.jsp">https://www.seleniumhq.org/docs/07_selenium_grid.jsp</a>] and [docker-compose|<a href="https://github.com/SeleniumHQ/docker-selenium/wiki/Getting-Started-with-D...">https://github.com/SeleniumHQ/docker-selenium/wiki/Getting-Started-with-D...</a>]. Since Selenium Grid provides preconfigured containers, we're not maintaining anything other than docker-compose yaml files. No need to worry about packaging browsers ourselves.</p>
<p>---</p>
<p>Update for posterity (Apr 3 2018): docker-compose doesn't work, but using a network and passing the hub IP (not container name) to the nodes does.</p>
<p>---</p>
<p><a href="https://gerrit.ovirt.org/#/c/67166">https://gerrit.ovirt.org/#/c/67166</a></p>
<pre>was:</pre>
<p>I'm writing a suite that does headless UI testing. One goal is to open headless firefox and actually open the UI, perform a login, make sure things look good, make sure there are no ui.log errors, etc. I'll also eventually add chromium, which can run headless now too.</p>
<p>The suite requires several firefox versions to be installed on the test machine, along with chromium. There are also some binary components required, geckodriver and chromedriver. These are not packaged.</p>
<p>Ideally the browsers can be installed to /opt/firefox55, /opt/firefox56, /opt/chromium62, etc. on the machine running the suite. So I think it makes sense to maintain a custom rpm with all of this.</p>
<p>Where can this rpm live? What is a reliable way to do this? (I know we want to avoid copr.)</p>
<p>…</p>
<p>Update for posterity (Mar 11 2018): we decided in the comments below to use [Selenium Grid|<a href="https://www.seleniumhq.org/docs/07_selenium_grid.jsp">https://www.seleniumhq.org/docs/07_selenium_grid.jsp</a>] and [docker-compose|<a href="https://github.com/SeleniumHQ/docker-selenium/wiki/Getting-Started-with-D...">https://github.com/SeleniumHQ/docker-selenium/wiki/Getting-Started-with-D...</a>]. Since Selenium Grid provides preconfigured containers, we're not maintaining anything other than docker-compose yaml files. No need to worry about packaging browsers ourselves.</p>
<p>---</p>
<p><a href="https://gerrit.ovirt.org/#/c/67166">https://gerrit.ovirt.org/#/c/67166</a></p>
<blockquote><h3>new ui_sanity scenario for basic_suite — need multiple firefoxes and chromium</h3>
<pre> Key: OST-99
URL: https://ovirt-jira.atlassian.net/browse/OST-99
Project: oVirt system tests
Issue Type: Improvement
Reporter: Greg Sheremeta
Assignee: infra</pre></blockquote>
<p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100082)</p>
<img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BS..." alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/>
</body></html>
------------=_1522780386-19863-450--
6 years, 1 month
[oVirt Jenkins] ovirt-system-tests_he-basic-ansible-suite-master - Build # 132 - Failure!
by jenkins＠jenkins.phx.ovirt.org
------=_Part_968_522320569.1522651074337
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Project: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-ansible-suite-ma...
Build: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-ansible-suite-ma...
Build Number: 132
Build Status: Failure
Triggered By: Started by timer
-------------------------------------
Changes Since Last Success:
-------------------------------------
Changes for Build #132
[Gal Ben Haim] he-iscsi-master: Temporarily exclude in check-patch
-----------------
Failed Tests:
-----------------
1 tests failed.
FAILED: 004_basic_sanity.snapshot_merge
Error Message:
status: 409
reason: Conflict
detail: Cannot create Snapshot. Snapshot is currently being created for VM vm0.
Stack Trace:
Traceback (most recent call last):
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 "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 68, in wrapper
return func(prefix.virt_env.engine_vm().get_api(), *args, **kwargs)
File "/home/jenkins/workspace/ovirt-system-tests_he-basic-ansible-suite-master/ovirt-system-tests/he-basic-ansible-suite-master/test-scenarios/004_basic_sanity.py", line 181, in snapshot_merge
api.vms.get(VM0_NAME).snapshots.add(dead_snap2_params)
File "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/brokers.py", line 34511, 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: Cannot create Snapshot. Snapshot is currently being created for VM vm0.
------=_Part_968_522320569.1522651074337--
6 years, 1 month
