December 2018 - Devel - oVirt List Archives

Questions for Redhat team
by Suchitra Herwadkar 13 Dec '18

13 Dec '18

Hi Nir & RedHat team 1. Cloned VM support in RHV. There are two types of clones as per my understanding 1. Full Cloned VM: Independent copy of a virtual machine that shares nothing with the parent template after the cloning operation. 2. Dependent Cloned VM: It is a copy of a virtual machine that shares virtual disks with the parent template. This type of clone is made from a snapshot of the parent which is qcow2 image. All files available on the parent at the moment of the snapshot continue to remain available to the linked clone. Ongoing changes to the virtual disk of the parent do not affect the linked clone, and changes to the disk of the linked clone do not affect the parent. We want to know what the customer preference ( 1 or 2) as both have pros & cons. What is the guidance given by RHV around this? How do we recommend customers to patch the template disks when multiple VMs are cloned from it? Kindly provide more details. 1. Is there a way to we can mount a QCOW2 image using QCOW2 mounter and have a block level view of the data ? We read about libguestfs but this is filesystem view. 1. We would like to know when we can expect “Allocation Regions API” . I’m referring to https://bugzilla.redhat.com/show_bug.cgi?id=1622946 This is marked for 4.3 at this point in time. I presume we will get it as part of 4.2.X release as well. Kindly confirm ? Thanks Suchitra From: pchavva(a)redhat.com When: 8:30 PM - 9:00 PM December 13, 2018 Subject: [EXTERNAL] Canceled event: RHV- Veritas Netbackup Weekly Sync @ Thu Dec 13, 2018 10am - 10:30am (EST) (suchitra.herwadkar(a)veritas.com) This event has been canceled. RHV- Veritas Netbackup Weekly Sync When Thu Dec 13, 2018 10am – 10:30am Eastern Time - New York Calendar suchitra.herwadkar(a)veritas.com Who • pchavva(a)redhat.com - organizer • mahesh.falmari(a)veritas.com • abhay.marode(a)veritas.com • nsoffer(a)redhat.com • ketan.pachpande(a)veritas.com • tnisan(a)redhat.com • sudhakar.paulzagade(a)veritas.com • suchitra.herwadkar(a)veritas.com • navin.tah(a)veritas.com • ehowriga(a)redhat.com • james.olson(a)veritas.com • adbarbos(a)redhat.com - optional • renee.carlisle(a)veritas.com - optional Agenda: This Engineering weekly sync will cover the engagement activity for Netbackup and RHV integration. To join the Meeting: https://bluejeans.com/5723877297<https://www.google.com/url?q=https%3A%2F%2Fbluejeans.com%2F5723877297&sa=D&…> To join via Room System: Video Conferencing System: <https://www.google.com/url?q=http%3A%2F%2Fredhat.bjn.vc&sa=D&ust=1545134436…> redhat.bjn.vc<https://www.google.com/url?q=http%3A%2F%2Fredhat.bjn.vc&sa=D&ust=1545134436…> -or-199.48.152.18 Meeting ID : 5723877297 To join via phone : 1) Dial: 408-915-6466 (United States) (see all numbers - <https://www.google.com/url?q=https%3A%2F%2Fwww.redhat.com%2Fen%2Fconference…> https://www.redhat.com/en/conference-numbers<https://www.google.com/url?q=https%3A%2F%2Fwww.redhat.com%2Fen%2Fconference…>) 2) Enter Conference ID : 5723877297 Invitation from Google Calendar<https://www.google.com/calendar/> You are receiving this courtesy email at the account suchitra.herwadkar(a)veritas.com 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<https://support.google.com/calendar/answer/37135#forwarding>.

2 1

Announcing 'COVERAGE' option in OST
by Marcin Sobczyk 13 Dec '18

13 Dec '18

Hi, I've been working on adding coverage report for VDSM in OST recently, and I'm happy to announce, that the first batch of patches is merged! To run a suite with coverage, look for 'COVERAGE' drop-down on OST's build parameters page. If you run OST locally, pass a '--coverage' argument to 'run_suite.sh'. Currently, coverage works only for VDSM in basic-suite-master, but adding VDSM support for other suites is now a no-brainer. More patches are on the way! Since the option is named 'COVERAGE', and not 'VDSM_COVERAGE', other projects are welcome to implement their coverage reports on top of it. Cheers, Marcin

9 8

ovirt-system-tests_compat-4.2-suite-master is failing since November 27
by Sandro Bonazzola 12 Dec '18

12 Dec '18

hi, ovirt-system-tests_compat-4.2-suite-master is failing since November 27 with following error: Error: Fault reason is "Operation Failed". Fault detail is "[Bond name 'bond_fancy0' does not follow naming criteria. For host compatibility version 4.3 or greater, custom bond names must begin with the prefix 'bond' followed by 'a-z', 'A-Z', '0-9', or '_' characters. For host compatibility version 4.2 and lower, custom bond names must begin with the prefix 'bond' followed by a number.]". HTTP response code is 400. I think that if the scope of the test is to check that 4.2 still works with 4.3 engine, bond_fancy0 works for 4.3 but it's clearly not good for 4.2 and the test needs a fix. -- SANDRO BONAZZOLA MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://red.ht/sig>

6 11

Request for reviews
by Germano Veit Michel 11 Dec '18

11 Dec '18

Hi, I would like to have these 2 trivial changes reviewed and merged in time for 4.3 vdsm. Please have a look: https://gerrit.ovirt.org/#/q/topic:dump-volume-chains+(status:open+OR+statu… Thanks, Germano

1 0

v2v: -o rhv-upload: Upload via NBD
by Nir Soffer 11 Dec '18

11 Dec '18

I posted this patch for vdsm, adding NBD APIs: https://gerrit.ovirt.org/c/96079/ The main purpose of these APIs are enabling incremental restore, but they also enable a more efficient rhv-upload via NBD, and importing to thin disks, which is not possible with current solution. The same idea can work for KubeVirt or other targets, minimizing specific target code. Here is how rhv-upload can work using NBD: 1. rhv-upload plugin separated to pre and post scripts - pre - prepare disk and start image transfer - post - finialize image transfer, create vm, etc. 2. rhr-upload-pre plugin create a transfer with transport="nbd" POST /imagetransfers <image_transfer> <disk id="123"/> <direction>upload</direction> <format>raw</format> <transport>nbd</transport> </image_transfer> Engine does not implement <transport> yet, but this should be an easy change. This will use the new NBD APIs to export the disk using NBD over unix socket. We can support later also NBD over TLS/PSK. Engine will return NBD url in transfer_url: <transfer_url>nbd:unix:/run/vdsm/nbd/<transfer_uuid>.sock</tansfer_url> 3. v2v use the trasfer_url to start qem-img with the NBD server: nbdkit (vddk) -> qemu-img convert -> qemu-nbd Note that nbdkit is removed from the rhv side of the pipeline. This is expected to improve the throughput significantly, since imageio is not very good with lot of small requests generated by qemu-img. 4. rhv-upload-post script invoked to complete the transfer What do you think? Nir

2 2

[VDSM] Incremental backup - vdsm NBD APIs
by Nir Soffer 11 Dec '18

11 Dec '18

I posted patches for vdsm new NBD APIs: https://gerrit.ovirt.org/q/topic:nbd+project:vdsm For the big picture, see the feature page: https://ovirt.org/develop/release-management/features/storage/incremental-b… Changes: - Adding option to run a service as user:group https://gerrit.ovirt.org/c/96077 - Adding back support for systemd-run and systemctl_stop to supervdsm. https://gerrit.ovirt.org/c/96078 - Introducing the NBD APIs https://gerrit.ovirt.org/c/96079 - Starting nbd module tests https://gerrit.ovirt.org/c/96080 - Allow running tests that need supervdsm on your laptop https://gerrit.ovirt.org/c/96081 The infrastructure changes may be useful for other maintainers. Please review, Nir

1 1

ovirt-engine has been tagged (ovirt-engine-4.2.8.1)
by Tal Nisan 10 Dec '18

10 Dec '18

1 0

vdsm has been tagged (v4.20.45)
by Milan Zamazal 10 Dec '18

10 Dec '18

1 0

Lago v0.45 Release Announcement
by Gal Ben Haim 09 Dec '18

09 Dec '18

Hi All, On behalf of the Lago team, I'm pleased to announce Lago v0.45 is available! For a detailed release announcement please refer to our Github page at: https://github.com/lago-project/lago/releases/tag/0.45 Resources ========== Lago Docs: http://lago.readthedocs.io/en/latest/ GitHub: https://github.com/lago-project/lago/ YUM Repository: http://resources.ovirt.org/repos/lago/stable/0.0/rpm/ Pypi: https://pypi.python.org/pypi/lago Docker Hub: https://hub.docker.com/r/lagoproject/lago/ Changelog: https://lago.readthedocs.io/en/latest/_static/ChangeLog.txt As always, if you find any problems, or willing to contribute, visit our GitHub page. Enjoy! -- *GAL BEN HAIM* RHV DEVOPS -- *GAL bEN HAIM* RHV DEVOPS

1 0

[Ovirt] [CQ weekly status] [07-12-2018]
by Dafna Ron 07 Dec '18

07 Dec '18

Hi, This mail is to provide the current status of CQ and allow people to review status before and after the weekend. Please refer to below colour map for further information on the meaning of the colours. *CQ-4.2*: YELLOW (#1) The main issues were packaging issues 1. we needed to replace the 7.6 image due to segmentation faults during add_host. 2. missing dependencies for qemu-kvm-ev - fixed with patch: https://gerrit.ovirt.org/#/c/96055/ *CQ-Master:* YELLOW (#1) 1. we needed to replace the 7.6 image due to segmentation faults during add_host (same as 4.2) 2. vdsm project moved to STDCI v2 which caused failures due to check-patch job which has been failing for a while. although it created failures, vdsm still continued running the V1 jobs which meant tested repo still had updated vdsm packages. Happy week! Dafna ------------------------------------------------------------------------------------------------------------------- COLOUR MAP Green = job has been passing successfully ** green for more than 3 days may suggest we need a review of our test coverage 1. 1-3 days GREEN (#1) 2. 4-7 days GREEN (#2) 3. Over 7 days GREEN (#3) Yellow = intermittent failures for different projects but no lasting or current regressions ** intermittent would be a healthy project as we expect a number of failures during the week ** I will not report any of the solved failures or regressions. 1. Solved job failures YELLOW (#1) 2. Solved regressions YELLOW (#2) Red = job has been failing ** Active Failures. The colour will change based on the amount of time the project/s has been broken. Only active regressions would be reported. 1. 1-3 days RED (#1) 2. 4-7 days RED (#2) 3. Over 7 days RED (#3)

1 0

Fwd: [CentOS-announce] Announcing the release of Gluster 5 on CentOS Linux 7 x86_64
by Sandro Bonazzola 06 Dec '18

06 Dec '18

fyi ---------- Forwarded message --------- From: Niels de Vos <ndevos(a)redhat.com> Date: gio 6 dic 2018, 20:00 Subject: [CentOS-announce] Announcing the release of Gluster 5 on CentOS Linux 7 x86_64 To: <centos-announce(a)centos.org> I am happy to announce the General Availability of Gluster 5 for CentOS 7 on x86_64. These packages are following the upstream Gluster Community releases, and will receive monthly bugfix updates. Gluster 5 is expected to receive updates until the end of October 2019. The maintanance and release schedule can be found at: https://www.gluster.org/community/release-schedule/ Users of CentOS 7 can now simply install Gluster 5 with only these two commands: # yum install centos-release-gluster # yum install glusterfs-server The centos-release-gluster package is delivered via CentOS Extras repos. This contains all the metadata and dependency information, needed to install Gluster 5. The actual package that will get installed is centos-release-gluster5. Users of Gluster 4.1 can stay on that release until June 2019. Users of Gluster 4.0 and earlier will need to manually upgrade by uninstalling the centos-release-gluster-legacy package, and replacing it with either the Gluster 5 or 4.1 version. Additional details about the upgrade process are linked in the announcement from the Gluster Community: https://lists.gluster.org/pipermail/announce/2018-October/000115.html We have a quickstart guide specifically built around the packages are available, it makes for a good introduction to Gluster and will help get you started in just a few simple steps, this quick start is available at https://wiki.centos.org/SpecialInterestGroup/Storage/gluster-Quickstart More details about the packages that the Gluster project provides in the Storage SIG is available in the documentation: https://wiki.centos.org/SpecialInterestGroup/Storage/Gluster The centos-release-gluster* repositories offer additional packages that enhance the usability of Gluster itself. Utilities and tools that were working with previous versions of Gluster are expected to stay working fine. If there are any problems, or requests for additional tools and applications to be provided, just send us an email with your suggestions. The current list of packages that is (planned to become) available can be found here: https://wiki.centos.org/SpecialInterestGroup/Storage/Gluster/Ecosystem-pkgs We welcome all feedback, comments and contributions. You can get in touch with the CentOS Storage SIG on the centos-devel mailing list (https://lists.centos.org ) and with the Gluster developer and user communities at https://www.gluster.org/mailman/listinfo , we are also available on irc at #gluster on irc.freenode.net, and on twitter at @gluster . Cheers, Niels de Vos Storage SIG member & Gluster maintainer _______________________________________________ CentOS-announce mailing list CentOS-announce(a)centos.org https://lists.centos.org/mailman/listinfo/centos-announce

1 0

[ANN] oVirt 4.3.0 Second Alpha Release is now available for testing
by Sandro Bonazzola 06 Dec '18

06 Dec '18

The oVirt Project is pleased to announce the availability of the Second Alpha Release of oVirt 4.3.0, as of December 6th, 2018 This is pre-release software. This pre-release should not to be used in production. Please take a look at our community page[1] to learn how to ask questions and interact with developers and users. All issues or bugs should be reported via oVirt Bugzilla[2]. This update is the second alpha release of the 4.3.0 version. This release brings more than 80 enhancements and more than 330 bug fixes on top of oVirt 4.2 series. What's new in oVirt 4.3.0? * Q35 chipset, support booting using UEFI and Secure Boot * Skylake-server and AMD EPYC support * New smbus driver in windows guest tools * Improved support for v2v * Tech preview for oVirt on Fedora 28 * Hundreds of bug fixes on top of oVirt 4.2 series * New VM portal details page (see a preview here: https://imgur.com/a/ExINpci) * New Cluster upgrade UI * OVN security groups * IPv6 (static host addresses) * LLDP Labeler * Support for 3.6 and 4.0 data centers, clusters and hosts were removed * Now using PostgreSQL 10 This release is available now on x86_64 architecture for: * Red Hat Enterprise Linux 7.6 or later * CentOS Linux (or similar) 7.6 or later This release supports Hypervisor Hosts on x86_64 and ppc64le architectures for: * Red Hat Enterprise Linux 7.6 or later * CentOS Linux (or similar) 7.6 or later * oVirt Node 4.3 (available for x86_64 only) Experimental tech preview for x86_64 and s390x architectures for Fedora 28 is also included. See the release notes draft [3] for installation / upgrade instructions and a list of new features and bugs fixed. Notes: - oVirt Appliance is already available for both CentOS 7 and Fedora 28 (tech preview). - oVirt Node NG is already available for both CentOS 7 - oVirt Node NG for Fedora 28 (tech preview) is facing build issues on Jenkins and will be released as soon as possible Additional Resources: * Read more about the oVirt 4.3.0 release highlights: http://www.ovirt.org/release/4.3.0/ * Get more oVirt project updates on Twitter: https://twitter.com/ovirt * Check out the latest project news on the oVirt blog: http://www.ovirt.org/blog/ [1] https://www.ovirt.org/community/ [2] https://bugzilla.redhat.com/enter_bug.cgi?classification=oVirt [3] http://www.ovirt.org/release/4.3.0/ [4] http://resources.ovirt.org/pub/ovirt-4.3-pre/iso/ -- SANDRO BONAZZOLA MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://red.ht/sig>

1 0

More logs from VNC/qemu/SASL
by Tomasz Barański 06 Dec '18

06 Dec '18

Hello I'm working on supporting VNC console on FIPS-enabled hosts[1]. I made qemu use SASL as authentication method instead of regular passwords. However, no matter what I do, I can't get it to accept credentials provided with a VNC client. Is there a way to get some qemu/SASL logs? I need to understand why the credentials are not accepted. Tomo [1] https://bugzilla.redhat.com/show_bug.cgi?id=1595536

1 0

[VDSM] check-merged failing for years - remove it?
by Nir Soffer 06 Dec '18

06 Dec '18

vdsm check-merged job takes 1.5 hours, and fails 80% of the time. https://jenkins.ovirt.org/job/vdsm_master_check-merged-el7-x86_64/buildTime… Nobody checks these failures or care about them. We are abusing CI resources for no benefit. Can we remove this job? Nir

6 10

planned Jenkins restart
by Evgheni Dereveanchin 05 Dec '18

05 Dec '18

Hi everyone, I'll be performing a planned Jenkins restart within the next hour. No new jobs will be scheduled during this maintenance period. I will inform you once it is over. Regards, Evgheni Dereveanchin

1 1

vdsm has been tagged (v4.30.4)
by Francesco Romani 05 Dec '18

05 Dec '18

_______________________________________________ Devel mailing list -- devel(a)ovirt.org To unsubscribe send an email to devel-leave(a)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/WUM4SIORNY5RN…

1 0

ovirt-engine has been tagged (ovirt-engine-4.3.0_alpha2)
by Tal Nisan 05 Dec '18

05 Dec '18

1 0

[OST] HE basic suite failing on reposync
by Ales Musil 05 Dec '18

05 Dec '18

Hello, I am trying to run locally he-basic-ansible-suite-master but it keeps failing on reposync: reposync command failed for repoid: ovirt-appliance-master-el7 Any idea what could be wrong? Thank you. Regards, Ales -- ALES MUSIL Associate Software Engineer - rhv network Red Hat EMEA <https://www.redhat.com/> amusil(a)redhat.com IM: amusil <https://red.ht/sig>

3 4

jenkins dead or barely alive?
by Michal Skrivanek 05 Dec '18

05 Dec '18

Hey, it didn’t work well yesterday evening (taking 10+ minutes to trigger CI) and this morning it’s even worse. Logging in to trigger it manually takes ~5 minutes, every action there seems to take ages... Thanks, michal

2 1

[IMPORTANT] Upgrading to PG 10.x in version 4.3 on f28/CentOS7.5 , instructions for developers,, please read before you re-base on master
by Eli Mesika 05 Dec '18

05 Dec '18

Hi We will merge a patch[1] today that will require the upcoming 4.3 version to use Postgres 10 on f28 and Postgres SCL 10 (Software Collections) on CentOS 7.5 * If you are using f28 and creating new DB schema for development (having no 9.x PG data), then you done and this change should be transparent to you. * If you are using f27, have some old 9.x PG data and upgrade to f28, then you will have to upgrade your old PG data after moving to f28 according to the instructions in [2] * If you are using CentOS then you are running PG SCL 9.5 and should upgrade to PG SCL 10 1. Upgrade to CentOS 7.5 (insure that you have the SCL repo [3] after upgrade) 2. #yum update -y # insure that your OS has latest patches 3. #service rh-postgresql95-postgresql stop 4. #yum install rh-postgresql10 rh-postgresql10-postgresql-contrib -y 5. #/opt/rh/rh-postgresql10/root/bin/postgresql-setup --upgrade --upgrade-from="rh-postgresql95-postgresql" # If you have junk sachems, drop them first, the upgrade of each takes time. 6. #service rh-postgresql10-postgresql start # check status to see that it is active 7. #service rh-postgresql10-postgresql enable 8. Insure that your patches are re-based on master latest 9. Remove all <target> binaries created with "#make clean install-dev PREFIX=<target>....." 10. Compile(make install-dev..)/Setup(engine-setup) and run again your patches (git branches you are working on) 11. Insure that basic operations (add new dc/cluster for example) are working 12. Track engine.log / server.log and PG logs for database errors 13. # yum remove rh-postgresql95 rh-postgresql95-postgresql-contrib -y (only if all above is succeed) [1] https://gerrit.ovirt.org/#/c/95100/ [2] https://docs.bmc.com/docs/btco113/migrating-the-data-from-postgresql-9-x-to… [3] https://wiki.centos.org/AdditionalResources/Repositories/SCL If you are developing from a VM then it is always recommended to create a "before upgrade" snapshot of the VM. (I know it is not supported from the user portal but you can ask for access rights only for doing this from your admin on the admin portal. If you have any questions/problems , please contact me Eli Mesika (emesika on IRC) Best Regards Eli

3 2

oVirt PPC support
by Alexandre Bencz 04 Dec '18

04 Dec '18

Hi I have a IBM Power7 machine, I saw that oVirt support is for PPC8, but, I would like to know if it is possible to use oVirt in PowerPC 7, if there is any internal limitation on the implementation of oVirt to not work in PPC7

1 0

Failing OST patches
by Kaustav Majumder 04 Dec '18

04 Dec '18

Recently I have pushed 2 patches for OST[1][2], both are failing in CI. Though unrelated failures I find the errors in "add_hosts" test beacuse the host is non operation within the asserted time.I have added the link for the jenkins log [3]. [1] https://gerrit.ovirt.org/#/c/95327/ [2] https://gerrit.ovirt.org/#/c/95347/ [3] https://pastebin.com/MVpws4Et Any advice? -- KAUSTAV MAJUMDER ASSOCIATE SOFTWARE ENGINEER Red Hat India PVT LTD. <https://www.redhat.com/> kmajumder(a)redhat.com M: 08981884037 IM: IRC: kmajumder <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> @redhatway <https://twitter.com/redhatway> @redhatinc <https://instagram.com/redhatinc> @redhatsnaps <https://snapchat.com/add/redhatsnaps>

4 6

Re: Any way to make VM Hidden/Locked for access
by Pavan Chavva 04 Dec '18

04 Dec '18

+Ovirt Devel and Adelino. FYI. Best, Pavan. On Wed, Nov 28, 2018 at 8:21 AM Mahesh Falmari <Mahesh.Falmari(a)veritas.com> wrote: > Hi Nir, > > Just wanted to check if there is any way to create a VM through API and > make this VM hidden or locked so that it is not shown/accessible to the > users until we explicitly enable it again. > > The use case here is of VM recovery, where we would like to create a VM > first and wanted to check if there is any issue in VM creation and then > fail in the first phase itself before the actual data transfer takes place. > But the issue we may see here is that once VM gets created, it becomes > accessible to users who may play with it and it would impact the subsequent > recovery operations. > > > > Thanks & Regards, > Mahesh Falmari > > > -- PAVAN KUMAR CHAVVA ENGINEERING PARTNER MANAGER Red Hat pchavva(a)redhat.com M: 4793219099 IM: pchavva

3 2

[Ovirt] [CQ weekly status] [30-11-2018]
by Dafna Ron 02 Dec '18

02 Dec '18

Hi, This mail is to provide the current status of CQ and allow people to review status before and after the weekend. Please refer to below colour map for further information on the meaning of the colours. *CQ-4.2*: RED (#1) I checked last date ovirt-engine and vdsm passed and moved packages to tested as they are the bigger projects and it was on the 27-11-218. We have been having sporadic failures for most of the projects on test check_snapshot_with_memory. We have deducted that this is caused by a code regression in storage based on the following things: 1.Evgheni and Gal helped debug this issue to rule out lago and infra issue as the cause of failure and both determined the issue is a code regression - most likely in storage. 2. The failure only happens on 4.2 branch. 3. the failure itself is cannot run a vm due to low disk space in storage domain and we cannot see any failures which would leave any leftovers in the storage domain. Dan and Ryan are actively involved in trying to find the regression but the consensus is that this is a storage related regression and* we are having a problem getting the storage team to join us in debugging the issue. * I prepared a patch to skip the test in case we cannot get cooperation from storage team and resolve this regression in the next few days: https://gerrit.ovirt.org/#/c/95889/ *CQ-Master:* YELLOW (#1) We have failures which CQ is still bisecting and until its done we cannot point to any specific failing projects. Happy week! Dafna ------------------------------------------------------------------------------------------------------------------- COLOUR MAP Green = job has been passing successfully ** green for more than 3 days may suggest we need a review of our test coverage 1. 1-3 days GREEN (#1) 2. 4-7 days GREEN (#2) 3. Over 7 days GREEN (#3) Yellow = intermittent failures for different projects but no lasting or current regressions ** intermittent would be a healthy project as we expect a number of failures during the week ** I will not report any of the solved failures or regressions. 1. Solved job failures YELLOW (#1) 2. Solved regressions YELLOW (#2) Red = job has been failing ** Active Failures. The colour will change based on the amount of time the project/s has been broken. Only active regressions would be reported. 1. 1-3 days RED (#1) 2. 4-7 days RED (#2) 3. Over 7 days RED (#3)

7 13

otopi defaults again to python3
by Yedidyah Bar David 02 Dec '18

02 Dec '18

Hi all, As some of you might recall, some time ago we made otopi default to python3, and quickly reverted that, realizing this causes too much breakage. Now things should hopefully be more stable, and I now merged a patch to default to python3 again. Current status: engine-setup works with python3 on fedora. host-deploy works with python3 on fedora, with both engine being on el7 and on fedora. Didn't try on el7, might work as well. hosted-engine --deploy is most likely broken on fedora, but I think it was already broken. We are working on that, but it will require some more time - notably, having stuff from vdsm on python3 (if not fully porting vdsm to python3, which I understand will take even more time). If you want to use python2, you can do that with: OTOPI_PYTHON=/bin/python hosted-engine --deploy On el7, if you manually added python3 (which is not available in the base repos), things will break - use above workaround if needed. Best regards, -- Didi

2 2