February 2019 - Devel - oVirt List Archives

OST manual: enable engine 4.3
by Nir Soffer 28 Feb '19

28 Feb '19

When starting manual OST job, we can select engine version. The available options are: - master - 42 Since we have now 4.3 branch, we should be able to select 4.3 engine. See attached screenshot.

3 2

Vdsm branch ovirt-4.3 created
by Milan Zamazal 27 Feb '19

27 Feb '19

Hi, I created ovirt-4.3 branch. That means patches for 4.3 must be backported from master since now. Not everything regarding CI is ready yet, but until we make the branch, we can't make some things working nor prove they are working. We need the branch to move forward. *Please don't merge non-4.3 patches to master yet.* Let's make 4.3 backports completely safe and trivial for a while, until we have working CI on 4.3. I'm not particularly happy with the branching process, let's use this experience to improve it next time. At minimum some guidelines should exist rather than just "common knowledge" with missing bits and pieces. Thanks, Milan

5 11

broken OST network suite (?)
by Miguel Duarte de Mora Barroso 26 Feb '19

26 Feb '19

Hi, I'm seeing the following error on the OST network suite: 17:05:56 Collecting pylint==1.6.4 17:05:57 Downloading https://files.pythonhosted.org/packages/92/f3/41deb50322d579517f779c3421b92… (569kB) 17:05:57 Collecting isort>=4.2.5 (from pylint==1.6.4) 17:05:57 Downloading https://files.pythonhosted.org/packages/35/c5/025aaa76f0f337e3d91197973c42b… (62kB) 17:05:58 Complete output from command python setup.py egg_info: 17:05:58 /usr/lib64/python2.7/distutils/dist.py:267: UserWarning: Unknown distribution option: 'python_requires' 17:05:58 warnings.warn(msg) 17:05:58 error in isort setup command: 'install_requires' must be a string or list of strings containing valid project/version requirement specifiers; Expected version spec in futures; python_version < "3.2" at ; python_version < "3.2" This happens on - at least - [0]. From my understanding, isort released a couple of new versions - according to [1] - and looks like that pylint version is too old for whatever new stuff isort now has. On other project I'm running pylint 1.8.4, which runs fine against that isort version: tox -e pylint pylint recreate: /home/mduarted/ovirt/ovirt-provider-ovn/.tox/pylint pylint installdeps: pytest==3.5.1, pylint==1.8.4, -r/home/mduarted/ovirt/ovirt-provider-ovn/requirements.txt pylint installed: DEPRECATION: Python 2.7 will reach the end of its life on January 1st, 2020. Please upgrade your Python as Python 2.7 won't be maintained after that date. A future version of pip will drop support for Python 2.7.,astroid==1.6.5,attrs==18.2.0,backports.functools-lru-cache==1.5,certifi==2018.11.29,chardet==3.0.4,configparser==3.7.3,enum34==1.1.6,extras==1.0.0,fixtures==3.0.0,funcsigs==1.0.2,futures==3.2.0,idna==2.8,isort==4.3.9,lazy-object-proxy==1.3.1,linecache2==1.0.0,mccabe==0.6.1,more-itertools==5.0.0,netaddr==0.7.19,ovs==2.10.0,ovsdbapp==0.15.0,pbr==5.1.2,pluggy==0.6.0,py==1.8.0,pylint==1.8.4,pytest==3.5.1,python-mimeparse==1.6.0,requests==2.21.0,singledispatch==3.4.0.3,six==1.12.0,sortedcontainers==2.1.0,testtools==2.3.0,traceback2==1.4.0,unittest2==1.1.0,urllib3==1.24.1,wrapt==1.11.1 pylint runtests: PYTHONHASHSEED='2585806524' pylint runtests: commands[0] | pylint --errors-only provider driver Using config file /home/mduarted/ovirt/ovirt-provider-ovn/.pylintrc make lint3____________________________________ summary _____________________________________ pylint: commands succeeded congratulations :) Pyling 2.2.2 also runs fine. Is there a reason for us to be using such an outdated version ? [0] - https://jenkins.ovirt.org/job/ovirt-system-tests_manual/4155/console [1] - https://pypi.org/project/isort/#history

1 1

[VDSM] Simplifying project ACL
by Nir Soffer 26 Feb '19

26 Feb '19

Hi all, I learned recently that we have these groups in the project: vdsm-maintainers: https://gerrit.ovirt.org/#/admin/groups/15,members vdsm-master-maintainers: https://gerrit.ovirt.org/#/admin/groups/106,members And we have this complicated access control list: https://gerrit.ovirt.org/#/admin/projects/vdsm,access Developers in vdsm-master-maintainers can approve patches, but cannot submit. I find this strange and more complicated than needed. I think we can trust people in the vdsm-master-maintainers group to do the right thing. I sent this patch to simplify the ACL (with help of Gerrit UI): https://gerrit.ovirt.org/c/97738/ Thoughts? Nir

2 2

Misc configuration': Failed to start service 'rh-postgresql95-postgresql
by Galit Rosenthal 24 Feb '19

24 Feb '19

Hi I receive this error message both in CQ and check_patch: 2019-02-16 16:28:06,874-0500 DEBUG otopi.plugins.otopi.services.systemd systemd.state:130 starting service rh-postgresql95-postgresql 2019-02-16 16:28:06,874-0500 DEBUG otopi.plugins.otopi.services.systemd plugin.executeRaw:813 execute: ('/usr/bin/systemctl', 'start', 'rh-postgresql95-postgresql.service'), executable='None', cwd='None', env=None 2019-02-16 16:28:07,913-0500 DEBUG otopi.plugins.otopi.services.systemd plugin.executeRaw:863 execute-result: ('/usr/bin/systemctl', 'start', 'rh-postgresql95-postgresql.service'), rc=1 2019-02-16 16:28:07,914-0500 DEBUG otopi.plugins.otopi.services.systemd plugin.execute:921 execute-output: ('/usr/bin/systemctl', 'start', 'rh-postgresql95-postgresql.service') stdout: 2019-02-16 16:28:07,914-0500 DEBUG otopi.plugins.otopi.services.systemd plugin.execute:926 execute-output: ('/usr/bin/systemctl', 'start', 'rh-postgresql95-postgresql.service') stderr: Job for rh-postgresql95-postgresql.service failed because the control process exited with error code. See "systemctl status rh-postgresql95-postgresql.service" and "journalctl -xe" for details. 2019-02-16 16:28:07,915-0500 DEBUG otopi.transaction transaction.abort:119 aborting 'File transaction for '/var/opt/rh/rh-postgresql95/lib/pgsql/data/pg_hba.conf'' 2019-02-16 16:28:07,916-0500 DEBUG otopi.context context._executeMethod:143 method exception Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/otopi/context.py", line 133, in _executeMethod method['method']() File "/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-setup/ovirt-engine/provisioning/postgres.py", line 201, in _misc self._provisioning.provision() File "/usr/share/ovirt-engine/setup/ovirt_engine_setup/engine_common/postgres.py", line 498, in provision self.restartPG() File "/usr/share/ovirt-engine/setup/ovirt_engine_setup/engine_common/postgres.py", line 399, in restartPG state=state, File "/usr/share/otopi/plugins/otopi/services/systemd.py", line 141, in state service=name, RuntimeError: Failed to start service 'rh-postgresql95-postgresql' 2019-02-16 16:28:07,918-0500 ERROR otopi.context context._executeMethod:152 Failed to execute stage 'Misc configuration': Failed to start service 'rh-postgresql95-postgresql' 2019-02-16 16:28:07,958-0500 DEBUG otopi.plugins.otopi.debug.debug_failure.debug_failure debug_failure._notification:100 tcp connections: id uid local foreign state pid exe What can cause it? Thanks Galit https://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt-master_chang… https://jenkins.ovirt.org/blue/organizations/jenkins/ovirt-system-tests_sta… Regards, Galit -- GALIT ROSENTHAL SOFTWARE ENGINEER Red Hat <https://www.redhat.com/> galit(a)gmail.com T: 972-9-7692230 <https://red.ht/sig>

12 33

OST failes since build 4134
by Nir Soffer 23 Feb '19

23 Feb '19

https://jenkins.ovirt.org/job/ovirt-system-tests_manual/buildTimeTrend Here are the failures since build 4134: - https://jenkins.ovirt.org/job/ovirt-system-tests_manual/4135/testReport/jun… Not related to the patch tested: https://gerrit.ovirt.org/c/97996/ I started a new build: https://jenkins.ovirt.org/job/ovirt-system-tests_manual/4140/ - https://jenkins.ovirt.org/job/ovirt-system-tests_manual/4136/ (no test results) - https://jenkins.ovirt.org/job/ovirt-system-tests_manual/4137/ (no tests results) - https://jenkins.ovirt.org/job/ovirt-system-tests_manual/4138/ (no test results) - https://jenkins.ovirt.org/job/ovirt-system-tests_manual/4139/testReport/jun… UI test failure/error? Nir

3 3

Fwd: Planned Outage - Fedora Core Services 2019-02-27 20:00 UTC
by Sandro Bonazzola 22 Feb '19

22 Feb '19

FYI ---------- Forwarded message --------- From: Stephen John Smoogen <smooge(a)gmail.com> Date: ven 22 feb 2019 alle ore 20:43 Subject: Planned Outage - Fedora Core Services 2019-02-27 20:00 UTC To: <announce(a)lists.fedoraproject.org>, Development discussions related to Fedora <devel(a)lists.fedoraproject.org>, Fedora Infrastructure < infrastructure(a)lists.fedoraproject.org> There will be an outage starting at 2019-02-27 20:00 UTC, which will last approximately 4-6 hours. To convert UTC to your local time, take a look at http://fedoraproject.org/wiki/Infrastructure/UTCHowto or run: date -d '2019-02-27 20:00UTC' Reason for outage: Fedora Infrastructure would like to update and reboot all core systems and services. This will update kernels, glibc, and systemd plus many other services on the affected systems. Affected Services: All systems under fedoraproject.org will be affected. Important databases and authentication will be updated and rebooted first. Then other non-build systems will follow. Then build systems will finalize the update/reboot cycle Ticket Link: https://pagure.io/fedora-infrastructure/issue/7591 Please join #fedora-admin or #fedora-noc on irc.freenode.net or add comments to the ticket for this outage above. -- Stephen J Smoogen. _______________________________________________ devel mailing list -- devel(a)lists.fedoraproject.org To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org -- 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

[Ovirt] [CQ weekly status] [22-02-2019]
by Dafna Ron 22 Feb '19

22 Feb '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) 1. rh-postgress was failing to start due to missing selinux policy causing engine to fail installation. Bug: https://bugzilla.redhat.com/show_bug.cgi Issue resolved by didi and Galit by: 1. adding a workaround to add the selinuc poslicy and also a proposed fix (as described in comment #6) 2. created new lago images with new selinux package *CQ-Master:* GREEN (#1) 1. The same issue in 4.2 has effected master (for upgrade suite) 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

Installing oVirt on Physical machine
by emmanualvnebu1＠gmail.com 22 Feb '19

22 Feb '19

Hi Guys, I am trying to install oVirt node on a physical machine. Once selected the option to install oVirt 4.3 it give a screen "dracut-initqueue time out And then get into emergency mode & gives dracut cmd line. if I exit the command line, it continue bootinto the installation window. However it gives a message "Kickstart file /run/install/ks.config is missing" (Pane is dead). Tried the same on vmware, it boot fine & am able to install it. Can someone tell me how could I fix this?

2 1

Query regarding copying and executing files inside guest OS
by Pravin Amin 22 Feb '19

22 Feb '19

Hi, We are looking for a way to copy files and execute scripts inside Virtual Machines hosted on oVirt manager (Any supported guest OS) either through REST API or using Guest Tools. Please let me know how we can achieve it. -Thanks, Pravin Amin Principal SQA Engineer Netbackup Veritas Technologies LLC Office: (91) 20 - 66157288 / Mobile: (91) 9881139050 pravin.amin(a)veritas.com<mailto:pravin.amin@veritas.com> [signature_394478960]<https://www.veritas.com/product/backup-and-recovery/netbackup-8?om_camp_id=…> This message (including any attachments) is intended only for the use of the individual or entity to which it is addressed and may contain information that is non-public, proprietary, privileged, confidential, and exempt from disclosure under applicable law or may constitute as attorney work product. If you are not the intended recipient, you are hereby notified that any use, dissemination, distribution, or copying of this communication is strictly prohibited. If you have received this communication in error, notify us immediately by telephone and (i) destroy this message if a facsimile or (ii) delete this message immediately if this is an electronic communication.

4 5