- Devel - oVirt List Archives

[Ovirt] [CQ weekly status] [25-01-2019]
by Dafna Ron 25 Jan '19

25 Jan '19

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*: GREEN (#1) We have no current failures. Last failed job was for ovirt-ansible-hosted-engine due to a failed build-artiacts job on Jan 24. the issue has been resolved today by Simon Tiraboschi *CQ-Master:* RED (#1) 1. tests are still failing on ovirt-engine master due to create of domain in version 5. this was reported to the list this week and a patch has been merged to engine: https://gerrit.ovirt.org/97262 The change is currently in sected off changes and should pass CQ in the next 24 hours. you can view the status of the patch in the last "get next" job in CQ: https://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt-master_chang… Current running jobs for 4.2 [1] and master [2] can be found here: [1] http://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt-4.2_change-qu… [2] http://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt-master_change… 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

[ANN] oVirt 4.3.0 Third Release Candidate is now available for testing
by Sandro Bonazzola 24 Jan '19

24 Jan '19

The oVirt Project is pleased to announce the availability of the Third Release Candidate of oVirt 4.3.0, as of January 24th, 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 first release candidate of the 4.3.0 version. This release brings more than 130 enhancements and more than 450 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 * OVA export / import of Templates * Full support for live migration of High Performance VMs * Microsoft Failover clustering support (SCSI Persistent Reservation) for Direct LUN disks * 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) * Support of Neutron from RDO OpenStack 13 as external network provider * Support of using Skydive from RDO OpenStack 14 as Tech Preview * Support for 3.6 and 4.0 data centers, clusters and hosts were removed * Now using PostgreSQL 10 * New metrics support using rsyslog instead of fluentd 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 CentOS 7 - oVirt Node NG for Fedora 28 (tech preview) is being delayed due to build issues with the build system. 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

[URGENT] 4.3.0 RC3 blocked
by Sandro Bonazzola 24 Jan '19

24 Jan '19

Hi, I was doing integration testing on the current 4.3.0-pre repository which is planned to be released today as RC3 and i can't start a newly created VM: *Bug 1669102* <https://bugzilla.redhat.com/show_bug.cgi?id=1669102> - can't start VM qemu-kvm: warning: All CPU(s) up to maxcpus should be described in NUMA config, ability to start up with partial NU MA mappings is obsoleted and will be removed in future can you please have a look? I've the system available for further investigations. Thanks, -- SANDRO BONAZZOLA MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://red.ht/sig>

2 3

ovirt-engine has been tagged (ovirt-engine-4.3.0.1)
by Piotr Kliczewski 24 Jan '19

24 Jan '19

1 0

Disable VNC Password in oVirt host
by Akshita Jain 23 Jan '19

23 Jan '19

Hi, I'm doing R&D project using oVirt 4.2. In my project i want to access the VNC Console on multiple screens from our separately hosted noVNC but I'm unable to access VNC console on multiple screen as it is password protected. Is there any way to disable the VNC Console Password and change it to a fixed value?

3 2

query on running OST
by Pooja Pandey 23 Jan '19

23 Jan '19

Hello Team, Could you please help me in answering a query about OST run.I am trying to run on a virtual machine and it is failing with an error that libvirtError: unsupported configuration: Domain requires KVM, but it is not available. Is it necessary to run this Ovirt System Test on a hypervisor only?Please reply on this so that I can proceed further.Thanks.... Regards, Pooja -- DISCLAIMER - *MSysTechnologies LLC* This email message, contents and its attachments may contain confidential, proprietary or legally privileged information and is intended solely for the use of the individual or entity to whom it is actually intended. If you have erroneously received this message, please permanently delete it immediately and notify the sender. If you are not the intended recipient of the email message,you are notified strictly not to disseminate,distribute or copy this e-mail.E-mail transmission cannot be guaranteed to be secure or error-free as Information could be intercepted, corrupted, lost, destroyed, incomplete or contain viruses and MSysTechnologies LLC accepts no liability for the contents and integrity of this mail or for any damage caused by the limitations of the e-mail transmission.

5 9

ovirt-engine has been tagged (ovirt-engine-4.3.0)
by Tal Nisan 22 Jan '19

22 Jan '19

1 0

vdsm has been tagged (v4.30.8)
by Milan Zamazal 22 Jan '19

22 Jan '19

1 0

vdsm has been tagged (v4.30.7)
by Milan Zamazal 22 Jan '19

22 Jan '19

1 0

Jenkins was restarted this morning
by Daniel Belenky 22 Jan '19

22 Jan '19

Hi all, Some of you have probably noticed that Jenkins was not responsive this morning. As a result, we've had to restart it. The service is up and running and everything should be back to normal by now. If you've had any running jobs by the time of the restart, please re-trigger them by going to your patch in Gerrit or PR in GitHub and comment '*ci test please*' to make sure that the CI system will test your jobs. Sorry for any inconvenience that was caused and do not hesitate to reach out to me or anyone from the CI team with questions or requests for assistance. Thanks, -- DANIEL BELENKY

1 0