June 2018 - Infra - oVirt List Archives

[JIRA] (OVIRT-2055) failure in suspend resume vm not related to reported change - need to investigate
by Dafna Ron (oVirt JIRA) 04 Jun '18

04 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2055?page=com.atlassian.jira.… ] Dafna Ron updated OVIRT-2055: ----------------------------- Labels: ost_failures ost_race (was: ost_failures) > failure in suspend resume vm not related to reported change - need to investigate > --------------------------------------------------------------------------------- > > Key: OVIRT-2055 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2055 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > Labels: ost_failures, ost_race > > Change 91507,1 (ovirt-engine-sdk-java) is probably the reason behind recent > system test failures in the "ovirt-master" change queue and needs to be fixed. > This change had been removed from the testing queue. Artifacts build from this > change will not be released until it is fixed. > For further details about the change see: > https://gerrit.ovirt.org/#/c/91507/1 > For failed test results see: > http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7721/ > I think the issue is on qemu/libvirt changed queries: > https://pastebin.com/afyeUAcT > https://pastebin.com/va20Y5Hp > checking his with vdsm people. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100086)

1 0

[JIRA] (OVIRT-1549) run OST as a third-party tester for OpenStack's ovsdbapp
by danken (oVirt JIRA) 04 Jun '18

04 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1549?page=com.atlassian.jira.… ] danken commented on OVIRT-1549: ------------------------------- [~eedri] I am not aware of ovsdbapp breaking us. However, openvswtich did, which would have been caught had we have such CI. I don't know if it is "worth it", as I have not estimated the resources needed, but I think that it would be beneficial for ovirt and its CI system. > run OST as a third-party tester for OpenStack's ovsdbapp > -------------------------------------------------------- > > Key: OVIRT-1549 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1549 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: oVirt CI > Reporter: danken > Assignee: infra > > https://github.com/openstack/ovsdbapp is a python binding for openvswitch-ovn. ovirt-provider-ovn is planning to use it instead of its own implementation. > ovsdbapp developers want to make sure they do not break the ovirt use case. I would like us to follow https://docs.openstack.org/infra/system-config/third_party.html and become a third-party tester of ovsdbapp. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100086)

1 0

[JIRA] (OVIRT-2072) build-artifacts job failed to fetch git with returned status code 143
by Dafna Ron (oVirt JIRA) 04 Jun '18

04 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2072?page=com.atlassian.jira.… ] Dafna Ron reassigned OVIRT-2072: -------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > build-artifacts job failed to fetch git with returned status code 143 > --------------------------------------------------------------------- > > Key: OVIRT-2072 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2072 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: Evgheni Dereveanchin > Labels: cq-issue-traking, ost_failures, ost_infra > > put vm offline (could not see a host in log) and re-ran the artifacts job. > Change 91568,10 (ovirt-provider-ovn) is probably the reason behind recent > system test failures in the "ovirt-master" change queue and needs to be fixed. > This change had been removed from the testing queue. Artifacts build from this > change will not be released until it is fixed. > For further details about the change see: > https://gerrit.ovirt.org/#/c/91568/10 > For failed test results see: > http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7993/ > 08:50:28 > git init /home/jenkins/workspace/ovirt-provider-ovn_master_build-artifacts-fc27-x86_64/ovirt-provider-ovn # timeout=10 > 08:50:28 Fetching upstream changes from git://gerrit.ovirt.org/ovirt-provider-ovn.git > 08:50:28 > git --version # timeout=10 > 08:50:28 > git fetch --tags --progress git://gerrit.ovirt.org/ovirt-provider-ovn.git +refs/heads/*:refs/remotes/origin/* > 09:00:28 ERROR: Timeout after 10 minutes > 09:00:28 ERROR: Error cloning remote repo 'origin' > 09:00:28 hudson.plugins.git.GitException: Command "git fetch --tags --progress git://gerrit.ovirt.org/ovirt-provider-ovn.git +refs/heads/*:refs/remotes/origin/*" returned status code 143: > 09:00:28 stdout: > 09:00:28 stderr: remote: Counting objects: 84340 -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100086)

1 0

[JIRA] (OVIRT-2078) Check option for private changes on Gerrit
by eyal edri (oVirt JIRA) 04 Jun '18

04 Jun '18

eyal edri created OVIRT-2078: -------------------------------- Summary: Check option for private changes on Gerrit Key: OVIRT-2078 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2078 Project: oVirt - virtualization made easy Issue Type: Task Reporter: eyal edri Assignee: infra Priority: High We need an option sometimes to post private changes ( not draft ) to Gerrit, Gerrit has support for private changes [1], we should check if its available in current version. [1] https://gerrit-review.googlesource.com/Documentation/intro-user.html#privat… -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100086)

1 0

[CQ]: 91885, 1 (ovirt-dwh) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 04 Jun '18

04 Jun '18

A system test invoked by the "ovirt-4.2" change queue including change 91885,1 (ovirt-dwh) failed. However, this change seems not to be the root cause for this failure. Change 91877,1 (ovirt-dwh) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 91877,1 (ovirt-dwh) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/91885/1 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/91877/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/2278/

2 1

[JIRA] (OVIRT-1466) Switch to deploying JJB via PIP
by eyal edri (oVirt JIRA) 04 Jun '18

04 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1466?page=com.atlassian.jira.… ] eyal edri updated OVIRT-1466: ----------------------------- Summary: Switch to deploying JJB via PIP (was: Switche to deploying JJB via PIP) > Switch to deploying JJB via PIP > ------------------------------- > > Key: OVIRT-1466 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1466 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: JJB > Reporter: Barak Korren > Assignee: infra > Labels: jjb, standard-ci > > Since the JJB deployment job runs directly on the Jenkins master, we've been creating and using an RPM package for JJB. This made it hard to switch JJB versions. > Once we implement OVIRT-1465, we gain sufficient isolation via mock to allow ourselves to install JJB via pip. > We can set things up so that pip installs a specific JJB version, that way we can gate JJB version updates and have then checked by check-patch. We can even expand the upstream polling system to track JJB versions for us and create update patches. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100086)

1 0

[JIRA] (OVIRT-1993) Looking for a new task to help with
by eyal edri (oVirt JIRA) 04 Jun '18

04 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1993?page=com.atlassian.jira.… ] eyal edri commented on OVIRT-1993: ---------------------------------- Here is a filter which shows you all the first_time_tasks: https://ovirt-jira.atlassian.net/issues/?filter=12803 You can also check the full backlog of tasks here [1] to see if something is appealing for you. Feel free to comment on a specific task for more info. [1] https://ovirt-jira.atlassian.net/secure/RapidBoard.jspa?projectKey=OVIRT&ra… > Looking for a new task to help with > ----------------------------------- > > Key: OVIRT-1993 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1993 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: sailesh baskar > Assignee: infra > > I would like to open a new ticket in the infrastructure team. Can you help > in the process? -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100086)

1 0

CI error
by Ala Hino 04 Jun '18

04 Jun '18

Hi, I am facing the following CI error on an engine patch: *11:49:30* Traceback (most recent call last):*11:49:30* File "/usr/bin/isort", line 6, in <module>*11:49:30* from pkg_resources import load_entry_point*11:49:30* File "/usr/lib/python2.7/site-packages/pkg_resources/__init__.py", line 3095, in <module>*11:49:30* @_call_aside*11:49:30* File "/usr/lib/python2.7/site-packages/pkg_resources/__init__.py", line 3079, in _call_aside*11:49:30* f(*args, **kwargs)*11:49:30* File "/usr/lib/python2.7/site-packages/pkg_resources/__init__.py", line 3108, in _initialize_master_working_set*11:49:30* working_set = WorkingSet._build_master()*11:49:30* File "/usr/lib/python2.7/site-packages/pkg_resources/__init__.py", line 570, in _build_master*11:49:30* ws.require(__requires__)*11:49:30* File "/usr/lib/python2.7/site-packages/pkg_resources/__init__.py", line 888, in require*11:49:30* needed = self.resolve(parse_requirements(requirements))*11:49:30* File "/usr/lib/python2.7/site-packages/pkg_resources/__init__.py", line 774, in resolve*11:49:30* raise DistributionNotFound(req, requirers)*11:49:30* pkg_resources.DistributionNotFound: The 'futures' distribution was not found and is required by isort*11:49:30* + exit 1*11:49:30* make: *** [Makefile:342: validations] Error 1 Patch: https://gerrit.ovirt.org/#/c/91841/ CI Log: https://jenkins.ovirt.org/job/ovirt-engine_master_check-patch-fc28-x86_64/5…

3 2

[ OST Failure Report ] [ oVirt master (ovirt-engine) ] [ 03.06.18 ] [098_ovirt_provider_ovn.use_ovn_provider ]
by Gal Ben Haim 03 Jun '18

03 Jun '18

Specifically, it failed to unplug a nic from a VM. Suspected patches: https://gerrit.ovirt.org/#/c/91195/ Link to Job: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/8019/ Link to all logs: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/8019/artifac… (Relevant) error snippet from the log: <error> 2018-06-03 06:35:30,764-04 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.HotUnplugNicVDSCommand] (default task-1) [32c965fd] FINISH, HotUnplugNicVDSCommand, return: , log id: 18d9b4e9 2018-06-03 06:35:30,764-04 DEBUG [org.ovirt.engine.core.common.di.interceptor.DebugLoggingInterceptor] (default task-1) [32c965fd] method: runVdsCommand, params: [HotUnplugNic, VmNicDeviceVDSParameters:{hostId='d0f5b521-ed04-4b9e-9524-7f8d4be842d0', vm.vm_name='vm0', nic='VmNic:{id='9419aca6-2fae-4851-a902-a6b5a88ac691', vnicProfileId='8d12fcbb-23e8-432d-845a-ab2b97039955', speed='10000', type='3', macAddress='00:1a:4a:16:01:0e', linked='true', vmId='ec4303e9-2b7a-451d-9f43-836c29767652', vmTemplateId='null'}', vmDevice='VmDevice:{id='VmDeviceId:{deviceId='9419aca6-2fae-4851-a902-a6b5a88ac691', vmId='ec4303e9-2b7a-451d-9f43-836c29767652'}', device='bridge', type='INTERFACE', specParams='[]', address='', managed='true', plugged='true', readOnly='false', deviceAlias='', customProperties='[]', snapshotId='null', logicalName='null', hostDevice='null'}'}], timeElapsed: 55ms 2018-06-03 06:35:30,765-04 ERROR [org.ovirt.engine.core.bll.network.vm.ActivateDeactivateVmNicCommand] (default task-1) [32c965fd] Command 'org.ovirt.engine.core.bll.network.vm.ActivateDeactivateVmNicCommand' failed: EngineException: org.ovirt.engine.core.vdsbroker.vdsbroker.VDSErrorException: VDSGenericException: VDSErrorException: Failed to HotUnplugNicVDS, error = General Exception: ('macAddr',), code = 100 (Failed with error GeneralException and code 100) 2018-06-03 06:35:30,774-04 DEBUG [org.ovirt.engine.core.common.di.interceptor.DebugLoggingInterceptor] (default task-1) [32c965fd] method: get, params: [d0f5b521-ed04-4b9e-9524-7f8d4be842d0], timeElapsed: 3ms 2018-06-03 06:35:30,781-04 DEBUG [org.ovirt.engine.core.utils.timer.FixedDelayJobListener] (DefaultQuartzScheduler5) [] Rescheduling DEFAULT.org.ovirt.engine.core.bll.gluster.GlusterSyncJob.refreshLightWeightData#-9223372036854775795 as there is no unfired trigger. 2018-06-03 06:35:30,781-04 DEBUG [org.ovirt.engine.core.utils.timer.FixedDelayJobListener] (DefaultQuartzScheduler6) [] Rescheduling DEFAULT.org.ovirt.engine.core.bll.gluster.GlusterServiceSyncJob.refreshGlusterServices#-9223372036854775801 as there is no unfired trigger. 2018-06-03 06:35:30,782-04 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-1) [32c965fd] EVENT_ID: NETWORK_DEACTIVATE_VM_INTERFACE_FAILURE(1,015), Failed to unplug Network Interface eth2 (VirtIO) from VM vm0. (User: admin@internal-authz) 2018-06-03 06:35:30,791-04 DEBUG [org.ovirt.engine.core.dal.dbbroker.PostgresDbEngineDialect$PostgresSimpleJdbcCall] (default task-1) [32c965fd] Compiled stored procedure. Call string i </error> -- *GAL bEN HAIM* RHV DEVOPS

2 3

[JIRA] (OVIRT-983) Improve CI output for Jenkins repo
by Barak Korren (oVirt JIRA) 03 Jun '18

03 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-983?page=com.atlassian.jira.p… ] Barak Korren commented on OVIRT-983: ------------------------------------ No. But the approach we'd take today would be to display the information on the page implemented in OVIRT-2050. [~dbelenky(a)redhat.com] did we create a ticket already for displaying HTML reports on the STDCI V2 page? If we did we can mark this as a duplicate. > Improve CI output for Jenkins repo > ---------------------------------- > > Key: OVIRT-983 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-983 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt CI > Reporter: Barak Korren > Assignee: infra > > Since we've added more ci jobs to the {{jenkins}} repo, the CI output because unclear. When it was one job, it was easy to understand it failed because of YAML issues. Now, when it passes on all platforms but el7, its easy to mistake this for a infra failure on el7 rather then a real problem with the patch. > The following improvements should be made to the job output: > # The YAML failure message should be placed directly in the Gerrit comment, this can be done with the "Unsuccessful Message File" feature of the Gerrit plugin. > # When YAML check succeeds ther sohuld be a message in Gerrit saying so and indicating where the DIFF output can be seen (will "Unsuccessful Message File" also work on success?) > # The {{differences.html}} file should probably be called {{index.html}} to get it placed in the job status page. > # Maybe add some javascript to {{differences.html}} to allow collapsing individual differences. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100086)

1 0