- Devel - oVirt List Archives

oVirt Engine 4.0.4 branched
by Tal Nisan 30 Aug '16

30 Aug '16

Hi everyone, We've created ovirt-engine-4.0.4 branch this morning from the 4.0.3 branch. >From now on 4.0.4 Engine patches will have to be backported to the new branch after being backported to the ovirt-engine-4.0 branch. Engine 4.0.5 patches can now be backported to ovirt-engine-4.0 branch. Tal.

3 4

repos down
by Gary Pedretty 30 Aug '16

30 Aug '16

--Apple-Mail=_A85252B1-0D2F-4BC6-948C-BDA2E4E5E66B Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 I am unable to do any installs, yum cannot access the mirrors list =E2=80=9CCould not retrieve mirrorlist = http://resources.ovirt.org/pub/yum-repo/mirrorlist-ovirt-4.0-el7=E2=80=9D = error was 12: Timeout on = http://resources.ovirt.org/pub/yum-repo/mirrorlist-ovirt-4.0-el7: (28, = =E2=80=98Connection timed out after 30001 milliseconds=E2=80=99)" Tried from various locations on different ISPs. Gary ------------------------------------------------------------------------ Gary Pedretty gary(a)ravnalaska.net = <mailto:gary@eraalaska.net> Systems Manager www.flyravn.com = <http://www.flyravn.com/> Ravn Alaska /\ 907-450-7251 5245 Airport Industrial Road / \/\ 907-450-7238 fax Fairbanks, Alaska 99709 /\ / \ \ Second greatest commandment Serving All of Alaska / \/ /\ \ \/\ =E2=80=9CLove your = neighbor as Really loving the record green up date! Summmer!! yourself=E2=80=9D = Matt 22:39 ------------------------------------------------------------------------ --Apple-Mail=_A85252B1-0D2F-4BC6-948C-BDA2E4E5E66B Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 <html><head><meta http-equiv=3D"Content-Type" content=3D"text/html = charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; = -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" = class=3D"">I am unable to do any installs, yum cannot access the mirrors = list<div class=3D""><br class=3D""></div><div class=3D"">=E2=80=9CCould = not retrieve mirrorlist <a = href=3D"http://resources.ovirt.org/pub/yum-repo/mirrorlist-ovirt-4.0-el7" = class=3D"">http://resources.ovirt.org/pub/yum-repo/mirrorlist-ovirt-4.0-el= 7</a>=E2=80=9D error was</div><div class=3D"">12: Timeout on <a = href=3D"http://resources.ovirt.org/pub/yum-repo/mirrorlist-ovirt-4.0-el7:"= = class=3D"">http://resources.ovirt.org/pub/yum-repo/mirrorlist-ovirt-4.0-el= 7:</a> (28, =E2=80=98Connection timed out after 30001 = milliseconds=E2=80=99)"</div><div class=3D""><br class=3D""></div><div = class=3D"">Tried from various locations on different ISPs.</div><div = class=3D""><br class=3D""></div><div class=3D"">Gary</div><div = class=3D""><br class=3D""><div class=3D""> <div style=3D"color: rgb(0, 0, 0); letter-spacing: normal; orphans: = auto; text-align: start; text-indent: 0px; text-transform: none; = white-space: normal; widows: auto; word-spacing: 0px; = -webkit-text-stroke-width: 0px; word-wrap: break-word; = -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" = class=3D""><div style=3D"color: rgb(0, 0, 0); letter-spacing: normal; = orphans: auto; text-align: start; text-indent: 0px; text-transform: = none; white-space: normal; widows: auto; word-spacing: 0px; = -webkit-text-stroke-width: 0px; word-wrap: break-word; = -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" = class=3D""><div style=3D"orphans: auto; text-align: start; text-indent: = 0px; widows: auto; word-wrap: break-word; -webkit-nbsp-mode: space; = -webkit-line-break: after-white-space;" class=3D""><div style=3D"orphans: = auto; text-align: start; text-indent: 0px; widows: auto; word-wrap: = break-word; -webkit-nbsp-mode: space; -webkit-line-break: = after-white-space;" class=3D""><div style=3D"orphans: auto; text-align: = start; text-indent: 0px; widows: auto; word-wrap: break-word; = -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" = class=3D""><div style=3D"orphans: auto; text-align: start; text-indent: = 0px; widows: auto; word-wrap: break-word; -webkit-nbsp-mode: space; = -webkit-line-break: after-white-space;" class=3D""><div style=3D"orphans: = auto; text-align: start; text-indent: 0px; widows: auto; word-wrap: = break-word; -webkit-nbsp-mode: space; -webkit-line-break: = after-white-space;" class=3D""><div style=3D"orphans: auto; text-align: = start; text-indent: 0px; widows: auto; word-wrap: break-word; = -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" = class=3D""><div style=3D"orphans: auto; text-align: start; text-indent: = 0px; widows: auto; word-wrap: break-word; -webkit-nbsp-mode: space; = -webkit-line-break: after-white-space;" class=3D""><font face=3D"Menlo" = style=3D"color: rgb(0, 0, 0); font-size: 12px; letter-spacing: normal; = text-transform: none; white-space: normal; word-spacing: 0px; = -webkit-text-stroke-width: 0px;" class=3D""><div = class=3D"">---------------------------------------------------------------= ---------</div><div class=3D"">Gary Pedretty         =                     =            <a = href=3D"mailto:gary@eraalaska.net" = class=3D"">gary(a)ravnalaska.net</a></div><div class=3D"">Systems Manager =                     =                     =  <a href=3D"http://www.flyravn.com" = class=3D"">www.flyravn.com</a></div><div class=3D"">Ravn Alaska   =                     =     /\                 =    907-450-7251</div><div class=3D"">5245 Airport Industrial = Road         /  \/\         =     907-450-7238 fax</div><div class=3D"">Fairbanks, Alaska =  99709        /\  /    \ \ = Second greatest commandment</div></font><font face=3D"Monaco" = class=3D""><span style=3D"font-size: 12px;" class=3D"">Serving All of = Alaska          /  \/  /\  \ \/\ =   =E2=80=9CLove your neighbor as</span></font><br = style=3D"font-family: Monaco;" class=3D""><font face=3D"Menlo" = style=3D"color: rgb(0, 0, 0); letter-spacing: normal; text-transform: = none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: = 0px;" class=3D""><span style=3D"font-size: 12px;" class=3D"">Really = loving the record green up date! Summmer!!   yourself=E2=80=9D M= att 22:39</span></font><div style=3D"color: rgb(0, 0, 0); = letter-spacing: normal; text-transform: none; white-space: normal; = word-spacing: 0px; -webkit-text-stroke-width: 0px; font-family: Menlo;" = class=3D""></div><font face=3D"Menlo" style=3D"font-size: 12px;" = class=3D""></font><span style=3D"color: rgb(0, 0, 0); letter-spacing: = normal; text-transform: none; white-space: normal; word-spacing: 0px; = -webkit-text-stroke-width: 0px; font-size: 12px;" class=3D""><font = face=3D"Menlo" class=3D""><div = class=3D"">---------------------------------------------------------------= ---------</div></font></span><div style=3D"color: rgb(0, 0, 0); = letter-spacing: normal; text-transform: none; white-space: normal; = word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=3D""><font = face=3D"Menlo" style=3D"font-size: 12px;" class=3D""><br = class=3D""></font></div></div><span style=3D"color: rgb(0, 0, 0); = letter-spacing: normal; text-transform: none; white-space: normal; = word-spacing: 0px; -webkit-text-stroke-width: 0px; font-size: 12px;" = class=3D""><br class=3D"Apple-interchange-newline"></span></div><span = style=3D"color: rgb(0, 0, 0); letter-spacing: normal; text-transform: = none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: = 0px; font-size: 12px;" class=3D""><br = class=3D"Apple-interchange-newline"></span></div><span style=3D"color: = rgb(0, 0, 0); letter-spacing: normal; text-transform: none; white-space: = normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; font-size: = 12px;" class=3D""><br class=3D"Apple-interchange-newline"></span></div><br= class=3D"Apple-interchange-newline"></div><br = class=3D"Apple-interchange-newline"></div><br = class=3D"Apple-interchange-newline"></div><br = class=3D"Apple-interchange-newline"></div><br = class=3D"Apple-interchange-newline"></div><br = class=3D"Apple-interchange-newline"><br = class=3D"Apple-interchange-newline"> </div> <br class=3D""></div></body></html>= --Apple-Mail=_A85252B1-0D2F-4BC6-948C-BDA2E4E5E66B--

3 2

oVirt 4.0.4 RC1 merge / branch / tag / bugzilla reminder
by Sandro Bonazzola 29 Aug '16

29 Aug '16

All stable branch maintainers, please make sure to - merge all relevant open bugs until Tuesday morning 11:00 AM TLV time. For each package that need to be built (i.e oVirt product) please make sure every bug in MODIFIED has the right Target Release and Target Milestone. A Target release should state the version of the package you're building and should include the same version you used for the tag you just used for this build. (e.g. for ovirt-engine, tag: ovirt-engine-4.0.4, tr: 4.0.4) A list of bugs that require attention is here: - https://bugzilla.redhat.com/buglist.cgi?quicksearch=target_milestone%3A4.0.… -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com <https://www.redhat.com/it/about/events/red-hat-open-source-day-2016>

1 0

oVirt 4.0.4 RC1 build planned
by Sandro Bonazzola 29 Aug '16

29 Aug '16

Fyi oVirt developers, An oVirt build is planned for this Tuesday 11:00 AM TLV time (10:00 AM CEST). Taking into consideration the time it takes for Jenkins to run a full CI everything need to be backported by Monday 11PM. Please make sure to mark as verified and CR +2 so it will be ready for merging Tuesday morning. A list of pending blockers is available here: https://bugzilla.redhat.com/buglist.cgi?quicksearch=target_milestone%3A4.0. <https://bugzilla.redhat.com/buglist.cgi?quicksearch=target_milestone%3A4.0.…> 4 <https://bugzilla.redhat.com/buglist.cgi?quicksearch=target_milestone%3A4.0.…> %20flag%3Ablocker%20status%3Anew%2Cassigned%2Cpost <https://bugzilla.redhat.com/buglist.cgi?quicksearch=target_milestone%3A4.0.…> -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com <https://www.redhat.com/it/about/events/red-hat-open-source-day-2016>

1 0

broken master: removal of release in spec requirements
by Yaniv Bronheim 29 Aug '16

29 Aug '16

Hi, In https://gerrit.ovirt.org/#/c/62672 we removed the release from vdsm* requirements. Although it sounds reasonable and quite safe, it was not. In development env it causes mixup of versions when upgrading. "yum install vdsm" will eventually cause this mixup as vdsm won't require the newer vdsm-python I think this change should be reverted and the solution should be in the build process. Newer release is equal to higher version, requirement should include the release number. so for example, 4.18.7-1 was shipped and for ppc we built 4.18.7-2 so 4.18.7-2 is newer. can't see how this can be different. e.g for the bug: =================================================================================================================================================================================================================== Package Arch Version Repository Size =================================================================================================================================================================================================================== Removing: vdsm x86_64 4.18.999-457.gitcde215c.el7.centos @ovirt-master-snapshot 2.7 M vdsm-api noarch 4.18.999-342.git40c3bbb.el7.centos @ovirt-master-snapshot 325 k vdsm-cli noarch 4.18.999-457.gitcde215c.el7.centos @ovirt-master-snapshot 342 k vdsm-hook-vmfex-dev noarch 4.18.999-457.gitcde215c.el7.centos @ovirt-master-snapshot 21 k vdsm-jsonrpc noarch 4.18.999-342.git40c3bbb.el7.centos @ovirt-master-snapshot 81 k vdsm-python noarch 4.18.999-342.git40c3bbb.el7.centos @ovirt-master-snapshot 2.4 M vdsm-xmlrpc noarch 4.18.999-342.git40c3bbb.el7.centos @ovirt-master-snapshot 109 k vdsm-yajsonrpc noarch 4.18.999-342.git40c3bbb.el7.centos @ovirt-master-snapshot 95 k Problem. -- *Yaniv Bronhaim.*

4 5

Re: [ovirt-devel] [libvirt] RFC: Limited dynamic ownership
by Martin Kletzander 29 Aug '16

29 Aug '16

--R3G7APHDIzY6R/pk Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline On Tue, Aug 23, 2016 at 07:25:56PM -0400, Daniel P. Berrange wrote: >On Tue, Aug 23, 2016 at 06:17:44PM -0400, Martin Kletzander wrote: >> On Tue, Aug 23, 2016 at 05:54:29PM -0400, Daniel P. Berrange wrote: >> > On Tue, Aug 23, 2016 at 05:06:20PM -0400, Martin Kletzander wrote: >> > > Hi everyone, >> > > >> > > so there was an idea about limiting the relabelling of images that >> > > libvirt does. And I'm taking the liberty of pitching my idea how to >> > > approach this. I feel like it's pretty simple thing and there's not >> > > much to talk about, but a) I could've missed something and b) you might >> > > hate the way I approach it. >> > > >> > > The idea is to extend the seclabel XML, for example: >> > > >> > > <seclabel type='dynamic' model='dac' relabel='whitelist'> >> > > <path>/var/lib/libvirt/images</path> >> > > <path>/data/virt-stuff</path> >> > > </seclabel> >> > > >> > > Either we allow 'relabel' to be set to 'whitelist' or add a new >> > > attribute with a name like 'mode' or something, which will control how >> > > we relabel the files (actually relabel='no' can mean 'whitelist' and >> > > relabel='yes' can mean blacklist without adding anything there). After >> > > that you can specify what paths are (dis)allowed to be labelled. >> > > >> > > Actually thinking about it I like the following the most: >> > > >> > > <seclabel type='dynamic' model='dac' relabel='no'> >> > > <whitelist path='/data'/> >> > > <blacklist path='/data/private/non-virt/stuff'/> >> > > </seclabel> >> > > >> > > which I believe is pretty explanatory. Feel free to ask if it's not. >> > > And let me know what you think. >> > >> > I don't think we need to get involved in the <seclabel> configuration. >> > >> >> I forgot to mention that I like that because you would be able to >> specify this per-disk as well as for the whole VM. > >Of course using info in <disk> directly achieves the same thing > >> > We've already got the ability in the <disk> config to provide the >> > full backing chain explicitly. If a management app provides a full >> > backing chain in the XML, we could validate the app provided chain >> > against the chain we probe and report error if they mis-match. (Maybe >> > we in fact already report this?) >> > >> >> Not yet: >> >> "It is currently ignored on input and only used for output to describe >> the detected backing chains of running domains." >> >> It would help with this, but I don't feel like it's that usable. Also >> I feel like everyone will overuse that while misunderstanding what it >> actually does. Also if you do some block-merge or whatever, you need to >> update the backing chain and everyone will just re-probe it because no >> management layer likes keeping more information than needed. > >If you provide the <seclabel> whitelist though, you're essentially >going to want to provide the same info that you would provide with >the <backing> data, as the whitelist you're providing there is >essentially trying to whitelist only the expected backing file. > >I don't feel like we should be inventing new seclabel elements to >duplicate info we could already provide via existing backing data >elements. > It just introduces more complexity that might result in more bugs, but yes, it is information duplication. >> > Thinking bout this in the context of a recent OpenStack Nova CVE, >> > where Nova mistakenly set format=qcow2, instead of format=raw, allowing >> > a malicious guest to write a qcow2 header with backing file. If Nova >> > had provided the full backing chain it expected (no backing chain at >> > all), then libvirt would have seen the maliciously created backing >> > chain, and caught the problem despite Nova giving the wrong format. >> > >> > >> > Separately from this, in the context of storage pools, when giving >> > a <disk type=pool> in the domain XML, we could do validation to >> > ensure the backing file of the volume always pointed to a volume >> > that was also inside a storage pool. This would allow us to have >> > backing files pointing to volumes in different storage pools, but >> > would prevent them pointing to arbitrary files that were not in >> > storage pools at all (eg /etc/password, or /dev/root, etc). >> > >> >> That is good idea, but it won't cover all the cases, for example if >> you're not using storage pools. > >Yep, at least from OpenStack POV our goal is to switch 100% to using >storage pools. > >For non-storage pool deployments though, I think it is common that >the mgmt app will have a specific place where it will always put >disks. eg on OpenStack file based disks will always live under >/var/lib/nova/instances. > >So if there was a qemu.conf setting to whitelist allowed disk image >locations, we could lock down where we permit relabelling for the >openstack host as a whole, and not need to change anything on a per >guest basis. > I like the per-guest approach better, but qemu.conf is satisfactory enough, I guess. >> It could be nice to get feedback from upper mgmt layers, any idea where >> else to post this questions? > >ovirt might have feedback i guess > Cc'd ovirt-devel, even though I don't think they use it (or at least not yet). If you feel like it, don't hesitate to Cc appropriate OpenStack list as well (if that's not much cross-posting). Martin >Regards, >Daniel >-- >|: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :| >|: http://libvirt.org -o- http://virt-manager.org :| >|: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| >|: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :| --R3G7APHDIzY6R/pk Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- iQIcBAEBCAAGBQJXw/4jAAoJEAgfwp8kF4bdEV4P/1JP07oQ2ug+sGs5CImqbJak 6eajVCCcobapZgT7rDWbla5e2G5XMdzbV1vVzuIl2OVo4rGmcLuZjozVH8dewg0M tEjWLenbciXnUcqIrEA8PTP5qAdEAdVUZ/7kwFT3shRjTUOEYk46BM+fiRWz/pQM DI/xaPpXcZarfohLOGUgdRv+00shQPVZFg786FXBL+aYNFwTfbFDOnboYEYwKhq2 WGHG0PWLF3iIBlJWBFs4Nz1pQ48cw4CGWmXcOGtusIiqud5FsbKjNX+s64PDY1Yz 8UzC4c9+4LyqobUJp5EulsAmXedKK0bTxs4GI/eePkHZfBaRuOJtshbY2iETljsS Ce1s9Y3gpfP6UzAZImOa67F2rms9Fgv8Mm4pRnG2l/FTCvFSq7Grn8pPKL12jWAN Ti6hOQGCX45h8lN17zfERlWWPBFk3Mtw3L8bbh8Ja0xhYgsH0qS1mdeE/VmjKKFC OqZvT9GgtwFg4t77nHCIhFBSTEc3DoV6lNMrPxaTVswXCKSlYJAz2IUd8DFN5FFF 71WlKgvCKWl6iqo2FpxklhqfsUNSL6J31Kgh29r54qYcNZc1oobWsyJAqyeQcpER 3nHyY14QhIDc2LojcEisGXyPErtHZiVfexlB++Ap2O5W3tkxH08yWnV0Cd2J+CK2 MLB3K7JjrEt84oY8EGP8 =JNYW -----END PGP SIGNATURE----- --R3G7APHDIzY6R/pk--

1 0

Python code style: introducing isort
by Sandro Bonazzola 26 Aug '16

26 Aug '16

Hi, in project maintained by integration team we tried to adhere to some styling rules while writing python code, one of these was related to the import lines. After a lot of time doing this manually, we discovered isort ( https://pypi.python.org/pypi/isort/4.2.5 ) We're using it before we push our code to gerrit and a few days ago I sent a patch for the python code within ovirt-engine: https://gerrit.ovirt.org/61964 The configuration we're currently using is: $ cat ~/.isort.cfg [settings] line_length=79 known_standard_library=configparser,Cheetah.Template force_single_line=True default_section=FIRSTPARTY known_otopi=otopi known_host_deploy=ovirt_host_deploy known_ovirt_engine=ovirt_engine known_ovirt_engine_setup=ovirt_engine_setup known_ovirt_setup_lib=ovirt_setup_lib known_vdsm=vdsm known_ovirt_hosted_engine_setup=ovirt_hosted_engine_setup sections=FUTURE,STDLIB,FIRSTPARTY,OTOPI,VDSM,HOST_DEPLOY,OVIRT_ENGINE,OVIRT_ENGINE_SETUP,OVIRT_SETUP_LIB,OVIRT_HOSTED_ENGINE_SETUP,THIRDPARTY,LOCALFOLDER lines_between_types=2 It has been proposed to add 'isort --check-only' in check-patch.for python projects in addition to pep8 style checking. It has also been proposed to reach consensus on isort configuration so all the python code within ovirt project will have same styling. I'd like to get some feedback about these proposal in order to decide how to procede. Thanks, -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

2 3

otopi based program testing: coverage reports
by Sandro Bonazzola 26 Aug '16

26 Aug '16

The otopi 1.6.0 package currently in ovirt-master-snapshot includes a new feature that allows you to collect coverage reports from your executions. In order to enable the feature you'll need to provide a configuration file like: 8<-------------------------------------- [run] branch = True [report] exclude_lines = # Have to re-enable the standard pragma pragma: no cover # Don't complain about missing debug-only code: def __repr__ if self\.debug # Don't complain if tests don't hit defensive assertion code: raise AssertionError raise NotImplementedError # Don't complain if non-runnable code isn't run: if 0: if __name__ == .__main__.: ignore_errors = True 8<------------------------------------ Be sure to have python-coverage and libselinux-python installed on your system and then execute: OTOPI_COVERAGE=1 COVERAGE_PROCESS_START=<your config> <your command> where your config is the path to your config file and your command may be engine-setup, engine-cleanup, ovirt-host-deploy, hosted-engine --deploy or any other possible command which uses otopi framework. In order to generate the report: coverage html -d coverage_html_report This feature is already leveraged in otopi check-patches and check-merged jobs: http://jenkins.ovirt.org/search/?q=otopi_master_check More test jobs will possibly follow. New tests to improve coverage, improvements to the coverage configuration, suggestions, porting to other projects are welcome. -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

1 0

ovirt-image-upload fails with NFS error when using a local disk
by Lynn Dixon 25 Aug '16

25 Aug '16

Hey all, I am using oVirt 4.0 and trying to upload an OVA into my export domain using the ovirt-image-uploader tool. My Export domain is a local disk on the host, and is NOT using NFS. However, it seems the ovirt-image-uploader tool assumes my domain is NFS and it will give the following error: ERROR: mount.nfs: Failed to resolve server None: Name or service not known Is there a way to import OVA's in to the Export domain when its using a local disk? *Lynn Dixon* | Red Hat Certified Architect #100-006-188 *Sr. Cloud Consultant* | Cloud Management Practice Google Voice: 423-618-1414 Cell/Text: 423-774-3188 Click here to view my Certification Portfolio <http://red.ht/1XMX2Mi>

2 6

Fwd: Build failed in Jenkins: ovirt_3.6_he-system-tests #339
by Pavel Zhukov 23 Aug '16

23 Aug '16

Hi, Hosted engine is failed to install and for some reasons OST is not failed because of that. http://jenkins.ovirt.org/job/ovirt_3.6_he-system-tests/338/consoleFull *08:15:52* |- /var/lib/cloud/instance/scripts/runcmd: line 2: /usr/bin/engine-setup: No such file or directory *08:15:52* |- HE_APPLIANCE_ENGINE_SETUP_FAIL*08:15:52* [ ERROR ] Engine setup failed on the appliance*08:15:52* [ ERROR ] Failed to execute stage 'Closing up': Engine setup failed on the appliance Please check its log on the appliance. *08:15:52* [ INFO ] Stage: Clean up*08:15:53* [ INFO ] Generating answer file '/var/lib/ovirt-hosted-engine-setup/answers/answers-20160823041551.conf'*08:15:53* [ INFO ] Stage: Pre-termination*08:15:53* [ INFO ] Stage: Termination*08:15:53* [ ERROR ] Hosted Engine deployment failed: this system is not reliable, please check the issue, fix and redeploy ---------- Forwarded message ---------- From: <jenkins(a)jenkins.phx.ovirt.org> Date: Tue, Aug 23, 2016 at 2:30 PM Subject: Build failed in Jenkins: ovirt_3.6_he-system-tests #339 To: sbonazzo(a)redhat.com, infra(a)ovirt.org, lveyde(a)redhat.com See <http://jenkins.ovirt.org/job/ovirt_3.6_he-system-tests/339/changes> Changes: [Yaniv Kaul] Combine Engine and Storage VMs. ------------------------------------------ [...truncated 1228 lines...] ## rc = 1 ########################################################## ##! ERROR vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv ##! Last 20 log enties: logs/mocker-fedora-23-x86_64. fc23.he_basic_suite_3.6.sh/he_basic_suite_3.6.sh.log ##! + true + env_cleanup + echo '#########################' ######################### + local res=0 + local uuid + echo '======== Cleaning up' ======== Cleaning up + [[ -e <http://jenkins.ovirt.org/job/ovirt_3.6_he-system-tests/ws/ ovirt-system-tests/deployment-he_basic_suite_3.6> ]] + echo '----------- Cleaning with lago' ----------- Cleaning with lago + lago --workdir <http://jenkins.ovirt.org/job/ovirt_3.6_he-system-tests/ws/ ovirt-system-tests/deployment-he_basic_suite_3.6> destroy --yes --all-prefixes + echo '----------- Cleaning with lago done' ----------- Cleaning with lago done + [[ 0 != \0 ]] + echo '======== Cleanup done' ======== Cleanup done + exit 0 Took 2133 seconds =================================== ##! ##! ERROR ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ##!######################################################## ########################################################## Build step 'Execute shell' marked build as failure Performing Post build task... Match found for :.* : True Logical operation result is TRUE Running script : #!/bin/bash -xe echo 'shell_scripts/system_tests.collect_logs.sh' # # Required jjb vars: # version # VERSION=3.6 SUITE_TYPE= WORKSPACE="$PWD" OVIRT_SUITE="$SUITE_TYPE_suite_$VERSION" TESTS_LOGS="$WORKSPACE/ovirt-system-tests/exported-artifacts" rm -rf "$WORKSPACE/exported-artifacts" mkdir -p "$WORKSPACE/exported-artifacts" if [[ -d "$TESTS_LOGS" ]]; then mv "$TESTS_LOGS/"* "$WORKSPACE/exported-artifacts/" fi [ovirt_3.6_he-system-tests] $ /bin/bash -xe /tmp/ hudson8442885515320324019.sh + echo shell_scripts/system_tests.collect_logs.sh shell_scripts/system_tests.collect_logs.sh + VERSION=3.6 + SUITE_TYPE= + WORKSPACE=<http://jenkins.ovirt.org/job/ovirt_3.6_he-system-tests/ws/> + OVIRT_SUITE=3.6 + TESTS_LOGS=<http://jenkins.ovirt.org/job/ovirt_3.6_he- system-tests/ws/ovirt-system-tests/exported-artifacts> + rm -rf <http://jenkins.ovirt.org/job/ovirt_3.6_he-system-tests/339/ artifact/exported-artifacts> + mkdir -p <http://jenkins.ovirt.org/job/ovirt_3.6_he-system-tests/339/ artifact/exported-artifacts> + [[ -d <http://jenkins.ovirt.org/job/ovirt_3.6_he-system-tests/ws/ ovirt-system-tests/exported-artifacts> ]] + mv <http://jenkins.ovirt.org/job/ovirt_3.6_he-system-tests/ws/ ovirt-system-tests/exported-artifacts/lago_logs> < http://jenkins.ovirt.org/job/ovirt_3.6_he-system-tests/ws/ ovirt-system-tests/exported-artifacts/test_logs> < http://jenkins.ovirt.org/job/ovirt_3.6_he-system-tests/339/ artifact/exported-artifacts/> POST BUILD TASK : SUCCESS END OF POST BUILD TASK : 0 Match found for :.* : True Logical operation result is TRUE Running script : #!/bin/bash -xe echo "shell-scripts/mock_cleanup.sh" shopt -s nullglob WORKSPACE="$PWD" # Make clear this is the cleanup, helps reading the jenkins logs cat <<EOC _______________________________________________________________________ ####################################################################### # # # CLEANUP # # # ####################################################################### EOC # Archive the logs, we want them anyway logs=( ./*log ./*/logs ) if [[ "$logs" ]]; then tar cvzf exported-artifacts/logs.tgz "${logs[@]}" rm -rf "${logs[@]}" fi # stop any processes running inside the chroot failed=false mock_confs=("$WORKSPACE"/*/mocker*) # Clean current jobs mockroot if any for mock_conf_file in "${mock_confs[@]}"; do [[ "$mock_conf_file" ]] || continue echo "Cleaning up mock $mock_conf" mock_root="${mock_conf_file##*/}" mock_root="${mock_root%.*}" my_mock="/usr/bin/mock" my_mock+=" --configdir=${mock_conf_file%/*}" my_mock+=" --root=${mock_root}" my_mock+=" --resultdir=$WORKSPACE" #TODO: investigate why mock --clean fails to umount certain dirs sometimes, #so we can use it instead of manually doing all this. echo "Killing all mock orphan processes, if any." $my_mock \ --orphanskill \ || { echo "ERROR: Failed to kill orphans on $chroot." failed=true } mock_root="$(\ grep \ -Po "(?<=config_opts\['root'\] = ')[^']*" \ "$mock_conf_file" \ )" || : [[ "$mock_root" ]] || continue mounts=($(mount | awk '{print $3}' | grep "$mock_root")) || : if [[ "$mounts" ]]; then echo "Found mounted dirs inside the chroot $chroot. Trying to umount." fi for mount in "${mounts[@]}"; do sudo umount --lazy "$mount" \ || { echo "ERROR: Failed to umount $mount." failed=true } done done # Clean any leftover chroot from other jobs for mock_root in /var/lib/mock/*; do this_chroot_failed=false mounts=($(mount | awk '{print $3}' | grep "$mock_root")) || : if [[ "$mounts" ]]; then echo "Found mounted dirs inside the chroot $mock_root." \ "Trying to umount." fi for mount in "${mounts[@]}"; do sudo umount --lazy "$mount" \ || { echo "ERROR: Failed to umount $mount." failed=true this_chroot_failed=true } done if ! $this_chroot_failed; then sudo rm -rf "$mock_root" fi done if $failed; then echo "Aborting." exit 1 fi # remove mock system cache, we will setup proxies to do the caching and this # takes lots of space between runs shopt -u nullglob sudo rm -Rf /var/cache/mock/* # restore the permissions in the working dir, as sometimes it leaves files # owned by root and then the 'cleanup workspace' from jenkins job fails to # clean and breaks the jobs sudo chown -R "$USER" "$WORKSPACE" [ovirt_3.6_he-system-tests] $ /bin/bash -xe /tmp/ hudson2384388653446686967.sh + echo shell-scripts/mock_cleanup.sh shell-scripts/mock_cleanup.sh + shopt -s nullglob + WORKSPACE=<http://jenkins.ovirt.org/job/ovirt_3.6_he-system-tests/ws/> + cat _______________________________________________________________________ ####################################################################### # # # CLEANUP # # # ####################################################################### + logs=(./*log ./*/logs) + [[ -n ./ovirt-system-tests/logs ]] + tar cvzf exported-artifacts/logs.tgz ./ovirt-system-tests/logs ./ovirt-system-tests/logs/ ./ovirt-system-tests/logs/mocker-fedora-23-x86_64.fc23.install_packages/ ./ovirt-system-tests/logs/mocker-fedora-23-x86_64.fc23. install_packages/stdout_stderr.log ./ovirt-system-tests/logs/mocker-fedora-23-x86_64.fc23. install_packages/root.log ./ovirt-system-tests/logs/mocker-fedora-23-x86_64.fc23. install_packages/state.log ./ovirt-system-tests/logs/mocker-fedora-23-x86_64.fc23. install_packages/build.log ./ovirt-system-tests/logs/mocker-fedora-23-x86_64.fc23.he_ basic_suite_3.6.sh/ ./ovirt-system-tests/logs/mocker-fedora-23-x86_64.fc23. he_basic_suite_3.6.sh/he_basic_suite_3.6.sh.log ./ovirt-system-tests/logs/mocker-fedora-23-x86_64.fc23.init/ ./ovirt-system-tests/logs/mocker-fedora-23-x86_64.fc23. init/stdout_stderr.log ./ovirt-system-tests/logs/mocker-fedora-23-x86_64.fc23.init/root.log ./ovirt-system-tests/logs/mocker-fedora-23-x86_64.fc23.init/state.log ./ovirt-system-tests/logs/mocker-fedora-23-x86_64.fc23.init/build.log ./ovirt-system-tests/logs/mocker-fedora-23-x86_64.fc23.clean_rpmdb/ ./ovirt-system-tests/logs/mocker-fedora-23-x86_64.fc23. clean_rpmdb/stdout_stderr.log + rm -rf ./ovirt-system-tests/logs + failed=false + mock_confs=("$WORKSPACE"/*/mocker*) + for mock_conf_file in '"${mock_confs[@]}"' + [[ -n <http://jenkins.ovirt.org/job/ovirt_3.6_he-system-tests/ws/ ovirt-system-tests/mocker-fedora-23-x86_64.fc23.cfg> ]] + echo 'Cleaning up mock ' Cleaning up mock + mock_root=mocker-fedora-23-x86_64.fc23.cfg + mock_root=mocker-fedora-23-x86_64.fc23 + my_mock=/usr/bin/mock + my_mock+=' --configdir=<http://jenkins.ovirt.org/job/ovirt_3.6_he- system-tests/ws/ovirt-system-tests'> + my_mock+=' --root=mocker-fedora-23-x86_64.fc23' + my_mock+=' --resultdir=<http://jenkins.ovirt.org/job/ovirt_3.6_he- system-tests/ws/'> + echo 'Killing all mock orphan processes, if any.' Killing all mock orphan processes, if any. + /usr/bin/mock --configdir=<http://jenkins.ovirt.org/job/ovirt_3.6_he- system-tests/ws/ovirt-system-tests> --root=mocker-fedora-23-x86_64.fc23 --resultdir=<http://jenkins.ovirt.org/job/ovirt_3.6_he-system-tests/ws/> --orphanskill WARNING: Could not find required logging config file: < http://jenkins.ovirt.org/job/ovirt_3.6_he-system-tests/ws/ ovirt-system-tests/logging.ini.> Using default... INFO: mock.py version 1.2.17 starting (python version = 3.4.3)... Start: init plugins INFO: selinux enabled Finish: init plugins Start: run Finish: run ++ grep -Po '(?<=config_opts\['\''root'\''\] = '\'')[^'\'']*' < http://jenkins.ovirt.org/job/ovirt_3.6_he-system-tests/ws/ ovirt-system-tests/mocker-fedora-23-x86_64.fc23.cfg> + mock_root=fedora-23-x86_64-235bec7d0621e95d1cae73d7cf9dc27c + [[ -n fedora-23-x86_64-235bec7d0621e95d1cae73d7cf9dc27c ]] + mounts=($(mount | awk '{print $3}' | grep "$mock_root")) ++ mount ++ awk '{print $3}' ++ grep fedora-23-x86_64-235bec7d0621e95d1cae73d7cf9dc27c + : + [[ -n '' ]] + false + shopt -u nullglob + sudo rm -Rf /var/cache/mock/fedora-23-x86_64- 235bec7d0621e95d1cae73d7cf9dc27c + sudo chown -R jenkins <http://jenkins.ovirt.org/job/ ovirt_3.6_he-system-tests/ws/> POST BUILD TASK : SUCCESS END OF POST BUILD TASK : 1 Recording test results ERROR: Step ‘Publish JUnit test result report’ failed: No test report files were found. Configuration error? Archiving artifacts _______________________________________________ Infra mailing list Infra(a)ovirt.org http://lists.ovirt.org/mailman/listinfo/infra -- Pavel Zhukov Software Engineer RHEV Devops IRC: landgraf

2 1