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

2017-11-27 Thread Allon Mureinik
Didi - we just saw a report of a similar failure on engine-4.1's OST. COuld you please backport these patches there too? On Mon, Nov 27, 2017 at 2:57 PM, Yedidyah Bar David wrote: > On Mon, Nov 27, 2017 at 10:38 AM, Yedidyah Bar David > wrote: > >> On Sun, Nov 26, 2017 at 7:24 PM, Nir Soffer w

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

2017-11-27 Thread Yedidyah Bar David
On Mon, Nov 27, 2017 at 10:38 AM, Yedidyah Bar David wrote: > On Sun, Nov 26, 2017 at 7:24 PM, Nir Soffer wrote: > > I think we need to check and report which process is listening on a port > > when starting a server on that port fail. > > How do you know that a server was "started on that port

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

2017-11-27 Thread Dafna Ron
I opened a bug for this issue: https://bugzilla.redhat.com/show_bug.cgi?id=1517764 On 11/26/2017 05:24 PM, Nir Soffer wrote: > 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

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

2017-11-27 Thread Yedidyah Bar David
On Sun, Nov 26, 2017 at 7:24 PM, Nir Soffer wrote: > I think we need to check and report which process is listening on a port > when starting a server on that port fail. How do you know that a server was "started on that port", and that if failed specifically because it failed to bind? There is

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
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 evidence in "/var/log/messages" [2] that >> "ov

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 and a high port, could

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] http://jenkins.ovirt.org/blue/rest/organizations/jenkins/pipelines/ovirt-master_change-queue-tester/runs/4153/nodes/

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

2017-11-24 Thread Dafna Ron
there were two different patches reported as failing cq today with the ovirt-imageio-proxy service failing to start. Here is the latest failure: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/4130/artifact On 11/23/2017 03:39 PM, Allon Mureinik wrote: > Daniel/Nir? > > On Thu, No

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

2017-11-23 Thread Dafna Ron
There was an issue with the mirrors and I see the patch merged 7 hours ago so its possible it was a late alert. On 11/23/2017 03:58 PM, Viktor Mihajlovski wrote: > On 23.11.2017 16:29, Dafna Ron wrote: >> Hi, >> >> We have a failing on test 001_initialize_engine.test_initialize_engine. >> >> This

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

2017-11-23 Thread Viktor Mihajlovski
On 23.11.2017 16:29, Dafna Ron wrote: > Hi, > > We have a failing on test 001_initialize_engine.test_initialize_engine. > > This is failing with error Failed to start service 'ovirt-imageio-proxy > > [...] > > http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/4055/artifact/ > The

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

2017-11-23 Thread Nir Soffer
On Thu, Nov 23, 2017 at 5:30 PM Dafna Ron wrote: > Hi, > > We have a failing on test 001_initialize_engine.test_initialize_engine. > > This is failing with error Failed to start service 'ovirt-imageio-proxy > Can your reproduce it? If fail with: Nov 23 07:30:47 lago-upgrade-from-release-suite-

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

2017-11-23 Thread Allon Mureinik
Daniel/Nir? On Thu, Nov 23, 2017 at 5:29 PM, Dafna Ron wrote: > Hi, > > We have a failing on test 001_initialize_engine.test_initialize_engine. > > This is failing with error Failed to start service 'ovirt-imageio-proxy > > > *Link and headline ofto suspected patches: * > > > * build: Make resul

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

2017-11-23 Thread Dafna Ron
Hi, We have a failing on test 001_initialize_engine.test_initialize_engine. This is failing with error Failed to start service 'ovirt-imageio-proxy ** *Link and headline ofto suspected patches: * *** build: Make resulting RPMs architecture-specific - https://gerrit.ovirt.org/#/c/84534/ Lin