- Devel - oVirt List Archives

ovirt-host-deploy and python3
by Tomáš Golembiovský 07 May '18

07 May '18

Hi, I'm trying to reinstall a CentOS host (using master-snapshot) and I noticed otopi is trying to use python3 while the ovirt-host-deploy is not yet fully python3 compatible: > 2018-05-03 21:35:56,855+0200 DEBUG otopi.plugins.otopi.system.info info._init:39 SYSTEM INFORMATION - BEGIN > 2018-05-03 21:35:56,855+0200 DEBUG otopi.plugins.otopi.system.info info._init:40 executable /bin/python3 > 2018-05-03 21:35:56,855+0200 DEBUG otopi.plugins.otopi.system.info info._init:41 python version 3.4.8 (default, Mar 23 2018, 10:04:27) > [GCC 4.8.5 20150623 (Red Hat 4.8.5-16)] > 2018-05-03 21:35:56,855+0200 DEBUG otopi.plugins.otopi.system.info info._init:42 python /bin/python3 > 2018-05-03 21:35:56,856+0200 DEBUG otopi.plugins.otopi.system.info info._init:43 platform linux > 2018-05-03 21:35:56,856+0200 DEBUG otopi.plugins.otopi.system.info info._init:44 distribution ('CentOS Linux', '7.4.1708', 'Core') > 2018-05-03 21:35:56,856+0200 DEBUG otopi.plugins.otopi.system.info info._init:45 host 'ovirt-host2' > 2018-05-03 21:35:56,856+0200 DEBUG otopi.plugins.otopi.system.info info._init:51 uid 0 euid 0 gid 0 egid 0 > 2018-05-03 21:35:56,856+0200 DEBUG otopi.plugins.otopi.system.info info._init:53 SYSTEM INFORMATION - END and then later: > 2018-05-03 21:35:56,912+0200 DEBUG otopi.context context._executeMethod:128 Stage init METHOD otopi.plugins.ovirt_host_deploy.node.detect.Plugin._init > 2018-05-03 21:35:56,914+0200 DEBUG otopi.context context._executeMethod:143 method exception > Traceback (most recent call last): > File "/tmp/ovirt-a0GNITSwX9/pythonlib/otopi/context.py", line 133, in _executeMethod > method['method']() > File "/tmp/ovirt-a0GNITSwX9/otopi-plugins/ovirt-host-deploy/node/detect.py", line 131, in _init > odeploycons.FileLocations.OVIRT_NODE_VARIANT_VAL) > File "/tmp/ovirt-a0GNITSwX9/otopi-plugins/ovirt-host-deploy/node/detect.py", line 69, in hasconf > io.StringIO('[default]\n' + f.read().decode('utf-8')) > AttributeError: 'str' object has no attribute 'decode' > 2018-05-03 21:35:56,915+0200 ERROR otopi.context context._executeMethod:152 Failed to execute stage 'Initializing': 'str' object has no attribute 'decode' There is definitely a bug (or at least weirdness) in host-deploy -- why use .decode() on object returned by codecs.open()? But also, should host-deploy be already python3 compatible and is this otopi behaviour expected? Tomas -- Tomáš Golembiovský <tgolembi(a)redhat.com>

6 12

oVirt RPC messages
by Anastasiya Ruzhanskaya 07 May '18

07 May '18

Hello! Do messages sent from ovirt-engine to ovirt-node in RPC format contain the session number or any user information?

2 3

dynamic ownership changes
by Martin Polednik 04 May '18

04 May '18

Hey, I've created a patch[0] that is finally able to activate libvirt's dynamic_ownership for VDSM while not negatively affecting functionality of our storage code. That of course comes with quite a bit of code removal, mostly in the area of host devices, hwrng and anything that touches devices; bunch of test changes and one XML generation caveat (storage is handled by VDSM, therefore disk relabelling needs to be disabled on the VDSM level). Because of the scope of the patch, I welcome storage/virt/network people to review the code and consider the implication this change has on current/future features. [0] https://gerrit.ovirt.org/#/c/89830/ mpolednik

8 25

Video and slides from the STDCI V2 talk
by Barak Korren 03 May '18

03 May '18

Video is available at: https://bluejeans.com/s/JQ2ES Slides are at: https://drive.google.com/file/d/1V1zPSdNicsiYXc3PX9iX5QkWLAqpCLYs/view As well as attached to this message. -- Barak Korren RHV DevOps team , RHCE, RHCi Red Hat EMEA redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted

1 0

Slides for STDCI V2 talk
by Barak Korren 02 May '18

02 May '18

Hi all, Attached are the slids I'm going to present in my talk about oVirt's STDCI V2. Regards, -- Barak Korren RHV DevOps team , RHCE, RHCi Red Hat EMEA redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted

1 0

Updated invitation: oVirt STDCI v2 deep dive @ Thu May 3, 2018 11:00 - 12:00 (IDT) (devel@ovirt.org)
by bkorren＠redhat.com 02 May '18

02 May '18

This event has been changed. Title: oVirt STDCI v2 deep dive Introduction to the 2nd version of oVirt's CI standard - What is it, what can it do, how to use it and how does it work.Note: Meeting was movedTo join the Meeting:https://bluejeans.com/8705030462To join via Room System:Video Conferencing System: redhat.bjn.vc -or-199.48.152.18Meeting ID : 8705030462To join via phone :1) Dial:    408-915-6466 (United States)    (see all numbers - https://www.redhat.com/en/conference-numbers)2) Enter Conference ID : 8705030462RSVP at:https://www.eventbrite.com/e/ovirt-stdci-v2-deep-dive-tickets-45468120372 (changed) When: Thu May 3, 2018 11:00 – 12:00 Jerusalem Where: ; https://bluejeans.com/8705030462, raanana-04-asia-8-p-vc Calendar: devel(a)ovirt.org Who: * bkorren(a)redhat.com - organizer * devel(a)ovirt.org * sbonazzo(a)redhat.com * dkenigsb(a)redhat.com * rbarry(a)redhat.com * mskrivan(a)redhat.com * eedri(a)redhat.com * tjelinek(a)redhat.com * tnisan(a)redhat.com * mperina(a)redhat.com * sradco(a)redhat.com * msivak(a)redhat.com * sabose(a)redhat.com Attachments: * ovirt-stdci-talk.pdf - https://drive.google.com/a/redhat.com/file/d/1V1zPSdNicsiYXc3PX9iX5QkWLAqpC… Event details: https://www.google.com/calendar/event?action=VIEW&eid=MHBvcmNoYWQ5YmtzNmlmd… Invitation from Google Calendar: https://www.google.com/calendar/ You are receiving this courtesy email at the account devel(a)ovirt.org because you are an attendee of this event. To stop receiving future updates for this event, decline this event. Alternatively you can sign up for a Google account at https://www.google.com/calendar/ and control your notification settings for your entire calendar. Forwarding this invitation could allow any recipient to modify your RSVP response. Learn more at https://support.google.com/calendar/answer/37135#forwarding

1 0

oVirt CI now supports Fedora 28
by Barak Korren 02 May '18

02 May '18

Since Fedora 28 was released yesterday, we've added support for it in the oVirt CI system. To use Fedora 28 just use 'fc28' as you would for other Fedora versions in the CI YAML files and/or file extensions in the 'automation/' directory. The synchronisation for our local mirror is ongoing at this time, so until it is done, the upstream Fedora mirrors will be used, this can cause some breakage. -- Barak Korren RHV DevOps team , RHCE, RHCi Red Hat EMEA redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted

1 0

Broken deps wihle testing master? Here some info
by Sandro Bonazzola 02 May '18

02 May '18

Hi, ovirt-release-master enables testing repos from CentOS. Testing repos are now switching to CentOS 7.5.1804 so you now need to enable also the CR repo when testing master on CentOS. CentOS 7.5 should be released this week or in worst case next week, so this is just a temporary issue while 7.5 is being rolled out. oVirt release 4.2 uses stable repos and is not affected by this temporary glitch. Thanks, -- SANDRO BONAZZOLA ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://red.ht/sig> <https://redhat.com/summit>

1 0

Re: [ovirt-devel] default maintainers plugin for other projects
by Barak Korren 02 May '18

02 May '18

(adding devel because this might be interesting for others). On 1 May 2018 at 21:16, Greg Sheremeta <gshereme(a)redhat.com> wrote: > How would I get this plugin added to ovirt-engine-dashboard and > ovirt-engine-node* ? > Its already available for all projects in gerrit.ovirt.org. > And then how would I configure it? (Add myself as a default, at least) > Two ways: With the GUI: ----------------- In Gerrit UI go to: Admin -> Projects -> (Old UI) -> (Your project) -> Reviewers (from top bar) Fill in filter (A file glob pattern - can be '*') and reviewer (An email address ora gerrit group ) and click "Add". Don't forget to switch back to new UI from the bottom right link. >From the command line ------------------------------- In a Git clone of the relevant project do: # git fetch origin refs/meta/config:meta-config # git checkout meta-config Then you can edit the 'reviewers.config' file (Make it if it isn't there) and put in something like the following: [filter "*"] reviewer = jenkins-maintainers reviewer = dron(a)redhat.com Once you're done with it commit the change and push it with: # git push -u origin meta-config refs/meta/config Since we have '-u' there, the next time around you change the 'meta-config' branch you can just do: # git push -u origin And that's about it. One thing to note - every project has a '<project-name>-maintainers' group, so its useful to add it it default. > ---------- Forwarded message ---------- > From: Roy Golan <rgolan(a)redhat.com> > Date: Mon, Jun 19, 2017 at 7:17 AM > Subject: Re: [ovirt-devel] [ENGINE][ACTION_NEEDED] - default maintainers, > per path > To: devel <devel(a)ovirt.org> > > > The patch is now merged and the it should start working immediately. For > anyone who is listed as a default reviewer I suggest to test it with a test > patch by some other submitter. (except for those who used groups of course) > > Thanks everyone for the cooperation on this. > > > On Mon, May 29, 2017 at 2:24 PM Roy Golan <rgolan(a)redhat.com> wrote: > >> Hi all, >> >> Some time ago the infra team enabled *gerrit default reviewer plugin* >> which you probably noticed if you logged in to gerrit. >> >> What we can do is for example set the stable branch maintainers per >> branch automatically: >> >> [filter "branch:ovirt-engine-4.1"] >> reviewer = stableBranchMaintainersGroup >> >> Put people based on path: >> >> [filter "branch:master file:^frontend/.*"] >> reviewer = j.r.r.t(a)shire.me >> >> >> >> *Action Needed:* >> Nominate yourself, or others, by amending this patch online [1]. Once >> this patch is fully acked and agreed we will merge it. If something can't >> get consensus we will defer it from the patch till maintainers agree. >> >> [1] https://gerrit.ovirt.org/#/c/77488/ >> >> >> >> >> > > _______________________________________________ > Devel mailing list > Devel(a)ovirt.org > http://lists.ovirt.org/mailman/listinfo/devel > > > > -- > > GREG SHEREMETA > > SENIOR SOFTWARE ENGINEER - TEAM LEAD - RHV UX > > Red Hat NA > > <https://www.redhat.com/> > > gshereme(a)redhat.com IRC: gshereme > <https://red.ht/sig> > > _______________________________________________ > Infra mailing list > Infra(a)ovirt.org > http://lists.ovirt.org/mailman/listinfo/infra > > -- Barak Korren RHV DevOps team , RHCE, RHCi Red Hat EMEA redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted

1 0

OST Failure - Weekly update [/04/2018-20/04/2018]
by Dafna Ron 30 Apr '18

30 Apr '18

Hi, I wanted to give a short status on this week's failures and OST current status. I am glad to report that the issue with CQ alerts was resolved thanks to Barak and Evgheni. You can read more about the issue and how it was resolved here: https://ovirt-jira.atlassian.net/browse/OVIRT-1974 Currently we have one on-going possible regression which was reported to the list and to Arik. the change reported: https://gerrit.ovirt.org/#/c/89852/ - examples: upload ova as a virtual machine template. you can view the details in this Jira: https://ovirt-jira.atlassian.net/browse/OFT-648 The majority of issues we had this week were failed-build artifacts for fc27. There were two different cases, one was reported to Francesco who was already working on a fix to the issue and the second started and resolved during the evening/night of Apr 26-27. You can see the Jira to these two issues here: https://ovirt-jira.atlassian.net/browse/OFT-605 https://ovirt-jira.atlassian.net/browse/OFT-612 There was an infra issue with Mirrors not being available for a few minutes. the issue was momentarily and was resolved on its own. https://ovirt-jira.atlassian.net/browse/OFT-606 *Below you can see the chart for this week's resolved issues but cause of failure:**Code* = regression of working components/functionalities *Infra* = infrastructure/OST Infrastructure/Lago related issues/Power outages *OST Tests* = package related issues, failed build artifacts *Below is a chart showing failures by suite type: * *Below is a chart showing failures by version type: * *Below you can see the number of reported failures by resolution status:* Thanks, Dafna

4 5