- Devel - oVirt List Archives

ovirt-engine has been tagged (ovirt-engine-4.3.7.2)
by Tal Nisan 12 Nov '19

12 Nov '19

1 0

vdsm has been tagged (v4.30.36)
by Milan Zamazal 11 Nov '19

11 Nov '19

1 0

VDSM TestCommunicate.test_send_receive() failed
by Eyal Shenitzky 11 Nov '19

11 Nov '19

Hi, I see this failure in the VDSM check-patch [1] - 11:25:34 =================================== FAILURES =================================== 11:25:34 ______________________ TestCommunicate.test_send_receive _______________________ 11:25:34 11:25:34 self = <storage.mailbox_test.TestCommunicate instance at 0x7fbf6498e680> 11:25:34 mboxfiles = MboxFiles(inbox='/var/tmp/vdsm/test_send_receive0/inbox', outbox='/var/tmp/vdsm/test_send_receive0/outbox') 11:25:34 11:25:34 def test_send_receive(self, mboxfiles): 11:25:34 msg_processed = threading.Event() 11:25:34 expired = False 11:25:34 received_messages = [] 11:25:34 11:25:34 def spm_callback(msg_id, data): 11:25:34 received_messages.append((msg_id, data)) 11:25:34 msg_processed.set() 11:25:34 11:25:34 with make_hsm_mailbox(mboxfiles, 7) as hsm_mb: 11:25:34 with make_spm_mailbox(mboxfiles) as spm_mm: 11:25:34 spm_mm.registerMessageType(b"xtnd", spm_callback) 11:25:34 VOL_DATA = dict( 11:25:34 poolID=SPUUID, 11:25:34 domainID='8adbc85e-e554-4ae0-b318-8a5465fe5fe1', 11:25:34 volumeID='d772f1c6-3ebb-43c3-a42e-73fcd8255a5f') 11:25:34 REQUESTED_SIZE = 100 11:25:34 11:25:34 hsm_mb.sendExtendMsg(VOL_DATA, REQUESTED_SIZE) 11:25:34 11:25:34 if not msg_processed.wait(10 * MONITOR_INTERVAL): 11:25:34 expired = True 11:25:34 11:25:34 > assert not expired, 'message was not processed on time' 11:25:34 E AssertionError: message was not processed on time 11:25:34 E assert not True 11:25:34 11:25:34 storage/mailbox_test.py:180: AssertionError Is this issue known to anyone? [1] - https://jenkins.ovirt.org/job/vdsm_standard-check-patch/14093/consoleFull Thanks -- Regards, Eyal Shenitzky

3 3

dropping Fedora 29 support
by Michal Skrivanek 11 Nov '19

11 Nov '19

Hi, any reason to keep Fedora 29 around anymore? It’s going EOL in 3 weeks. We usually need newer stuff anyway, and it would also save CI resources since we already added el8 and f30 everywhere Thanks, michal

4 10

oVirt 4.4 / master CI readiness
by Sandro Bonazzola 07 Nov '19

07 Nov '19

Hi, I need an update on current status for oVirt 4.4 / CI readiness. Where do we stand with OST? How long will it take to get it up and running with el8 hosts and el7 engine? Thanks, -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://www.redhat.com/>*Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours.*

3 4

Dropping local crypto settings throughout oVirt in favour of crypto policies
by Marcin Sobczyk 07 Nov '19

07 Nov '19

Hi, given that crypto policies appeared in RHEL8 I think it's a good time to discuss using them throughout oVirt. I prepared a document, that describes the current state of crypto settings in VDSM along with the benefits and potential issues that come with moving to crypto policies. If you have a moment, please go through the doc - any input and comments are welcome. https://docs.google.com/document/d/1K19jDOITEQenPDbbSft2ChgGrL_DgpcbQon_bWL… Regards, Marcin Sobczyk

2 2

Building vdsm repo fails in CI
by Vojtech Juranek 07 Nov '19

07 Nov '19

Hi, when I try to build vdsm repo in Jenkins, it fails with ERROR: Command failed: 16:22:41 # /usr/bin/yum --installroot /var/lib/mock/epel-8- ppc64le-873106fe041e712f3fe68fbbfa530ba7-bootstrap-5067/root/ --releasever 8 install dnf dnf-plugins-core distribution-gpg-keys --setopt=tsflags=nocontexts 16:22:41 Failed to set locale, defaulting to C 16:22:41 Error: Package: python3-dnf-4.0.9.2-5.el8.noarch (centos-base-el8) 16:22:41 Requires: python3-libdnf >= 0.22.5-3 see e.g. [1]. Could someone take a look? It blocks any OST testing. Thanks Vojta [1] https://jenkins.ovirt.org/job/vdsm_standard-check-patch/13877/consoleFull

2 2

Check "ignore OVF update failure" when setting Domain to Maintenance
by scott.fitzgerald＠oracle.com 06 Nov '19

06 Nov '19

Hi, As in title, how do I access this checkbox when calling domainService().deactivate()? TIA

2 3

[feedback needed] VirtIO Windows Drivers - new installer
by Steve Graham 04 Nov '19

04 Nov '19

Good morning - I gave 0.1.173 from the 0.1.173-2 folder a try and the installation is failing when trying to start the "virtio-win-guest-tools" service. I tried multiple times and made sure I have administrative rights but can't get it to work. I rebooted and tried again and that didn't help. The system is 2012 R2 fully patched. Thank you for all your hard work! [image: 2019-10-30_11-12-00.png]

3 5

[oVirt] [CQ weekly status] [02-11-2019]
by Dusan Fodor 02 Nov '19

02 Nov '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.3*: RED (#1) Last failure was on 01-11 for ovirt-system-tests caused by failing in its on-merge job- it is probably related to gating effort, thread was open to investigate this. *CQ-Master:* YELLOW (#1 Last failure was on 01-11 caused by known, random add storage domain failure (test issue). Current running jobs for 4.3 [1] and master [2] can be found here: [1] https://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt-4.3_change-q… [2] http://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt-master_change… Have a nice week! Dusan ------------------------------------------------------------------------------------------------------------------- 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) _______________________________________________ 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/YCNCKRK3G4EJX…

1 0