[ovirt-devel] Re: Request for reviews - vdsm-tool update-volume

2018-11-11 Thread Germano Veit Michel
Hi,

I've finished developing the tools we would like to have to fix snapshot
related issues.

Piotr did an initial review in one of the patches, but there is still a lot
of reviewing that needs to be done. Could you please review this series?
https://gerrit.ovirt.org/#/q/topic:snapshot-tools
I'm specially concerned about 94366, I'm not sure that is the right way do
to that.

Note: there are some random CI failures on F28 that we are investigating in
a different mail thread* , so with every rebase 1 to 3 patches fail.
* [VDSM] TestMount.testSymlinkMount failing

Thanks



On Mon, Oct 8, 2018 at 4:43 PM Germano Veit Michel 
wrote:

> All passing CI and rebased to latest master.
> Reviews are welcome.
>
> On Tue, Sep 25, 2018 at 8:01 AM Germano Veit Michel 
> wrote:
>
>>
>>
>> On Tue, Sep 25, 2018 at 7:59 AM Dan Kenigsberg  wrote:
>>
>>>
>>>
>>> On Tue, Sep 25, 2018 at 12:49 AM Germano Veit Michel 
>>> wrote:
>>>


 On Mon, Sep 24, 2018 at 11:56 PM Dan Kenigsberg 
 wrote:

> On Mon, Sep 24, 2018 at 9:24 AM Germano Veit Michel <
> germ...@redhat.com> wrote:
> >
> > Hi,
> >
> > I'm working an a tool (vdsm-tool update-volume) to make modifying SD
> metadata easier and more importantly, safer. This is very useful to 
> recover
> from failed LSMs or snapshot issues.
> >
> > The plan is to use the VDSM API (modified by some of these patches)
> and add a tool (vdsm-tool) that talks to the API and modifies the volumes
> metadata as required by the user. Currently this is done manually, i.e.:
> looking at MD_XXX tags, doing dd, sed and then dd back to the storage. Any
> wrong argument (like a skip in place of a seek) can ruin the entire
> metadata, so this tool can be quite handy.
> >
> > The code is not necessarily 100% finished yet, but I've been testing
> this for some time and it seems ok from a functional point of view. I'm
> just not sure everything I did (especially inside VDSM, example 94366) is
> correct. Your comments on what can/should be improved are very welcome at
> this point. Please see this series and help reviewing it.
> >
> >
> https://gerrit.ovirt.org/#/q/topic:update-volume+(status:open+OR+status:merged)
> > https://gerrit.ovirt.org/#/c/93258/
>
> I am not a maintainer of vdsm.storage, but I can say that I'm missing
> a high-level description of the change that you are suggesting, and
> its motivation. When do you see a need to manually change the metadata
> of volumes? Shouldn't we fix the bug that causes this need?
>

 Ohh, sorry. I thought it was obvious. This is for snapshot related
 issues. These bugs have been present for a while, they are fixed but new
 ones come up. In the end downstream support is constantly manually
 repairing chains. This is why this tool is needed. Both to make those
 changes safer and to save time.


> I personally have a deep resentment to a "force" flags - not just
> here, but everywhere. It is never clear what is being forced. Some
> things cannot or should not be forced.
>

 Nir already suggested to remove the force flag. I don't mind, the idea
 was just to keep the old behavior the same if the force flag is not used.


>
> One last note: a CI+1 gives a positive psychological vibe to your
> reviewer.
>
 Yes, I know. Most of them have CI+1. They keep randomly failing on FC28
 (but EL7 succeeds) on every push.

>>>
>>> We used to have a regression in iproute on Fedora few weeks ago. a
>>> rebase on master may help. It is your responsibility to find why fc28
>>> fails, as we cannot merge a patch that does not pass there.
>>>
>>
>> Thanks, I'll rebase them. Hopefully thats it.
>>
>>
>>>
>>> And there is just one that is constantly failing, I even sent an email
 to this list ("Jenkins help") to try to better understand why, but no
 one replied yet. It seems to be complaining about an object not having a
 member, but the member is created at runtime (based on api schema).

>>>
___
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/devel@ovirt.org/message/R5PIDWACMJJ6CG4MM32NE2CVU25VRDPM/


[ovirt-devel] Re: [VDSM] TestMount.testSymlinkMount failing

2018-11-11 Thread Germano Veit Michel
On Fri, Nov 9, 2018 at 3:25 PM Germano Veit Michel 
wrote:

>
>
> On Wed, Nov 7, 2018 at 9:34 PM Nir Soffer  wrote:
>
>> On Wed, Nov 7, 2018 at 6:27 AM Germano Veit Michel 
>> wrote:
>>
>>> Hi,
>>>
>>> I have seen CI failing with some "random" errors which makes submitting
>>> a series of patches a bit annoying, as some patch always fails with some
>>> error, then next run another patch fails.
>>>
>>> One of these problems is TestMount.testSymlinkMount. Looks like its
>>> getting EBUSY when doing a rmdir. So probably something still using it?
>>>
>>> === FAILURES 
>>> ===
>>> __ TestMount.testSymlinkMount 
>>> __
>>>
>>> args = (,)
>>> kwargs = {}
>>>
>>> @wraps(f)
>>> def wrapper(*args, **kwargs):
>>> if cond:
>>> raise SkipTest(reason)
>>> >   return f(*args, **kwargs)
>>>
>>> testValidation.py:274:
>>> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
>>> _ _
>>> testValidation.py:333: in wrapper
>>> return f(*args, **kwargs)
>>> storage/mount_test.py:167: in testSymlinkMount
>>> m.umount()
>>> /usr/lib64/python2.7/contextlib.py:35: in __exit__
>>> self.gen.throw(type, value, traceback)
>>> testlib.py:218: in namedTemporaryDir
>>> shutil.rmtree(tmpDir)
>>> /usr/lib64/python2.7/shutil.py:261: in rmtree
>>> rmtree(fullname, ignore_errors, onerror)
>>> /usr/lib64/python2.7/shutil.py:270: in rmtree
>>> onerror(os.rmdir, path, sys.exc_info())
>>> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
>>> _ _
>>>
>>> path = '/var/tmp/tmpOYMiHx/mountpoint', ignore_errors = False
>>> onerror = 
>>>
>>> def rmtree(path, ignore_errors=False, onerror=None):
>>> """Recursively delete a directory tree.
>>>
>>> If ignore_errors is set, errors are ignored; otherwise, if onerror
>>> is set, it is called to handle the error with arguments (func,
>>> path, exc_info) where func is os.listdir, os.remove, or os.rmdir;
>>> path is the argument to that function that caused it to fail; and
>>> exc_info is a tuple returned by sys.exc_info().  If ignore_errors
>>> is false and onerror is None, an exception is raised.
>>>
>>> """
>>> if ignore_errors:
>>> def onerror(*args):
>>> pass
>>> elif onerror is None:
>>> def onerror(*args):
>>> raise
>>> try:
>>> if os.path.islink(path):
>>> # symlinks to directories are forbidden, see bug #1669
>>> raise OSError("Cannot call rmtree on a symbolic link")
>>> except OSError:
>>> onerror(os.path.islink, path, sys.exc_info())
>>> # can't continue even if onerror hook returns
>>> return
>>> names = []
>>> try:
>>> names = os.listdir(path)
>>> except os.error, err:
>>> onerror(os.listdir, path, sys.exc_info())
>>> for name in names:
>>> fullname = os.path.join(path, name)
>>> try:
>>> mode = os.lstat(fullname).st_mode
>>> except os.error:
>>> mode = 0
>>> if stat.S_ISDIR(mode):
>>> rmtree(fullname, ignore_errors, onerror)
>>> else:
>>> try:
>>> os.remove(fullname)
>>> except os.error, err:
>>> onerror(os.remove, fullname, sys.exc_info())
>>> try:
>>> >   os.rmdir(path)
>>> E   OSError: [Errno 16] Device or resource busy: 
>>> '/var/tmp/tmpOYMiHx/mountpoint'
>>>
>>> /usr/lib64/python2.7/shutil.py:268: OSError
>>> - Captured stderr call 
>>> -
>>> 2018-11-07 00:41:55,518 DEBUG (MainThread) [storage.Misc.excCmd] 
>>> /usr/bin/taskset --cpu-list 0-1 /sbin/mkfs.ext2 -F 
>>> /var/tmp/tmpOYMiHx/backing.img (cwd None) (commands:68)
>>> 2018-11-07 00:41:55,561 DEBUG (MainThread) [storage.Misc.excCmd] SUCCESS: 
>>>  = 'mke2fs 1.44.2 (14-May-2018)\n';  = 0 (commands:89)
>>> 2018-11-07 00:41:55,562 INFO  (MainThread) [storage.Mount] mounting 
>>> /var/tmp/tmpOYMiHx/link_to_image at /var/tmp/tmpOYMiHx/mountpoint 
>>> (mount:204)
>>> 2018-11-07 00:41:55,563 DEBUG (MainThread) [root] /usr/bin/taskset 
>>> --cpu-list 0-1 /usr/bin/mount -o loop /var/tmp/tmpOYMiHx/link_to_image 
>>> /var/tmp/tmpOYMiHx/mountpoint (cwd None) (commands:68)
>>> 2018-11-07 00:41:55,598 DEBUG (MainThread) [root] SUCCESS:  = '';  
>>> = 0 (commands:89)
>>> 2018-11-07 00:41:55,599 DEBUG (MainThread) [storage.Mount] 
>>> /var/tmp/tmpOYMiHx/mountpoint mounted: 0.03 seconds (utils:454)
>>> 2018-11-07 00:41:55,599 DEBUG (MainThread) [root] /usr/bin/taskset 
>>> --cpu-list 0-1 /sbin/udevadm settle --timeout=5 (cwd None) (commands:68)
>>> 2018-11-07 00:41:55,624 DEBUG (MainThread) 

[ovirt-devel] Re: [CQ ovirt master] [ovirt-engine] - not passing for 10 days

2018-11-11 Thread Dan Kenigsberg
On Sun, Nov 11, 2018 at 5:27 PM Eyal Edri  wrote:
>
>
>
> On Sun, Nov 11, 2018 at 5:24 PM Eyal Edri  wrote:
>>
>>
>>
>> On Sun, Nov 11, 2018 at 5:20 PM Dan Kenigsberg  wrote:
>>>
>>> On Sun, Nov 11, 2018 at 4:36 PM Ehud Yonasi  wrote:
>>> >
>>> > Hey,
>>> > I've seen that CQ Master is not passing ovirt-engine for 10 days and 
>>> > fails on test suite called restore_vm0_networking
>>> > here's a snap error regarding it:
>>> >
>>> > https://pastebin.com/7msEYqKT
>>> >
>>> > Link to a sample job with the error:
>>> >
>>> > http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/3/artifact/basic-suite.el7.x86_64/004_basic_sanity.py.junit.xml
>>>
>>> I cannot follow this link because I'm 4 minutes too late
>>>
>>> jenkins.ovirt.org uses an invalid security certificate. The
>>> certificate expired on November 11, 2018, 5:13:25 PM GMT+2. The
>>> current time is November 11, 2018, 5:17 PM.
>>
>>
>> Yes, we're looking into that issue now.
>
>
> Fixed, you should be able to access it now.

OST fails during restore_vm0_networking in line 101 of
004_basic_sanity.py while comparing
vm_service.get().status == state

It seems that instead of reporting back the VM status, Engine set garbage
"The response content type 'text/html; charset=iso-8859-1' isn't the
expected XML"

I do not know what could cause that, and engine.log does not mention
it. But it seems like a problem in engine API hence +Martin Perina and
+Ondra Machacek .



>
>>
>>
>>
>>>
>>>
>>> >
>>> > Can some1 have a look at it and help to resolve the issue?
>>> >
>>> >
>>> > ___
>>> > Infra mailing list -- in...@ovirt.org
>>> > To unsubscribe send an email to infra-le...@ovirt.org
>>> > Privacy Statement: https://www.ovirt.org/site/privacy-policy/
>>> > oVirt Code of Conduct: 
>>> > https://www.ovirt.org/community/about/community-guidelines/
>>> > List Archives: 
>>> > https://lists.ovirt.org/archives/list/in...@ovirt.org/message/ZQAYWTLZJKGPJ25F33E6ICVDXQDYSKSQ/
>>> ___
>>> Devel mailing list -- devel@ovirt.org
>>> To unsubscribe send an email to devel-le...@ovirt.org
>>> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
>>> oVirt Code of Conduct: 
>>> https://www.ovirt.org/community/about/community-guidelines/
>>> List Archives: 
>>> https://lists.ovirt.org/archives/list/devel@ovirt.org/message/R5LOJH73XCLLFOUTKPM5GUCS6PNNKGTE/
>>
>>
>>
>> --
>>
>> Eyal edri
>>
>>
>> MANAGER
>>
>> RHV/CNV DevOps
>>
>> EMEA VIRTUALIZATION R
>>
>>
>> Red Hat EMEA
>>
>> TRIED. TESTED. TRUSTED.
>> phone: +972-9-7692018
>> irc: eedri (on #tlv #rhev-dev #rhev-integ)
>
>
>
> --
>
> Eyal edri
>
>
> MANAGER
>
> RHV/CNV DevOps
>
> EMEA VIRTUALIZATION R
>
>
> Red Hat EMEA
>
> TRIED. TESTED. TRUSTED.
> phone: +972-9-7692018
> irc: eedri (on #tlv #rhev-dev #rhev-integ)
___
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/devel@ovirt.org/message/DA6Q5RE5JO3FYIKN2QLKLWMCUBQA2HBX/


[ovirt-devel] Re: amount of reports by abrt

2018-11-11 Thread Piotr Kliczewski
niedz., 11 lis 2018, 15:26: Nir Soffer  napisał(a):

> On Sat, Nov 10, 2018 at 8:19 PM Piotr Kliczewski <
> piotr.kliczew...@gmail.com> wrote:
>
>> I attended a talk about abrt and noticed there are good number of reports
>> [1] generated by issues in ovirt.
>>
>
> Interesting, but does not seem very useful now.
>
> For example this issue:
> https://retrace.fedoraproject.org/faf/reports/1800689/
>
> https://retrace.fedoraproject.org/faf/problems/bthash/?bth=78aadb337727a80e425738f897ce652408ee396d=f9f894ff896f63455df6175635c7ec441cab225
>
> 11103922 reports for ovirt-imageio-daemon 1.0.0
> 6501 repots for ovirt-imageio-daemon 1.1.0
>
> But there is no info about this error, except the name of the exception
> NoSectionError
> Which means code tried to access non-existing section in a config file.
>
> The current version of imageio is 1.4.5, and the version released with
> 4.2.0 was 1.3 or 1.4, so this whatever this issue was, it is not relevant
> for long time.
>
> This could be more relevant if we could get mail about reports when they
> are submitted to the system. Do you know how we can configure the
> system to make the reports more useful?
>

Not sure but will ask about email notifications and if there is a way to
remove old, not vaild reports.


> Nir
>
___
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/devel@ovirt.org/message/YXBDKKPUZAFAPJUREPB7J5PP4YZVIRLG/


[ovirt-devel] Re: [CQ ovirt master] [ovirt-engine] - not passing for 10 days

2018-11-11 Thread Eyal Edri
On Sun, Nov 11, 2018 at 5:24 PM Eyal Edri  wrote:

>
>
> On Sun, Nov 11, 2018 at 5:20 PM Dan Kenigsberg  wrote:
>
>> On Sun, Nov 11, 2018 at 4:36 PM Ehud Yonasi  wrote:
>> >
>> > Hey,
>> > I've seen that CQ Master is not passing ovirt-engine for 10 days and
>> fails on test suite called restore_vm0_networking
>> > here's a snap error regarding it:
>> >
>> > https://pastebin.com/7msEYqKT
>> >
>> > Link to a sample job with the error:
>> >
>> >
>> http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/3/artifact/basic-suite.el7.x86_64/004_basic_sanity.py.junit.xml
>>
>> I cannot follow this link because I'm 4 minutes too late
>>
>> jenkins.ovirt.org uses an invalid security certificate. The
>> certificate expired on November 11, 2018, 5:13:25 PM GMT+2. The
>> current time is November 11, 2018, 5:17 PM.
>>
>
> Yes, we're looking into that issue now.
>

Fixed, you should be able to access it now.


>
>
>
>>
>> >
>> > Can some1 have a look at it and help to resolve the issue?
>> >
>> >
>> > ___
>> > Infra mailing list -- in...@ovirt.org
>> > To unsubscribe send an email to infra-le...@ovirt.org
>> > Privacy Statement: https://www.ovirt.org/site/privacy-policy/
>> > oVirt Code of Conduct:
>> https://www.ovirt.org/community/about/community-guidelines/
>> > List Archives:
>> https://lists.ovirt.org/archives/list/in...@ovirt.org/message/ZQAYWTLZJKGPJ25F33E6ICVDXQDYSKSQ/
>> ___
>> Devel mailing list -- devel@ovirt.org
>> To unsubscribe send an email to devel-le...@ovirt.org
>> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
>> oVirt Code of Conduct:
>> https://www.ovirt.org/community/about/community-guidelines/
>> List Archives:
>> https://lists.ovirt.org/archives/list/devel@ovirt.org/message/R5LOJH73XCLLFOUTKPM5GUCS6PNNKGTE/
>>
>
>
> --
>
> Eyal edri
>
>
> MANAGER
>
> RHV/CNV DevOps
>
> EMEA VIRTUALIZATION R
>
>
> Red Hat EMEA 
>  TRIED. TESTED. TRUSTED. 
> phone: +972-9-7692018
> irc: eedri (on #tlv #rhev-dev #rhev-integ)
>


-- 

Eyal edri


MANAGER

RHV/CNV DevOps

EMEA VIRTUALIZATION R


Red Hat EMEA 
 TRIED. TESTED. TRUSTED. 
phone: +972-9-7692018
irc: eedri (on #tlv #rhev-dev #rhev-integ)
___
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/devel@ovirt.org/message/JRIPHKR77YLJWRXBPDA43L7AYJELTBJZ/


[ovirt-devel] Re: [CQ ovirt master] [ovirt-engine] - not passing for 10 days

2018-11-11 Thread Eyal Edri
On Sun, Nov 11, 2018 at 5:20 PM Dan Kenigsberg  wrote:

> On Sun, Nov 11, 2018 at 4:36 PM Ehud Yonasi  wrote:
> >
> > Hey,
> > I've seen that CQ Master is not passing ovirt-engine for 10 days and
> fails on test suite called restore_vm0_networking
> > here's a snap error regarding it:
> >
> > https://pastebin.com/7msEYqKT
> >
> > Link to a sample job with the error:
> >
> >
> http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/3/artifact/basic-suite.el7.x86_64/004_basic_sanity.py.junit.xml
>
> I cannot follow this link because I'm 4 minutes too late
>
> jenkins.ovirt.org uses an invalid security certificate. The
> certificate expired on November 11, 2018, 5:13:25 PM GMT+2. The
> current time is November 11, 2018, 5:17 PM.
>

Yes, we're looking into that issue now.



>
> >
> > Can some1 have a look at it and help to resolve the issue?
> >
> >
> > ___
> > Infra mailing list -- in...@ovirt.org
> > To unsubscribe send an email to infra-le...@ovirt.org
> > Privacy Statement: https://www.ovirt.org/site/privacy-policy/
> > oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> > List Archives:
> https://lists.ovirt.org/archives/list/in...@ovirt.org/message/ZQAYWTLZJKGPJ25F33E6ICVDXQDYSKSQ/
> ___
> Devel mailing list -- devel@ovirt.org
> To unsubscribe send an email to devel-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
> https://lists.ovirt.org/archives/list/devel@ovirt.org/message/R5LOJH73XCLLFOUTKPM5GUCS6PNNKGTE/
>


-- 

Eyal edri


MANAGER

RHV/CNV DevOps

EMEA VIRTUALIZATION R


Red Hat EMEA 
 TRIED. TESTED. TRUSTED. 
phone: +972-9-7692018
irc: eedri (on #tlv #rhev-dev #rhev-integ)
___
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/devel@ovirt.org/message/R4XF3Q7LLLJZZXBUBJG2VT5O3SDFBNY5/


[ovirt-devel] Re: [CQ ovirt master] [ovirt-engine] - not passing for 10 days

2018-11-11 Thread Dan Kenigsberg
On Sun, Nov 11, 2018 at 4:36 PM Ehud Yonasi  wrote:
>
> Hey,
> I've seen that CQ Master is not passing ovirt-engine for 10 days and fails on 
> test suite called restore_vm0_networking
> here's a snap error regarding it:
>
> https://pastebin.com/7msEYqKT
>
> Link to a sample job with the error:
>
> http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/3/artifact/basic-suite.el7.x86_64/004_basic_sanity.py.junit.xml

I cannot follow this link because I'm 4 minutes too late

jenkins.ovirt.org uses an invalid security certificate. The
certificate expired on November 11, 2018, 5:13:25 PM GMT+2. The
current time is November 11, 2018, 5:17 PM.

>
> Can some1 have a look at it and help to resolve the issue?
>
>
> ___
> Infra mailing list -- in...@ovirt.org
> To unsubscribe send an email to infra-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
> oVirt Code of Conduct: 
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives: 
> https://lists.ovirt.org/archives/list/in...@ovirt.org/message/ZQAYWTLZJKGPJ25F33E6ICVDXQDYSKSQ/
___
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/devel@ovirt.org/message/R5LOJH73XCLLFOUTKPM5GUCS6PNNKGTE/


[ovirt-devel] [CQ ovirt master] [ovirt-engine] - not passing for 10 days

2018-11-11 Thread Ehud Yonasi
Hey,
I've seen that CQ Master is not passing ovirt-engine for 10 days and fails
on test suite called restore_vm0_networking
here's a snap error regarding it:

https://pastebin.com/7msEYqKT

Link to a sample job with the error:

http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/3/artifact/basic-suite.el7.x86_64/004_basic_sanity.py.junit.xml

Can some1 have a look at it and help to resolve the issue?
___
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/devel@ovirt.org/message/ZQAYWTLZJKGPJ25F33E6ICVDXQDYSKSQ/


[ovirt-devel] Re: amount of reports by abrt

2018-11-11 Thread Nir Soffer
On Sat, Nov 10, 2018 at 8:19 PM Piotr Kliczewski 
wrote:

> I attended a talk about abrt and noticed there are good number of reports
> [1] generated by issues in ovirt.
>

Interesting, but does not seem very useful now.

For example this issue:
https://retrace.fedoraproject.org/faf/reports/1800689/
https://retrace.fedoraproject.org/faf/problems/bthash/?bth=78aadb337727a80e425738f897ce652408ee396d=f9f894ff896f63455df6175635c7ec441cab225

11103922 reports for ovirt-imageio-daemon 1.0.0
6501 repots for ovirt-imageio-daemon 1.1.0

But there is no info about this error, except the name of the exception
NoSectionError
Which means code tried to access non-existing section in a config file.

The current version of imageio is 1.4.5, and the version released with
4.2.0 was 1.3 or 1.4, so this whatever this issue was, it is not relevant
for long time.

This could be more relevant if we could get mail about reports when they
are submitted to the system. Do you know how we can configure the
system to make the reports more useful?

Nir
___
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/devel@ovirt.org/message/UBYRSESHFTYU3D5BDH5RQOPR7IXGSHHM/


[ovirt-devel] Re: amount of reports by abrt

2018-11-11 Thread Piotr Kliczewski
niedz., 11 lis 2018, 09:16: Dan Kenigsberg  napisał(a):

> On Sat, Nov 10, 2018 at 8:19 PM Piotr Kliczewski
>  wrote:
> >
> > I attended a talk about abrt and noticed there are good number of
> reports [1] generated by issues in ovirt.
>
>
> Did they teach how to read these reports?
> Can you tell what is the 10 most common exceptions occurring in oVirt
> context?
>

Yes, please take a look at [1]. There are good numbers of reports for ovirt
components some with many millions occurrances over several years.


> >
> > Thanks,
> > Piotr
> >
> > [1] https://retrace.fedoraproject.org/faf/reports/
> > ___
> > Devel mailing list -- devel@ovirt.org
> > To unsubscribe send an email to devel-le...@ovirt.org
> > Privacy Statement: https://www.ovirt.org/site/privacy-policy/
> > oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> > List Archives:
> https://lists.ovirt.org/archives/list/devel@ovirt.org/message/EECX2SVR4Q4TG4BWZWZCTKIC335ZH6CH/
>
___
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/devel@ovirt.org/message/BZAPTSER5UJVEVCI2LAP5VCADFCEGDXG/


[ovirt-devel] Re: amount of reports by abrt

2018-11-11 Thread Dan Kenigsberg
On Sat, Nov 10, 2018 at 8:19 PM Piotr Kliczewski
 wrote:
>
> I attended a talk about abrt and noticed there are good number of reports [1] 
> generated by issues in ovirt.


Did they teach how to read these reports?
Can you tell what is the 10 most common exceptions occurring in oVirt context?

>
> Thanks,
> Piotr
>
> [1] https://retrace.fedoraproject.org/faf/reports/
> ___
> Devel mailing list -- devel@ovirt.org
> To unsubscribe send an email to devel-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
> oVirt Code of Conduct: 
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives: 
> https://lists.ovirt.org/archives/list/devel@ovirt.org/message/EECX2SVR4Q4TG4BWZWZCTKIC335ZH6CH/
___
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/devel@ovirt.org/message/Z4NPNTMRSJJV2OM7BLRIYEHXRT7JB7JU/