Re: [ovirt-devel] alerts in webadmin UI

On Mon, Nov 27, 2017 at 9:22 PM, Greg Sheremeta wrote: > Hi, > > If you create new "alert" messages in the webadmin UI, or you are working > near some code that has an alert, please use the PatternFly alert widget > instead of rendering a plain (or red) label. > > Example: >

[ovirt-devel] alerts in webadmin UI

Hi, If you create new "alert" messages in the webadmin UI, or you are working near some code that has an alert, please use the PatternFly alert widget instead of rendering a plain (or red) label. Example: http://www.patternfly.org/pattern-library/communication/inline-notifications/ Widget:

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

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

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

I doubt that patch has anything to do with ovirt-imageio not starting. Daniel/Nir - any insight? On Mon, Nov 27, 2017 at 5:11 PM, Dafna Ron wrote: > *Hi, * > > * We have a failure reported in ovirt 4.1 on ovirt-imageio not starting > and causing initialize_engine to fail I am

[ovirt-devel] [ OST Failure Report ] [ oVirt 4.1 ] [ 27-11-2017] [ 001_initialize_engine.test_initialize_engine ]

** *Hi*, ** * ** We have a failure reported in ovirt 4.1**on ovirt-imageio not starting and causing initialize_engine to fail I am not sure the reported patch is related**but it was reported by cq as the cause of the failure. Link and headline of suspected patches: Renamed

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

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

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

On Mon, Nov 27, 2017 at 2:30 PM, Allon Mureinik wrote: > The analysis is completely wrong. > > The offending patch is [1]. I assume the reason for the failure is that > gap between when the CI passed (Nov 21) and when it was merged (Nov 26). In > the five days in between,

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

The analysis is completely wrong. The offending patch is [1]. I assume the reason for the failure is that gap between when the CI passed (Nov 21) and when it was merged (Nov 26). In the five days in between, other patches entered master and invalidated this CI result. To quote the job's log: """

[ovirt-devel] Adding internal links

Hi, Quick request about adding links to pages on the ovirt site If you happen to be adding links that point to another page on ovirt.org or even to a different section on the same page, please remember to include the *complete relative URL*. For example: In the oVirt quick start guide

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

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

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

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

Re: [ovirt-devel] [rhev-tech] Correct way to import hooking?

On Sat, Nov 25, 2017 at 1:56 AM, Nir Soffer wrote: > On Fri, Nov 24, 2017 at 5:34 PM Piotr Kliczewski > wrote: >> >> On Fri, Nov 24, 2017 at 4:00 PM, Piotr Kliczewski >> wrote: >> > On Fri, Nov 24, 2017 at 2:20 PM, Nir