- Devel - oVirt List Archives

FC28 Blacklisted in oVirt STDCI V2
by Barak Korren 10 Jun '19

10 Jun '19

Hi all, By Snadro's request, as of a few minutes ago FC28 had been blacklisted in oVirt's STDCI V2 system. What this means is that if any project has FC28 threads configured in its STDCI V2 YAML configuration file, those threads will be ignored by the STDCI system and not invoked. Threads for building and testing on other distributions will keep working as before. It is still recommended that projects with fc28 configuration will patch their configuration files to remove FC28, to make it easier to understand what the CI does and not rely on an implicit blacklist. Please note that this only concerns projects that have made the switch to STDCI V2. Projects that still use V1, and have FC28 jobs defined, those jobs will keep working as before. The following patch by Sandro, however, includes code to remove all those jobs: https://gerrit.ovirt.org/c/100556/ Thanks, Barak. -- Barak Korren RHV DevOps team , RHCE, RHCi Red Hat EMEA redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted

1 0

cannot add host (oVirt 4.3.3.7)
by Hetz Ben Hamo 09 Jun '19

09 Jun '19

Hi, I'm trying to add a new host to oVirt. The main host is Xeon E5 while the new host is AMD Ryzen 5. The main host is running oVirt 4.3.3 and the new node is a minimal install of CentOS 7.6 (1810) with all the latest updates. I'm enclosing the log files. it complains that it cannot get the oVirt packages, perhaps wrong channel(?). Looking at the log, it's trying to use minidnf. I don't think CentOS 7 supports DNF.. Thanks Hetz תודה, *חץ בן חמו* אתם מוזמנים לבקר בבלוג היעוץ <http://linvirtstor.net/> או בבלוג הפרטי שלי <http://benhamo.org>

1 0

[Ovirt] [CQ weekly status] [07-06-2019]
by Dafna Ron 07 Jun '19

07 Jun '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) Last failure was on 05-06 for project ovirt-ansible-cluster-upgrade due to failure in test 002_bootstrap.add_master_storage_domain. The fix was created and merged <https://gerrit.ovirt.org/#/c/100089/> *CQ-4.3*: RED (#1) vdsm is currently broken due to https://gerrit.ovirt.org/#/c/100576/ - Remove SOS VDSM plugin vdsm sos plugin will be available from centos 7.7 as part of sos-3.7-3. however, the metrics tests are using sos-logcollector which s causing a failure in ost. We are waiting for Shirly to have a look at the tests and see how they can be fixed. *CQ-Master:* RED (#1) vdsm is currently broken due to https://gerrit.ovirt.org/#/c/100576/ - Remove SOS VDSM plugin vdsm sos plugin will be available from centos 7.7 as part of sos-3.7-3. however, the metrics tests are using sos-logcollector which s causing a failure in ost. We are waiting for Shirly to have a look at the tests and see how they can be fixed. Current running jobs for 4.2 [1], 4.3 [2] and master [3] can be found here: [1] http://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt-4.2_change-qu… [2] https://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt-4.3_change-q… [3] 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

Master is broken for Fedora
by Sandro Bonazzola 05 Jun '19

05 Jun '19

Hi, just to let you know that vdsm jsut broke hosted engine on fedora. Reason is that hosted engine is still building for python2 whiile vdsm is now being shipped for python3 only. hosted engine build is currently broken on missing yajsonrpc being: $ rpm -ql https://resources.ovirt.org/pub/ovirt-master-snapshot/rpm/fc28/noarch/vdsm-… /usr/lib/python3.6/site-packages/yajsonrpc/__pycache__/betterAsyncore.cpython-36.opt-1.pyc /usr/lib/python3.6/site-packages/yajsonrpc/__pycache__/betterAsyncore.cpython-36.pyc /usr/lib/python3.6/site-packages/yajsonrpc/__pycache__/exception.cpython-36.opt-1.pyc /usr/lib/python3.6/site-packages/yajsonrpc/__pycache__/exception.cpython-36.pyc /usr/lib/python3.6/site-packages/yajsonrpc/__pycache__/stomp.cpython-36.opt-1.pyc /usr/lib/python3.6/site-packages/yajsonrpc/__pycache__/stomp.cpython-36.pyc /usr/lib/python3.6/site-packages/yajsonrpc/__pycache__/stompclient.cpython-36.opt-1.pyc /usr/lib/python3.6/site-packages/yajsonrpc/__pycache__/stompclient.cpython-36.pyc /usr/lib/python3.6/site-packages/yajsonrpc/__pycache__/stompserver.cpython-36.opt-1.pyc /usr/lib/python3.6/site-packages/yajsonrpc/__pycache__/stompserver.cpython-36.pyc /usr/lib/python3.6/site-packages/yajsonrpc/betterAsyncore.py /usr/lib/python3.6/site-packages/yajsonrpc/exception.py /usr/lib/python3.6/site-packages/yajsonrpc/stomp.py /usr/lib/python3.6/site-packages/yajsonrpc/stompclient.py /usr/lib/python3.6/site-packages/yajsonrpc/stompserver.py please note that package naming for this package is not following Fedora guidelines. It should be prefixed with "python3-" according to https://docs.fedoraproject.org/en-US/packaging-guidelines/Python/#_naming Rule doesn't apply to applications but yajsonrpc subpackage is a library package. -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://red.ht/sig> <https://redhat.com/summit>

3 10

ovirt-engine has been tagged (ovirt-engine-4.3.4.3)
by Tal Nisan 05 Jun '19

05 Jun '19

1 0

Planned restart of production services
by Evgheni Dereveanchin 05 Jun '19

05 Jun '19

Hi everyone, I will be restarting several production systems within the following hour to apply updates. The following services may be unreachable for some period of time: - resources.ovirt.org - package repositories - jenkins.ovirt.org - CI master - glance.ovirt.org - Glance image repository Package repositories will be unreachable for a short period of time. No new CI jobs will be started during this period. I will announce you once maintenance is complete. -- Regards, Evgheni Dereveanchin

1 1

Feature Request: oVirt to warn when VDO is getting full
by Strahil 04 Jun '19

04 Jun '19

Hello All, I would like to ask how many of you use VDO before asking the oVirt Devs to assess a feature in oVirt for monitoring the size of the VDOs on hyperconverged systems. I think such warning, will save a lot of headaches, but it will not be usefull if most of the community is not using VDO at all. Best Regards, Strahil Nikolov

3 2

ovirt-engine has been tagged (ovirt-engine-4.3.4.2)
by Tal Nisan 29 May '19

29 May '19

1 0

Fwd: Fedora 28 End Of Life
by Sandro Bonazzola 29 May '19

29 May '19

FYI. Fedora 29 oVirt packages building is still in progress. The following package still need to be built, help with getting them built on fedora 29 will be appreciated. cockpit-ovirt engine-db-query ovirt-engine-api-explorer ovirt-engine-appliance ovirt-engine-extension-aaa-misc ovirt-engine-nodejs-modules ovirt-engine-sdk-python (sdk3) ovirt-engine-ui-extensions ovirt-engine-yarn ovirt-guest-agent-windows ovirt-guest-tools-iso ovirt-host ovirt-hosted-engine-ha ovirt-hosted-engine-setup ovirt-node-ng-image ovirt-provider-ovn ovirt-scheduler-proxy vdsm Thanks ---------- Forwarded message --------- Da: Mohan Boddu <mboddu(a)bhujji.com> Date: mer 29 mag 2019 alle ore 01:05 Subject: Fedora 28 End Of Life To: <announce(a)lists.fedoraproject.org>, < test-announce(a)lists.fedoraproject.org>, < devel-announce(a)lists.fedoraproject.org> As of the 28th of May 2019, Fedora 28 has reached its end of life for updates and support. No further updates, including security updates, will be available for Fedora 28. Fedora 29 will continue to receive updates until approximately one month after the release of Fedora 31. The maintenance schedule of Fedora releases is documented on the Fedora Project wiki [0]. The Fedora Project wiki also contains instructions [1] on how to upgrade from a previous release of Fedora to a version receiving updates. Regards, Mohan Boddu. [0] https://fedoraproject.org/wiki/Fedora_Release_Life_Cycle#Maintenance_Schedu… [1]https://fedoraproject.org/wiki/Upgrading?rd=DistributionUpgrades _______________________________________________ devel-announce mailing list -- devel-announce(a)lists.fedoraproject.org To unsubscribe send an email to devel-announce-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-announce@lists.fedorapr… -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://red.ht/sig> <https://redhat.com/summit>

1 0

VDSM Python 3 RPMs are available
by Marcin Sobczyk 28 May '19

28 May '19

Hi, I'm happy to announce, that with [1] landing in master, we're now building Python 3 packages for VDSM. Example pipeline run can be found here [2]. Currently the py3 RPMs still have some broken dependencies and there are ongoing efforts to fix these. All scripts in built RPMs have py3 shebang lines, but there is no guarantee that all of them will work. We also build for Fedora 28 only - more patches are on the way that will build RPMs for Fedora 30. If you want to make py3 RPMs out of your VDSM patch, you simply need to post 'ci please build' in gerrit - that will launch 'build-artifacts' stdci stage which produces py2 and py3 RPMs in its sub-stages. Regards, Marcin [1] https://gerrit.ovirt.org/#/c/100135/ [2] https://jenkins.ovirt.org/job/vdsm_standard-on-merge/755/artifact/

2 1