Re: [ovirt-devel] Adding s390 support to oVirt

2017-11-26 Thread Dan Horák
sending once more for the s390x list ... On Fri, 24 Nov 2017 10:05:06 +0100 Viktor Mihajlovski wrote: > On 21.11.2017 11:26, Dan Horák wrote: > [...] > >> qemu s390x emulation does not work with code compiled for z12. > >> Would a real virtual machine be what you

Re: [ovirt-devel] Adding s390 support to oVirt

2017-11-26 Thread Barak Korren
On 24 November 2017 at 14:36, Dan Horák wrote: > > ok, I'm pretty sure we can make it work :-) Please send me your > public SSH key and preferred username, then I'll set up you an account > for you and we can work on the remaining details. > I would actually like two keys to be

Re: [ovirt-devel] oVirt CI now supports Fedora 27 and Fedora Rawhide

2017-11-26 Thread Eyal Edri
On Sat, Nov 25, 2017 at 12:32 PM, Barak Korren wrote: > On 24 November 2017 at 22:57, Dan Kenigsberg wrote: > > On Fri, Nov 24, 2017 at 1:46 PM, Barak Korren > wrote: > >> On 24 November 2017 at 13:27, Dan Kenigsberg

Re: [ovirt-devel] [ OST Failure Report ] [ oVirt master ] [ 23-11-2017 ] [ 001_initialize_engine.test_initialize_engine ]

2017-11-26 Thread Nir Soffer
I think we need to check and report which process is listening on a port when starting a server on that port fail. Didi, do you think we can integrate this in the deploy code, or this should be implemented in each server? Maybe when deployment fails, the deploy code can report all the listening

Re: [ovirt-devel] [ OST Failure Report ] [ oVirt master ] [ 23-11-2017 ] [ 001_initialize_engine.test_initialize_engine ]

2017-11-26 Thread Gal Ben Haim
We still see this issue on the upgrade suite from latest release to master [1]. I don't see any evidence in "/var/log/messages" [2] that "ovirt-imageio-proxy" was started twice. [1]

Re: [ovirt-devel] [ OST Failure Report ] [ oVirt master ] [ 23-11-2017 ] [ 001_initialize_engine.test_initialize_engine ]

2017-11-26 Thread Yaniv Kaul
On Sun, Nov 26, 2017 at 4:53 PM, Gal Ben Haim wrote: > We still see this issue on the upgrade suite from latest release to master > [1]. > I don't see any evidence in "/var/log/messages" [2] that > "ovirt-imageio-proxy" was started twice. > Since it's not a registered port

[ovirt-devel] Subject: [ OST Failure Report ] [ oVirt master ] [ 26.11.17 ] [ 001_initialize_engine ]

2017-11-26 Thread Gal Ben Haim
Suspected patches: https://gerrit.ovirt.org/#/c/84618/2 Link to Job: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/4158/ Link to all logs: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/4158/artifact/exported-artifacts/basic-suit-master-el7/ Error snippet from

Re: [ovirt-devel] [ OST Failure Report ] [ oVirt master ] [ 23-11-2017 ] [ 001_initialize_engine.test_initialize_engine ]

2017-11-26 Thread Gal Ben Haim
The failure is not consistent. On Sun, Nov 26, 2017 at 5:33 PM, Yaniv Kaul wrote: > > > On Sun, Nov 26, 2017 at 4:53 PM, Gal Ben Haim wrote: > >> We still see this issue on the upgrade suite from latest release to >> master [1]. >> I don't see any