January 2019 - Devel - oVirt List Archives

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

18 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*: RED (#1) one issue still pending: 1. ovirt-provider-ovn is failing due to change https://gerrit.ovirt.org/#/c/96926/ - ip_version is mandatory on POSTs The change is failing the ost test because ip version needs to be specifically provided as a result of introducing v6 There is a patch by Miguel which I merged. there are a few patches in test now so waiting to see if the patch fixes the issue. https://gerrit.ovirt.org/#/c/97072/ - basic-suite-42: align w/ networking API Jira: https://ovirt-jira.atlassian.net/browse/OVIRT-2655 *CQ-Master:* GREEN (#2) Last failure was on Jan 14th for project ovirt-ansible-hosted-engine-setup. The project was failing on https://docs.fedoraproject.org/en-US/packaging-guidelines/Directory_Replace… Jira was closed today as projects are passing: https://ovirt-jira.atlassian.net/browse/OVIRT-2650 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

[ OST Failure Report ] [ oVirt 4.2 (ovirt-ansible-hosted-engine-setup) ] [ 14-01-2019 ] [ 001_upgrade_engine.test_initialize_engine]
by Dafna Ron 18 Jan '19

18 Jan '19

Hi, we are failing test 001_upgrade_engine.test_initialize_engine on ovirt 4.2 for project ovirt-ansible-hosted-engine-setup. Patch reported by CQ: https://github.com/oVirt/ovirt-ansible-hosted-engine-setup/commit/860f6a69d… - Rename the role - replacing '-' with '_' Ido, can you please check this issue? failed build: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/3712/ error: [ INFO ] Checking for an update for Setup... An update for the Setup packages ovirt-engine-setup ovirt-engine-setup-plugin-websocket-proxy ovirt-engine-dwh-setup was found. Please update that package by running: "yum update ovirt-engine-setup ovirt-engine-setup-plugin-websocket-proxy ovirt-engine-dwh-setup" and then execute Setup again. [ ERROR ] Failed to execute stage 'Environment customization': Please update the Setup packages [ INFO ] Stage: Clean up Log file is located at /var/log/ovirt-engine/setup/ovirt-engine-setup-20190114053840-4ysu6y.log [ INFO ] Generating answer file '/var/lib/ovirt-engine/setup/answers/20190114053855-setup.conf' [ INFO ] Stage: Pre-termination [ INFO ] Stage: Termination [ ERROR ] Execution of setup failed ('FATAL Internal error (main): Please update the Setup packages',) lago.ssh: DEBUG: Command 8e6b18d0 on lago-upgrade-from-release-suite-4-2-engine errors: Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/otopi/__main__.py", line 88, in main installer.execute() File "/usr/lib/python2.7/site-packages/otopi/main.py", line 157, in execute self.context.runSequence() File "/usr/lib/python2.7/site-packages/otopi/context.py", line 771, in runSequence util.raiseExceptionInformation(infos[0]) File "/usr/lib/python2.7/site-packages/otopi/util.py", line 81, in raiseExceptionInformation exec('raise info[1], None, info[2]') 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-common/distro-rpm/packages.py", line 410, in _customization raise RuntimeError(_('Please update the Setup packages')) RuntimeError: Please update the Setup packages Error Thanks, Dafna

4 8

ovirt-containers - is this project still alive?
by Sandro Bonazzola 18 Jan '19

18 Jan '19

Hi, I was removing 4.1 jenkins job and found out a 4.1 job for ovirt-containers project. Owners are Fabian Deutsch and Evgheni Dereveanchin, in CC. Contributors are Juan Hernandez and Simone Tiraboschi. I see no activity there in a while, jobs have not been created for 4.2. Is this an abandoned project? Can we drop jenkins jobs at all? 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>

3 3

[ OST Failure Report ] [ oVirt 4.2 (ovirt-provider-ovn) ] [ 18-01-2019 ] [ 098_ovirt_provider_ovn.use_ovn_provider ]
by Dafna Ron 18 Jan '19

18 Jan '19

Hi, We have a failure in ovn tests in branch 4.2. Marcin/Miguel, can you please take a look? Jira opened: https://ovirt-jira.atlassian.net/browse/OVIRT-2655 Link and headline of suspected patches: https://gerrit.ovirt.org/#/c/96926/ - ip_version is mandatory on POSTs Link to Job: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/3742/ Link to all logs: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/3742/artifact/ba… (Relevant) error snippet from the log: <error> 2019-01-18 00:14:30,591 root Starting server 2019-01-18 00:14:30,592 root Version: 1.2.19-0.20190117180529.gite1d4195 2019-01-18 00:14:30,592 root Build date: 20190117180529 2019-01-18 00:14:30,592 root Githash: e1d4195 2019-01-18 00:20:39,394 ovsdbapp.backend.ovs_idl.vlog ssl:127.0.0.1:6641: no response to inactivity probe after 5.01 seconds, disconnecting 2019-01-18 00:45:01,435 root From: ::ffff:192.168.200.1:49008 Request: POST /v2.0/subnets/ 2019-01-18 00:45:01,435 root Request body: {"subnet": {"network_id": "99c260ec-dad4-40b9-8732-df32dd54bd00", "dns_nameservers": ["8.8.8.8"], "cidr": "1.1.1.0/24", "gateway_ip": "1.1.1.1", "name": "subnet_1"}} 2019-01-18 00:45:01,435 root Missing 'ip_version' attribute Traceback (most recent call last): File "/usr/share/ovirt-provider-ovn/handlers/base_handler.py", line 134, in _handle_request method, path_parts, content File "/usr/share/ovirt-provider-ovn/handlers/selecting_handler.py", line 175, in handle_request return self.call_response_handler(handler, content, parameters) File "/usr/share/ovirt-provider-ovn/handlers/neutron.py", line 36, in call_response_handler return response_handler(ovn_north, content, parameters) File "/usr/share/ovirt-provider-ovn/handlers/neutron_responses.py", line 154, in post_subnets subnet = nb_db.add_subnet(received_subnet) File "/usr/share/ovirt-provider-ovn/neutron/neutron_api_mappers.py", line 74, in wrapper validate_rest_input(rest_data) File "/usr/share/ovirt-provider-ovn/neutron/neutron_api_mappers.py", line 596, in validate_add_rest_input raise BadRequestError('Missing \'ip_version\' attribute') BadRequestError: Missing 'ip_version' attribute </error>

3 3

[VDSM] FAIL: test_add_delete_ipv6 (network.ip_address_test.IPAddressTest) fail again
by Nir Soffer 16 Jan '19

16 Jan '19

We had this failure a lot in the past and it seems to be resolve, but I see it again today: ====================================================================== FAIL: test_add_delete_ipv6 (network.ip_address_test.IPAddressTest) ---------------------------------------------------------------------- Traceback (most recent call last): File "/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/tests/testValidation.py", line 333, in wrapper return f(*args, **kwargs) File "/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/tests/network/ip_address_test.py", line 226, in test_add_delete_ipv6 self._test_add_delete(IPV6_A_WITH_PREFIXLEN, IPV6_B_WITH_PREFIXLEN) File "/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/tests/network/ip_address_test.py", line 247, in _test_add_delete self._assert_has_no_address(nic, ip_b) File "/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/tests/network/ip_address_test.py", line 344, in _assert_has_no_address self._assert_address_not_in(address_with_prefixlen, addresses) File "/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/tests/network/ip_address_test.py", line 352, in _assert_address_not_in self.assertNotIn(address_with_prefixlen, addresses_list) AssertionError: '2002:99::1/64' unexpectedly found in ['2002:99::1/64', '2001:99::1/64', 'fe80::6:23ff:fead:ed34/64'] -------------------- >> begin captured logging << -------------------- 2019-01-04 16:01:53,543 DEBUG (MainThread) [root] /sbin/ip link add name dummy_NKzY1 type dummy (cwd None) (cmdutils:133) 2019-01-04 16:01:53,559 DEBUG (MainThread) [root] SUCCESS: <err> = ''; <rc> = 0 (cmdutils:141) 2019-01-04 16:01:53,563 DEBUG (netlink/events) [root] START thread <Thread(netlink/events, started daemon 139806010234624)> (func=<bound method Monitor._scan of <vdsm.network.netlink.monitor.Monitor object at 0x7f271d654cd0>>, args=(), kwargs={}) (concurrent:193) 2019-01-04 16:01:53,567 DEBUG (MainThread) [root] /sbin/ip link set dev dummy_NKzY1 up (cwd None) (cmdutils:133) 2019-01-04 16:01:53,586 DEBUG (MainThread) [root] SUCCESS: <err> = ''; <rc> = 0 (cmdutils:141) 2019-01-04 16:01:53,593 DEBUG (netlink/events) [root] FINISH thread <Thread(netlink/events, started daemon 139806010234624)> (concurrent:196) 2019-01-04 16:01:53,597 DEBUG (MainThread) [root] /sbin/ip -6 addr add dev dummy_NKzY1 2001:99::1/64 (cwd None) (cmdutils:133) 2019-01-04 16:01:53,615 DEBUG (MainThread) [root] SUCCESS: <err> = ''; <rc> = 0 (cmdutils:141) 2019-01-04 16:01:53,620 DEBUG (MainThread) [root] /sbin/ip -6 addr add dev dummy_NKzY1 2002:99::1/64 (cwd None) (cmdutils:133) 2019-01-04 16:01:53,632 DEBUG (MainThread) [root] SUCCESS: <err> = ''; <rc> = 0 (cmdutils:141) 2019-01-04 16:01:53,639 DEBUG (MainThread) [root] /sbin/ip -6 addr del dev dummy_NKzY1 2002:99::1/64 (cwd None) (cmdutils:133) 2019-01-04 16:01:53,656 DEBUG (MainThread) [root] SUCCESS: <err> = ''; <rc> = 0 (cmdutils:141) 2019-01-04 16:01:53,670 DEBUG (MainThread) [root] /sbin/ip link del dev dummy_NKzY1 (cwd None) (cmdutils:133) 2019-01-04 16:01:53,705 DEBUG (MainThread) [root] SUCCESS: <err> = ''; <rc> = 0 (cmdutils:141) --------------------- >> end captured logging << --------------------- Build: https://jenkins.ovirt.org/blue/rest/organizations/jenkins/pipelines/vdsm_st…

2 6

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

s390x repository closure issue
by Sandro Bonazzola 09 Jan '19

09 Jan '19

Hi, just an heads up that s390x repository is failing repository closure: *00:05:15.127* Problem 2: package ovirt-host-dependencies-4.3.0-0.2.master.20190109065452.gite6c98f4.fc28.s390x requires vdsm >= 4.30.3, but none of the providers can be installed*00:05:15.127* - package vdsm-4.30.3-1.fc28.s390x requires ovirt-imageio-daemon >= 1.2.0, but none of the providers can be installed*00:05:15.127* - conflicting requests*00:05:15.127* - nothing provides ovirt-imageio-common = 1.5.0 needed by ovirt-imageio-daemon-1.5.0-0.201901061027.gita4be4ca.fc28.noarch*00:05:15.127* - nothing provides libvirt-daemon-kvm >= 4.9.0-1 needed by vdsm-4.30.4-92.git2282ef29b.fc28.s390x*00:05:15.127* - nothing provides ovirt-imageio-common = 1.4.6 needed by ovirt-imageio-daemon-1.4.6-1.fc28.noarch*00:05:15.127* - nothing provides libvirt-daemon-kvm >= 4.9.0-1 needed by vdsm-4.30.4-1.fc28.s390x If you can provide missing dependencies please let me know. 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

oVirt 4.3.0 RC build delay
by Sandro Bonazzola 08 Jan '19

08 Jan '19

As per subject, Jenkins is under maintenance so no build can be done till maintenance is completed. -- 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 1

Jenkins Jobs Are Not Always Triggered From Gerrit
by Anton Marchukov 08 Jan '19

08 Jan '19

Hello All. We noted that jenkins CI jobs are not always triggered for gerrit changes. While we are investigating this, I want to remind that you always can trigger / re-trigger check-patch jobs yourself. Just go to to the link [1], insert your change id and trigger it. Thanks. [1] https://jenkins.ovirt.org/gerrit_manual_trigger/ -- Anton Marchukov Team Lead - Release Management - RHV DevOps - Red Hat

2 2

vdsm has been tagged (v4.30.5)
by Milan Zamazal 08 Jan '19

08 Jan '19

1 0

ovirt-engine has been tagged (ovirt-engine-4.2.8.2)
by Tal Nisan 07 Jan '19

07 Jan '19

1 0

vdsm has been tagged (v4.20.46)
by Milan Zamazal 07 Jan '19

07 Jan '19

1 0

Please review "dump-chains-sqlite"
by Germano Veit Michel 07 Jan '19

07 Jan '19

Hi, With these 2 changes the ovirt-log-collector will collect storage domain metadata from all storage domains of the environment in a more efficient way. https://gerrit.ovirt.org/#/q/topic:dump-chains-sqlite I'll be away for the next 2 weeks, but reviews are welcome. If there is any problem with one of these patches, please don't merge any of them as they require each other. And if you have extra time, reviews are welcome on this series too =D https://gerrit.ovirt.org/#/q/topic:snapshot-tools Thanks, Germano

2 2

preventing modifications of exiting upgrade scripts
by Eli Mesika 03 Jan '19

03 Jan '19

Hi Please note that patch[1] was merged. This patch will prevent(with a detailed ERROR[2]) any attempt to modify an existing DB upgrade script since this may lead to upgrade problems. The correct way to change something in the database is a new upgrade script. In a case that the upgrade script must be changed, this can be forced by adding a special keyword[3] to your commit header. Please see [1] description for details. If you have any questions, please let me know. [1] https://gerrit.ovirt.org/#/c/96421/ [2] [ERROR] : Changing an existing upgrade script is dangerous and can cause upgrade problems, if you are doing that in purpose and sure that there is no other way to fix the issue you are working on, please add the key 'Allow-db-upgrade-script-changes:Yes' to your patch commit message." [3] "Allow-db-upgrade-script-changes:Yes" Thanks Eli Mesika

1 0

Failed to add host to oVirt
by Eyal Shenitzky 02 Jan '19

02 Jan '19

Hey, I am failing to add a host to oVirt due to the following error: 2018-12-23 11:15:29,482+0200 ERROR otopi.context context._executeMethod:152 Failed to execute stage 'Environment customization': Cannot find a valid baseurl for repo: ovirt -master-centos-gluster5/7Server/x86_64 Does someone encounter this issue? -- Regards, Eyal Shenitzky

2 1