- Devel - oVirt List Archives

[REQUEST FOR COMMENTS] oVirt features tracking and documentation
by Sandro Bonazzola 26 Feb '17

26 Feb '17

Hi, I'm facing a new challenge today, I see new features getting pushed to oVirt gerrit intentionally out of bugzilla. The specific case is not really relevant, but just for reference: https://gerrit.ovirt.org/#/c/65761/ . Looks like we'll see features getting merged without any RFE opened in bugzilla for them. With current workflow, auto-generating release notes from bugzilla doc-texts. this means they won't ever be documented. I'd like to open this public discussion getting comments about how things will be handled. Thanks, -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

5 8

[HEADS UP] ovift-engine: repository closure check on check-patch
by Sandro Bonazzola 26 Feb '17

26 Feb '17

Hi, with the following commits: - https://gerrit.ovirt.org/71553 - https://gerrit.ovirt.org/71623 a minimal repository closure check is added to check-patches.sh. Instead of performing a full blown repository closure, I limited the check to the built rpms in oreder to reduce the risk of hitting repository closure errors due to different projects. This should help dropping the long time failing repository closure jobs which are struggling to keep the pace with the changes we introduce in master. It should also help avoiding to merge patches which will break the repository and the plain rpm install flow. The second patch switch from ovirt-master-release to experimental repo. Here I need infra input, not sure experimental is the desired repo, deisgned to replace ovirt-master-snapshot. Thanks, -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

2 4

Vdsm build failure
by Piotr Kliczewski 24 Feb '17

24 Feb '17

Nir, I saw this issue in [1]: 10:20:12 FAIL: test_send_receive (storage_mailbox_test.TestMailbox) 10:20:12 ---------------------------------------------------------------------- 10:20:12 Traceback (most recent call last): 10:20:12 File "/home/jenkins/workspace/vdsm_master_check-patch-fc25-x86_64/vdsm/tests/storage_mailbox_test.py", line 132, in test_send_receive 10:20:12 self.assertFalse(expired, 'message was not processed on time') 10:20:12 AssertionError: message was not processed on time it is something known? Thanks, Piotr [1] http://jenkins.ovirt.org/job/vdsm_master_check-patch-fc25-x86_64/1541/conso…

2 4

planned Jenkins restart
by Evgheni Dereveanchin 24 Feb '17

24 Feb '17

Hi everyone, I'll be performing a planned Jenkins restart within the next hour. No new builds will be scheduled during this maintenance period. I will announce you once it is finished. Regards, Evgheni Dereveanchin

1 1

[ OST Failure Report ] [ oVirt master ] [ 22/02/2017 ] [add_secondary_storage_domains]
by Barak Korren 23 Feb '17

23 Feb '17

Test failed: [ add_secondary_storage_domains ] Note: - This may or may not be related to https://bugzilla.redhat.com/show_bug.cgi?id=1421945 The BZ talks about sporadic failures, while this seems to be happening consistently (for 6 runs so far) Link to suspected patches: - https://gerrit.ovirt.org/70415 - https://gerrit.ovirt.org/69157 Link to Job: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/5487/ Link to all logs: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/5487/artif… Error snippet from log: <error> RequestError: status: 400 reason: Bad Request detail: Cannot import Virtual Disk: Storage Domain cannot be accessed. -Please check that at least one Host is operational and Data Center state is up. </error> http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/5487/testR… -- Barak Korren bkorren(a)redhat.com RHCE, RHCi, RHV-DevOps Team https://ifireball.wordpress.com/

4 13

oVirt Engine 4.1.1 has been branched out
by Tal Nisan 23 Feb '17

23 Feb '17

Hi everyone, Since we've moved to blocker/exception only mode we've branched oVirt engine 4.1.1 today from the ovirt-engine-4.1 branch to allow work on 4.1.3 bugs. >From this moment on 4.1.1 engine bugs have to be merged to: master ovirt-engine-4.1 ovirt-engine-4.1.1.z For 4.1.3 only the first 2 branches. Thanks.

5 8

[ OST Failure Report ] [ oVirt master ] [ 22/2/2017 ] [prepare_migration_attachments_ipv4]
by Barak Korren 23 Feb '17

23 Feb '17

Test failed: [ prepare_migration_attachments_ipv4 ] Link to suspected patches: - Link to Job: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/5480/ Link to all logs: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/5480/artif… Error snippet from log: <error> status: 409 reason: Conflict detail: Cannot setup Networks. Operation can be performed only when Host status is Maintenance, Up, NonOperational. </error> -- Barak Korren bkorren(a)redhat.com RHCE, RHCi, RHV-DevOps Team https://ifireball.wordpress.com/

2 2

[Important!][Action required!] CI-whitelist re-activated
by Barak Korren 23 Feb '17

23 Feb '17

TL;DR: If you are a patch author, please ask your project maintainer to have you added to the CI whitelist. The oVirt CI system tries to be a useful and powerful tool for patch authors and project maintainers. With the current CI-standards, power is placed in the hands of patch authors to make the system do almost anything. We try to be an "open" Open-Source project, so permission is given to anyone to open a Gerrit account and submit patches. The above opens the door to the CI system being maliciously exploited, so some countermeasure was needed. The builders of the CI system foresaw this and have put in place a white-list mechanism that makes the CI system only run jobs for patches that come from listed authors. In recent years the CI system had been re-engineered with the push towards the CI standards, and the whitelist mechanism was rendered non-active. Finally realizing the potential for harm, we acted quickly to re-enable the whitelist mechanism. We made an effort to include current authors and maintainers, but we do not know everyone. People not included in the whitelist will see the following message when submitting patches: To avoid overloading the infrastructure, a whitelist for running gerrit triggered jobs has been set in place, if you feel like you should be in it, please contact infra at ovirt dot org If you come across this message, please ask the project maintainer to send a message to the infra team asking for you to added to the CI whitelist. We'd rather not receive direct messages from individual contributors, because we do not know everyone and cannot verify sources. We (the infra team) know that the current mechanism can sound draconian and be inconvenient. But we had to put something in place quickly. Please join the discussion at [1] to improve it. [1]: https://ovirt-jira.atlassian.net/browse/OVIRT-1154 -- Barak Korren bkorren(a)redhat.com RHCE, RHCi, RHV-DevOps Team https://ifireball.wordpress.com/

4 6

OST: HE vm does not restart on HC setup
by Sahina Bose 22 Feb '17

22 Feb '17

Hi all, On the HC setup, the HE VM is not restarted. The agent.log has MainThread::INFO::2017-02-21 22:09:58,022::state_machine::169::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(refresh) Global metadata: {} MainThread::INFO::2017-02-21 22:09:58,023::state_machine::177::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(refresh) Local (id 1): {'engine-health': {'reason': 'failed to getVmStats', 'health': 'unknown', 'vm': 'unknown', 'detail': 'unknown'}, 'bridge': True, 'mem-free': 4079.0, 'maintenance': False, 'cpu-load': 0.0491, 'gateway': True} ... MainThread::INFO::2017-02-21 22:10:29,219::state_decorators::25::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(check) Unknown local engine vm status no actions taken MainThread::INFO::2017-02-21 22:10:29,219::brokerlink::111::ovirt_hosted_engine_ha.lib.brokerlink.BrokerLink::(notify) Trying: notify time=1487733029.22 type=state_transition detail=ReinitializeFSM-UnknownLocalVmState hostname='lago-hc-basic-suite-master-host0' MainThread::INFO::2017-02-21 22:10:29,317::brokerlink::121::ovirt_hosted_engine_ha.lib.brokerlink.BrokerLink::(notify) Success, was notification of state_transition (ReinitializeFSM-UnknownLocalVmState) sent? ignored and the vdsm.log 2017-02-21 22:09:11,962-0500 INFO (libvirt/events) [virt.vm] (vmId='2ccc0ef0-cc31-45b8-8e91-a78fa4cad671') Changed state to Down: User shut down from within the guest (code=7) (vm:1269) 2017-02-21 22:09:11,962-0500 INFO (libvirt/events) [virt.vm] (vmId='2ccc0ef0-cc31-45b8-8e91-a78fa4cad671') Stopping connection (guestagent:429) 2017-02-21 22:09:29,727-0500 ERROR (jsonrpc/4) [api] FINISH getStats error=Virtual machine does not exist: {'vmId': u'2ccc0ef0-cc31-45b8-8e91-a78fa4cad671'} (api:69) Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/vdsm/common/api.py", line 67, in method ret = func(*args, **kwargs) File "/usr/share/vdsm/API.py", line 335, in getStats vm = self.vm File "/usr/share/vdsm/API.py", line 130, in vm raise exception.NoSuchVM(vmId=self._UUID) NoSuchVM: Virtual machine does not exist: {'vmId': u'2ccc0ef0-cc31-45b8-8e91-a78fa4cad671'} What should I be looking for to identify the issue? The logs are at http://jenkins.ovirt.org/job/ovirt_master_hc-system-tests/lastCompletedBuil… thanks sahina

7 10

moVirt 1.7 RC 1
by Tomas Jelinek 22 Feb '17

22 Feb '17

Hey All, the first public RC of moVirt 1.7 has been released! [3] It can be downloaded only using direct link [1] - the play store will be upgraded once it is considered stable. This release has many enhancements, most notably: - enhanced dashboard + a documentation written explaining how the values are actually calculated [2] - support for signed certificates for communication with oVirt API (e.g. not self signed ones) - support for SPICE + VNC and made SPICE connection more stable (thanx Iordan!). To enjoy the fixes, please update aSPICE to 4.2 + many smaller enhancements/fixes Big thanx to everyone who have contributed to this RC! Would you also like to help/contribute? Sure, for example you can: - download RC [1], test it and report bugs (here to thread or to [4]) - patches are always welcome :) have a nice day, Tomas [1]: https://github.com/matobet/moVirt/blob/master/moVirt/moVirt-release.apk?raw… [2]: https://github.com/matobet/moVirt/wiki/User%27s-guide#dashboard [3]: https://github.com/matobet/moVirt [4]: https://github.com/matobet/moVirt/issues

1 0