January 2019 - Devel - oVirt List Archives

Request for adding ovirt-engine-sdk-go as an incubator project under oVirt
by Joey Ma 16 Jan '19

16 Jan '19

Hi fellows, My name is Joey. Now I'm maintaining the project ovirt-engine-sdk-go[1] which provides a Golang based sdk for oVirt engine REST API. During the past year, I was keeping in touch Ondra, Juan and Martin. It's very appreciated that they helped me a lot to improve the sdk and also added me into the oVirt developer team[2] in github. Both Ondra and I think that the project is in great shape and ready for production use. :-) The original plan is to add the project into oVirt 4.3 official release. While according to the schedules[3] for 4.3, maybe there's no enough time to make it done due to some additional CI work. So if I may ask, is that possible to add the project as an oVirt incubator project first, by transferring the project from my personal account to oVirt orgnization in github or gerrit? And then accept it as a full oVirt project after all the graduation requirements are matched. Thank you all in advance. Regards, Joey [1]: https://github.com/imjoey/ovirt-engine-sdk-go [2]: https://ovirt-jira.atlassian.net/browse/OVIRT-2460 [3]: https://www.ovirt.org/develop/release-management/releases/4.3/release-manag…

4 6

[VDSM] Network tests started to fail on Fedora 28 in travis
by Nir Soffer 15 Jan '19

15 Jan '19

________ ERROR at setup of TestOvsApiBase.test_execute_a_single_command ________ @pytest.fixture(scope='session', autouse=True) def ovs_service(): service = OvsService() with xfail_when_running_on_travis_with_centos(): > service.setup() network/integration/ovs/conftest.py:38: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = <network.ovsnettestlib.OvsService object at 0x7fbdc2256a58> def setup(self): if not self.ovs_init_state_is_up: cmd.exec_sync([OVS_CTL, '--system-id=random', 'start']) > assert self.is_service_running() E AssertionError This line looks wrong: with xfail_when_running_on_travis_with_centos() The test fail on Fedora: https://travis-ci.org/nirs/vdsm/jobs/480027211 https://travis-ci.org/nirs/vdsm/jobs/480027212 works on CentOS: https://travis-ci.org/nirs/vdsm/jobs/480027210 Looks like we need to switch the check to Fedora. I think this started to fail today, after I rebuild the Fedora 28 image: https://gerrit.ovirt.org/c/96847/ maybe an update in Fedora is related? Nir

1 1

[Call for Testing] oVirt 4.3.0
by Sandro Bonazzola 15 Jan '19

15 Jan '19

Hi, we are planning to release a 4.3.0 RC2 tomorrow morning, January 16th 2019. We have a scheduled final release for oVirt 4.3.0 on January 29th: this is the time when testing is most effective to ensure the release will be as much stable as possible. Please join us testing the RC2 release this week and reporting issues to https://bugzilla.redhat.com/enter_bug.cgi?classification=oVirt Please remember this is still pre-release material, we recommend not installing it on production environments yet. 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>

1 0

vdsm has been tagged (v4.30.6)
by Milan Zamazal 15 Jan '19

15 Jan '19

1 0

Error while executing action Attach Storage Domain: AcquireHostIdFailure
by Fedor Gavrilov 15 Jan '19

15 Jan '19

Hi, I'm setting up iSCSI domain on freshly installed ovirt and hitting subj when I try adding new data domain. After it's added it's in Unattached state and can't be removed either. I found something in bugzilla about NFS storage and sanlock, could it be related? I allocated iSCSI fileio storage on the same machine where host is (so I'm connecting 127.0.0.1:3260), was that my mistake? Thanks in advance, Fedor Gavrilov

2 3

SSO with lightdm
by jeremiah52＠naver.com 15 Jan '19

15 Jan '19

I knows there are the GDM plugin and KDM plugin of ovirt-guest-agent that makes SSO in linux is possible. I want to make SSO with lightdm is possble. To add lightdm plugin to ovirt-guest-agent is enough? or something more is needed? I don't know how to develop SSO with lightdm.

3 2

Hard disk requirement
by Hetz Ben Hamo 13 Jan '19

13 Jan '19

Hi, The old oVirt (3.x?) ISO image wasn't requiring a big hard disk in order to install the node part on a physical machine, since the HE and other parts were running using NFS/iSCSI etc. oVirt 4.X if I understand correctly - does require hard disk on the node. Can this requirement be avoided and just use an SD Card? Whats the minimum storage for the local node? Thanks, Hetz

2 1

Can we drop fc27 jobs / rpms from CI/tested repos?
by Eyal Edri 13 Jan '19

13 Jan '19

5 8

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

11 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 (#3) we have not had any failures since before the holidays. *CQ-Master:* YELLOW (#2) - We had two different code regressions for ovirt-engine and vdsm both were reported and solved during the week. - we had missing packages which were fixed with this patch: https://gerrit.ovirt.org/#/c/96831/ Last successful build for vdsm and ovirt-engine was today (11th Jan). Current status 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

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

10 Jan '19

1 1