- Infra - oVirt List Archives

[JIRA] (OVIRT-2076) name clash on vdsm module at host-deploy
by Dafna Ron (oVirt JIRA) 04 Jun '18

04 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2076?page=com.atlassian.jira.… ] Dafna Ron commented on OVIRT-2076: ---------------------------------- [~stirabos(a)redhat.com] can you please add some info on how is the change resolved this error and if it it would effect any other projects? > name clash on vdsm module at host-deploy > ---------------------------------------- > > Key: OVIRT-2076 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2076 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > Labels: cq-issue-traking, ost_code_regression, ost_failures > > Add host is failing and was reported by gal for hc > https://jenkins.ovirt.org/view/oVirt%20system%20tests/job/ovirt-system-test… > (Relevant) error snippet from the host deploy log: > <error> > 2018-05-30 05:30:09,706-0400 DEBUG otopi.plugins.otopi.dialog.machine dialog.__logString:204 DIALOG:SEND **%EventStart STAGE misc METHOD otopi.plugins.ovirt_host_deploy.hosted-engine.configureha.Plugin._set_ha_conf (None) > 2018-05-30 05:30:09,713-0400 ERROR otopi.plugins.ovirt_host_deploy.hosted-engine.configureha configureha._set_ha_conf:114 HA client was not imported > 2018-05-30 05:30:09,713-0400 DEBUG otopi.context context._executeMethod:143 method exception > Traceback (most recent call last): > File "/tmp/ovirt-lQCcc6VFAV/pythonlib/otopi/context.py", line 133, in _executeMethod > method['method']() > File "/tmp/ovirt-lQCcc6VFAV/otopi-plugins/ovirt-host-deploy/hosted-engine/configureha.py", line 116, in _set_ha_conf > _('Cannot resolve ovirt_hosted_engine_ha module') > RuntimeError: Cannot resolve ovirt_hosted_engine_ha module -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100086)

1 0

[JIRA] (OVIRT-2074) missing dependency for python-isort
by Dafna Ron (oVirt JIRA) 04 Jun '18

04 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2074?page=com.atlassian.jira.… ] Dafna Ron commented on OVIRT-2074: ---------------------------------- [~sbonazzo(a)redhat.com] can you please update on the status of the bug and when should we see this resolved? > missing dependency for python-isort > ----------------------------------- > > Key: OVIRT-2074 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2074 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > Labels: cq-issue-traking, ost_failures > > need to change fc27 to fc28 to fix the failures. > Sandro submitted a change for some projects but some are still missing. > Sandro: > Fix is here: https://gerrit.ovirt.org/91769 ; needs an engine to be built on fedora to pass CI, I'm on it. > Going on failures, I will help him with the change for failed projects build-artifacts with the same issue. -- 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 eyal edri (oVirt JIRA) 04 Jun '18

04 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1549?page=com.atlassian.jira.… ] eyal edri commented on OVIRT-1549: ---------------------------------- The repo you provided has an 'openstack-netron-openvswitch' pkg, so we can't use it because it has different naming that what oVirt uses right? Is there a different repo that has nightly builds or something similar that can we used in OST? > 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-2054) false change reported since package is not deployed on ost
by Dafna Ron (oVirt JIRA) 04 Jun '18

04 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2054?page=com.atlassian.jira.… ] Dafna Ron updated OVIRT-2054: ----------------------------- Labels: ost_failures ost_race (was: ost_failures) > false change reported since package is not deployed on ost > ---------------------------------------------------------- > > Key: OVIRT-2054 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2054 > 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/ > The package is not deployed on OST so it could not have been the reason for failure. > + I am investigating the cause of failure but since we do not deploy the package on ost there is actually no chance that the failure was due to the change - hence its false report. > Is there a way to check if a project is deployed on ost? do we even need to run ost on it or can we skip it as long as the package is not actually tested? is there a way for me to check that somewhere? -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100086)

1 0

[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

[JIRA] (OVIRT-1554) Get rid of old 'create_rpms' jobs
by Barak Korren (oVirt JIRA) 03 Jun '18

03 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1554?page=com.atlassian.jira.… ] Barak Korren edited comment on OVIRT-1554 at 6/3/18 3:32 PM: ------------------------------------------------------------- Having create_rpms jobs means we have to keep maintaining the JJB templates for then, its in out interest to have them removed. We've been hit many times in the past with the situation were a code improvement in STDCI was found to be breaking the create_rpm jobs. Bottom-line reopening the ticket. Hopefully we can close it once everything migrates to STDCI V2. was (Author: bkorren(a)redhat.com) Having create_rpms jobs means we have to keep maintaining the JJB templates for then, its in out interest to have them removed. We've been hit many times in the past with the situation were a code improvement in STDCI was found to be breaking the create_rpm jobs. > Get rid of old 'create_rpms' jobs > --------------------------------- > > Key: OVIRT-1554 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1554 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt CI > Reporter: Barak Korren > Assignee: infra > Labels: re-factor, standard-ci > > '*create_rpms*' jobs are the old kind of jobs that we used to have before STD-CI. We still have many of those laying around. > Here is the list for the time of writing these lines: > # vdsm_any_create-rpms_manual > # mom_any_create-rpms_manual_old > # qemu_4.1_create-rpms-el7-x86_64_merged > # qemu_4.1_create-rpms-el7-ppc64le_merged > # qemu_4.1_create-rpms-el7-x86_64_created > # qemu_4.1_create-rpms-el7-ppc64le_created > # qemu_master_create-rpms-el7-x86_64_created > # slf4j_master_create-rpms-el6-x86_64_merged > # qemu_master_create-rpms-el7-ppc64le_created > # slf4j_master_create-rpms-el6-x86_64_created > # ioprocess_0.15_create-rpms-el7-x86_64_merged > # ovirt-wgt_4.1_create-rpms-fc24-x86_64_merged > # ioprocess_0.15_create-rpms-el7-x86_64_created > # ovirt-wgt_4.1_create-rpms-fc24-x86_64_created > # ovirt-reports_3.6_create-rpms-el6-x86_64_merged > # ovirt-reports_3.6_create-rpms-el7-x86_64_merged > # ovirt-wgt_master_create-rpms-fc25-x86_64_merged > # py2exe-py2.7_4.1_create-rpms-fc24-x86_64_merged > # pywin32-py2.7_4.1_create-rpms-el7-x86_64_merged > # vcredist-x86_4.1_create-rpms-fc24-x86_64_merged > # ovirt-reports_3.6_create-rpms-el6-x86_64_created > # ovirt-reports_3.6_create-rpms-el7-x86_64_created > # ovirt-wgt_master_create-rpms-fc25-x86_64_created > # py2exe-py2.7_4.1_create-rpms-fc24-x86_64_created > # python-windows_4.1_create-rpms-el7-x86_64_merged > # pywin32-py2.7_4.1_create-rpms-el7-x86_64_created > # pywin32-py2.7_4.1_create-rpms-fc24-x86_64_merged > # vcredist-x86_4.1_create-rpms-fc24-x86_64_created > # ovirt-hosted-engine-ha_any_create-rpms_manual_old > # ovirt-vmconsole_3.6_create-rpms-el6-x86_64_merged > # ovirt-vmconsole_3.6_create-rpms-el7-x86_64_merged > # python-windows_4.1_create-rpms-el7-x86_64_created > # python-windows_4.1_create-rpms-fc24-x86_64_merged > # pywin32-py2.7_4.1_create-rpms-fc24-x86_64_created > # ovirt-vmconsole_3.6_create-rpms-el6-x86_64_created > # ovirt-vmconsole_3.6_create-rpms-el7-x86_64_created > # py2exe-py2.7_master_create-rpms-fc25-x86_64_merged > # python-windows_4.1_create-rpms-fc24-x86_64_created > # pywin32-py2.7_master_create-rpms-el7-x86_64_merged > # vcredist-x86_master_create-rpms-fc25-x86_64_merged > # vcredist-x86_master_create-rpms-fc26-x86_64_merged > # ovirt-host-deploy_3.6_create-rpms-el6-x86_64_merged > # ovirt-host-deploy_3.6_create-rpms-el7-x86_64_merged > # py2exe-py2.7_master_create-rpms-fc25-x86_64_created > # python-windows_master_create-rpms-el7-x86_64_merged > # pywin32-py2.7_master_create-rpms-el7-x86_64_created > # pywin32-py2.7_master_create-rpms-fc25-x86_64_merged > # pywin32-py2.7_master_create-rpms-fc26-x86_64_merged > # vcredist-x86_master_create-rpms-fc25-x86_64_created > # vcredist-x86_master_create-rpms-fc26-x86_64_created > # ovirt-host-deploy_3.6_create-rpms-el6-x86_64_created > # ovirt-host-deploy_3.6_create-rpms-el7-x86_64_created > # python-windows_master_create-rpms-el7-x86_64_created > # python-windows_master_create-rpms-fc25-x86_64_merged > # python-windows_master_create-rpms-fc26-x86_64_merged > # pywin32-py2.7_master_create-rpms-fc25-x86_64_created > # pywin32-py2.7_master_create-rpms-fc26-x86_64_created > # ovirt-log-collector_3.6_create-rpms-el6-x86_64_merged > # ovirt-log-collector_3.6_create-rpms-el7-x86_64_merged > # python-windows_master_create-rpms-fc25-x86_64_created > # python-windows_master_create-rpms-fc26-x86_64_created > # ovirt-log-collector_3.6_create-rpms-el6-x86_64_created > # ovirt-log-collector_3.6_create-rpms-el7-x86_64_created > # ovirt-engine-sdk-java_3.6_create-rpms-el6-x86_64_merged > # ovirt-engine-sdk-java_3.6_create-rpms-el7-x86_64_merged > # ovirt-engine-sdk-java_3.6_create-rpms-fc24-x86_64_merged > # ovirt-engine-wildfly10_4.1_create-rpms-el7-x86_64_merged > # ovirt-hosted-engine-ha_3.6_create-rpms-el7-x86_64_merged > # jasperreports-server_master_create-rpms-el6-x86_64_merged > # jasperreports-server_master_create-rpms-el7-x86_64_merged > # ovirt-engine-wildfly10_4.1_create-rpms-el7-x86_64_created > # ovirt-engine-wildfly10_4.1_create-rpms-fc24-x86_64_merged > # ovirt-hosted-engine-ha_3.6_create-rpms-el7-x86_64_created > # jasperreports-server_master_create-rpms-el6-x86_64_created > # jasperreports-server_master_create-rpms-el7-x86_64_created > # ovirt-engine-wildfly10_4.1_create-rpms-fc24-x86_64_created > # ovirt-engine-wildfly10_master_create-rpms-el7-x86_64_merged > # ovirt-engine-wildfly10_master_create-rpms-el7-x86_64_created > # ovirt-engine-wildfly10_master_create-rpms-fc25-x86_64_merged > # ovirt-engine-wildfly10_master_create-rpms-fc26-x86_64_merged > # nsis-simple-service-plugin_4.1_create-rpms-fc24-x86_64_merged > # ovirt-engine-wildfly10_master_create-rpms-fc25-x86_64_created > # ovirt-engine-wildfly10_master_create-rpms-fc26-x86_64_created > # nsis-simple-service-plugin_4.1_create-rpms-fc24-x86_64_created > # tmp_ovirt-hosted-engine-ha_master_create-rpms-el7-x86_64_tagged > # nsis-simple-service-plugin_master_create-rpms-fc25-x86_64_merged > # ovirt-engine-wildfly-overlay10_4.1_create-rpms-el6-x86_64_merged > # ovirt-engine-wildfly-overlay10_4.1_create-rpms-el7-x86_64_merged > # nsis-simple-service-plugin_master_create-rpms-fc25-x86_64_created > # ovirt-engine-wildfly-overlay10_4.1_create-rpms-el6-x86_64_created > # ovirt-engine-wildfly-overlay10_4.1_create-rpms-el7-x86_64_created > # ovirt-engine-wildfly-overlay10_4.1_create-rpms-fc24-x86_64_merged > # ovirt-engine-wildfly-overlay10_4.1_create-rpms-fc24-x86_64_created > # ovirt-engine-wildfly-overlay10_master_create-rpms-el6-x86_64_merged > # ovirt-engine-wildfly-overlay10_master_create-rpms-el7-x86_64_merged > # ovirt-engine-wildfly-overlay10_master_create-rpms-el6-x86_64_created > # ovirt-engine-wildfly-overlay10_master_create-rpms-el7-x86_64_created > # ovirt-engine-wildfly-overlay10_master_create-rpms-fc25-x86_64_merged > # ovirt-engine-wildfly-overlay10_master_create-rpms-fc25-x86_64_created -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100086)

1 0

[JIRA] (OVIRT-1554) Get rid of old 'create_rpms' jobs
by Barak Korren (oVirt JIRA) 03 Jun '18

03 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1554?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1554: ------------------------------------- Having create_rpms jobs means we have to keep maintaining the JJB templates for then, its in out interest to have them removed. We've been hit many times in the past with the situation were a code improvement in STDCI was found to be breaking the create_rpm jobs. > Get rid of old 'create_rpms' jobs > --------------------------------- > > Key: OVIRT-1554 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1554 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt CI > Reporter: Barak Korren > Assignee: infra > Labels: re-factor, standard-ci > > '*create_rpms*' jobs are the old kind of jobs that we used to have before STD-CI. We still have many of those laying around. > Here is the list for the time of writing these lines: > # vdsm_any_create-rpms_manual > # mom_any_create-rpms_manual_old > # qemu_4.1_create-rpms-el7-x86_64_merged > # qemu_4.1_create-rpms-el7-ppc64le_merged > # qemu_4.1_create-rpms-el7-x86_64_created > # qemu_4.1_create-rpms-el7-ppc64le_created > # qemu_master_create-rpms-el7-x86_64_created > # slf4j_master_create-rpms-el6-x86_64_merged > # qemu_master_create-rpms-el7-ppc64le_created > # slf4j_master_create-rpms-el6-x86_64_created > # ioprocess_0.15_create-rpms-el7-x86_64_merged > # ovirt-wgt_4.1_create-rpms-fc24-x86_64_merged > # ioprocess_0.15_create-rpms-el7-x86_64_created > # ovirt-wgt_4.1_create-rpms-fc24-x86_64_created > # ovirt-reports_3.6_create-rpms-el6-x86_64_merged > # ovirt-reports_3.6_create-rpms-el7-x86_64_merged > # ovirt-wgt_master_create-rpms-fc25-x86_64_merged > # py2exe-py2.7_4.1_create-rpms-fc24-x86_64_merged > # pywin32-py2.7_4.1_create-rpms-el7-x86_64_merged > # vcredist-x86_4.1_create-rpms-fc24-x86_64_merged > # ovirt-reports_3.6_create-rpms-el6-x86_64_created > # ovirt-reports_3.6_create-rpms-el7-x86_64_created > # ovirt-wgt_master_create-rpms-fc25-x86_64_created > # py2exe-py2.7_4.1_create-rpms-fc24-x86_64_created > # python-windows_4.1_create-rpms-el7-x86_64_merged > # pywin32-py2.7_4.1_create-rpms-el7-x86_64_created > # pywin32-py2.7_4.1_create-rpms-fc24-x86_64_merged > # vcredist-x86_4.1_create-rpms-fc24-x86_64_created > # ovirt-hosted-engine-ha_any_create-rpms_manual_old > # ovirt-vmconsole_3.6_create-rpms-el6-x86_64_merged > # ovirt-vmconsole_3.6_create-rpms-el7-x86_64_merged > # python-windows_4.1_create-rpms-el7-x86_64_created > # python-windows_4.1_create-rpms-fc24-x86_64_merged > # pywin32-py2.7_4.1_create-rpms-fc24-x86_64_created > # ovirt-vmconsole_3.6_create-rpms-el6-x86_64_created > # ovirt-vmconsole_3.6_create-rpms-el7-x86_64_created > # py2exe-py2.7_master_create-rpms-fc25-x86_64_merged > # python-windows_4.1_create-rpms-fc24-x86_64_created > # pywin32-py2.7_master_create-rpms-el7-x86_64_merged > # vcredist-x86_master_create-rpms-fc25-x86_64_merged > # vcredist-x86_master_create-rpms-fc26-x86_64_merged > # ovirt-host-deploy_3.6_create-rpms-el6-x86_64_merged > # ovirt-host-deploy_3.6_create-rpms-el7-x86_64_merged > # py2exe-py2.7_master_create-rpms-fc25-x86_64_created > # python-windows_master_create-rpms-el7-x86_64_merged > # pywin32-py2.7_master_create-rpms-el7-x86_64_created > # pywin32-py2.7_master_create-rpms-fc25-x86_64_merged > # pywin32-py2.7_master_create-rpms-fc26-x86_64_merged > # vcredist-x86_master_create-rpms-fc25-x86_64_created > # vcredist-x86_master_create-rpms-fc26-x86_64_created > # ovirt-host-deploy_3.6_create-rpms-el6-x86_64_created > # ovirt-host-deploy_3.6_create-rpms-el7-x86_64_created > # python-windows_master_create-rpms-el7-x86_64_created > # python-windows_master_create-rpms-fc25-x86_64_merged > # python-windows_master_create-rpms-fc26-x86_64_merged > # pywin32-py2.7_master_create-rpms-fc25-x86_64_created > # pywin32-py2.7_master_create-rpms-fc26-x86_64_created > # ovirt-log-collector_3.6_create-rpms-el6-x86_64_merged > # ovirt-log-collector_3.6_create-rpms-el7-x86_64_merged > # python-windows_master_create-rpms-fc25-x86_64_created > # python-windows_master_create-rpms-fc26-x86_64_created > # ovirt-log-collector_3.6_create-rpms-el6-x86_64_created > # ovirt-log-collector_3.6_create-rpms-el7-x86_64_created > # ovirt-engine-sdk-java_3.6_create-rpms-el6-x86_64_merged > # ovirt-engine-sdk-java_3.6_create-rpms-el7-x86_64_merged > # ovirt-engine-sdk-java_3.6_create-rpms-fc24-x86_64_merged > # ovirt-engine-wildfly10_4.1_create-rpms-el7-x86_64_merged > # ovirt-hosted-engine-ha_3.6_create-rpms-el7-x86_64_merged > # jasperreports-server_master_create-rpms-el6-x86_64_merged > # jasperreports-server_master_create-rpms-el7-x86_64_merged > # ovirt-engine-wildfly10_4.1_create-rpms-el7-x86_64_created > # ovirt-engine-wildfly10_4.1_create-rpms-fc24-x86_64_merged > # ovirt-hosted-engine-ha_3.6_create-rpms-el7-x86_64_created > # jasperreports-server_master_create-rpms-el6-x86_64_created > # jasperreports-server_master_create-rpms-el7-x86_64_created > # ovirt-engine-wildfly10_4.1_create-rpms-fc24-x86_64_created > # ovirt-engine-wildfly10_master_create-rpms-el7-x86_64_merged > # ovirt-engine-wildfly10_master_create-rpms-el7-x86_64_created > # ovirt-engine-wildfly10_master_create-rpms-fc25-x86_64_merged > # ovirt-engine-wildfly10_master_create-rpms-fc26-x86_64_merged > # nsis-simple-service-plugin_4.1_create-rpms-fc24-x86_64_merged > # ovirt-engine-wildfly10_master_create-rpms-fc25-x86_64_created > # ovirt-engine-wildfly10_master_create-rpms-fc26-x86_64_created > # nsis-simple-service-plugin_4.1_create-rpms-fc24-x86_64_created > # tmp_ovirt-hosted-engine-ha_master_create-rpms-el7-x86_64_tagged > # nsis-simple-service-plugin_master_create-rpms-fc25-x86_64_merged > # ovirt-engine-wildfly-overlay10_4.1_create-rpms-el6-x86_64_merged > # ovirt-engine-wildfly-overlay10_4.1_create-rpms-el7-x86_64_merged > # nsis-simple-service-plugin_master_create-rpms-fc25-x86_64_created > # ovirt-engine-wildfly-overlay10_4.1_create-rpms-el6-x86_64_created > # ovirt-engine-wildfly-overlay10_4.1_create-rpms-el7-x86_64_created > # ovirt-engine-wildfly-overlay10_4.1_create-rpms-fc24-x86_64_merged > # ovirt-engine-wildfly-overlay10_4.1_create-rpms-fc24-x86_64_created > # ovirt-engine-wildfly-overlay10_master_create-rpms-el6-x86_64_merged > # ovirt-engine-wildfly-overlay10_master_create-rpms-el7-x86_64_merged > # ovirt-engine-wildfly-overlay10_master_create-rpms-el6-x86_64_created > # ovirt-engine-wildfly-overlay10_master_create-rpms-el7-x86_64_created > # ovirt-engine-wildfly-overlay10_master_create-rpms-fc25-x86_64_merged > # ovirt-engine-wildfly-overlay10_master_create-rpms-fc25-x86_64_created -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100086)

1 0

[JIRA] (OVIRT-1554) Get rid of old 'create_rpms' jobs
by Barak Korren (oVirt JIRA) 03 Jun '18

03 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1554?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1554: -------------------------------- Status: To Do (was: In Progress) > Get rid of old 'create_rpms' jobs > --------------------------------- > > Key: OVIRT-1554 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1554 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt CI > Reporter: Barak Korren > Assignee: infra > Labels: re-factor, standard-ci > > '*create_rpms*' jobs are the old kind of jobs that we used to have before STD-CI. We still have many of those laying around. > Here is the list for the time of writing these lines: > # vdsm_any_create-rpms_manual > # mom_any_create-rpms_manual_old > # qemu_4.1_create-rpms-el7-x86_64_merged > # qemu_4.1_create-rpms-el7-ppc64le_merged > # qemu_4.1_create-rpms-el7-x86_64_created > # qemu_4.1_create-rpms-el7-ppc64le_created > # qemu_master_create-rpms-el7-x86_64_created > # slf4j_master_create-rpms-el6-x86_64_merged > # qemu_master_create-rpms-el7-ppc64le_created > # slf4j_master_create-rpms-el6-x86_64_created > # ioprocess_0.15_create-rpms-el7-x86_64_merged > # ovirt-wgt_4.1_create-rpms-fc24-x86_64_merged > # ioprocess_0.15_create-rpms-el7-x86_64_created > # ovirt-wgt_4.1_create-rpms-fc24-x86_64_created > # ovirt-reports_3.6_create-rpms-el6-x86_64_merged > # ovirt-reports_3.6_create-rpms-el7-x86_64_merged > # ovirt-wgt_master_create-rpms-fc25-x86_64_merged > # py2exe-py2.7_4.1_create-rpms-fc24-x86_64_merged > # pywin32-py2.7_4.1_create-rpms-el7-x86_64_merged > # vcredist-x86_4.1_create-rpms-fc24-x86_64_merged > # ovirt-reports_3.6_create-rpms-el6-x86_64_created > # ovirt-reports_3.6_create-rpms-el7-x86_64_created > # ovirt-wgt_master_create-rpms-fc25-x86_64_created > # py2exe-py2.7_4.1_create-rpms-fc24-x86_64_created > # python-windows_4.1_create-rpms-el7-x86_64_merged > # pywin32-py2.7_4.1_create-rpms-el7-x86_64_created > # pywin32-py2.7_4.1_create-rpms-fc24-x86_64_merged > # vcredist-x86_4.1_create-rpms-fc24-x86_64_created > # ovirt-hosted-engine-ha_any_create-rpms_manual_old > # ovirt-vmconsole_3.6_create-rpms-el6-x86_64_merged > # ovirt-vmconsole_3.6_create-rpms-el7-x86_64_merged > # python-windows_4.1_create-rpms-el7-x86_64_created > # python-windows_4.1_create-rpms-fc24-x86_64_merged > # pywin32-py2.7_4.1_create-rpms-fc24-x86_64_created > # ovirt-vmconsole_3.6_create-rpms-el6-x86_64_created > # ovirt-vmconsole_3.6_create-rpms-el7-x86_64_created > # py2exe-py2.7_master_create-rpms-fc25-x86_64_merged > # python-windows_4.1_create-rpms-fc24-x86_64_created > # pywin32-py2.7_master_create-rpms-el7-x86_64_merged > # vcredist-x86_master_create-rpms-fc25-x86_64_merged > # vcredist-x86_master_create-rpms-fc26-x86_64_merged > # ovirt-host-deploy_3.6_create-rpms-el6-x86_64_merged > # ovirt-host-deploy_3.6_create-rpms-el7-x86_64_merged > # py2exe-py2.7_master_create-rpms-fc25-x86_64_created > # python-windows_master_create-rpms-el7-x86_64_merged > # pywin32-py2.7_master_create-rpms-el7-x86_64_created > # pywin32-py2.7_master_create-rpms-fc25-x86_64_merged > # pywin32-py2.7_master_create-rpms-fc26-x86_64_merged > # vcredist-x86_master_create-rpms-fc25-x86_64_created > # vcredist-x86_master_create-rpms-fc26-x86_64_created > # ovirt-host-deploy_3.6_create-rpms-el6-x86_64_created > # ovirt-host-deploy_3.6_create-rpms-el7-x86_64_created > # python-windows_master_create-rpms-el7-x86_64_created > # python-windows_master_create-rpms-fc25-x86_64_merged > # python-windows_master_create-rpms-fc26-x86_64_merged > # pywin32-py2.7_master_create-rpms-fc25-x86_64_created > # pywin32-py2.7_master_create-rpms-fc26-x86_64_created > # ovirt-log-collector_3.6_create-rpms-el6-x86_64_merged > # ovirt-log-collector_3.6_create-rpms-el7-x86_64_merged > # python-windows_master_create-rpms-fc25-x86_64_created > # python-windows_master_create-rpms-fc26-x86_64_created > # ovirt-log-collector_3.6_create-rpms-el6-x86_64_created > # ovirt-log-collector_3.6_create-rpms-el7-x86_64_created > # ovirt-engine-sdk-java_3.6_create-rpms-el6-x86_64_merged > # ovirt-engine-sdk-java_3.6_create-rpms-el7-x86_64_merged > # ovirt-engine-sdk-java_3.6_create-rpms-fc24-x86_64_merged > # ovirt-engine-wildfly10_4.1_create-rpms-el7-x86_64_merged > # ovirt-hosted-engine-ha_3.6_create-rpms-el7-x86_64_merged > # jasperreports-server_master_create-rpms-el6-x86_64_merged > # jasperreports-server_master_create-rpms-el7-x86_64_merged > # ovirt-engine-wildfly10_4.1_create-rpms-el7-x86_64_created > # ovirt-engine-wildfly10_4.1_create-rpms-fc24-x86_64_merged > # ovirt-hosted-engine-ha_3.6_create-rpms-el7-x86_64_created > # jasperreports-server_master_create-rpms-el6-x86_64_created > # jasperreports-server_master_create-rpms-el7-x86_64_created > # ovirt-engine-wildfly10_4.1_create-rpms-fc24-x86_64_created > # ovirt-engine-wildfly10_master_create-rpms-el7-x86_64_merged > # ovirt-engine-wildfly10_master_create-rpms-el7-x86_64_created > # ovirt-engine-wildfly10_master_create-rpms-fc25-x86_64_merged > # ovirt-engine-wildfly10_master_create-rpms-fc26-x86_64_merged > # nsis-simple-service-plugin_4.1_create-rpms-fc24-x86_64_merged > # ovirt-engine-wildfly10_master_create-rpms-fc25-x86_64_created > # ovirt-engine-wildfly10_master_create-rpms-fc26-x86_64_created > # nsis-simple-service-plugin_4.1_create-rpms-fc24-x86_64_created > # tmp_ovirt-hosted-engine-ha_master_create-rpms-el7-x86_64_tagged > # nsis-simple-service-plugin_master_create-rpms-fc25-x86_64_merged > # ovirt-engine-wildfly-overlay10_4.1_create-rpms-el6-x86_64_merged > # ovirt-engine-wildfly-overlay10_4.1_create-rpms-el7-x86_64_merged > # nsis-simple-service-plugin_master_create-rpms-fc25-x86_64_created > # ovirt-engine-wildfly-overlay10_4.1_create-rpms-el6-x86_64_created > # ovirt-engine-wildfly-overlay10_4.1_create-rpms-el7-x86_64_created > # ovirt-engine-wildfly-overlay10_4.1_create-rpms-fc24-x86_64_merged > # ovirt-engine-wildfly-overlay10_4.1_create-rpms-fc24-x86_64_created > # ovirt-engine-wildfly-overlay10_master_create-rpms-el6-x86_64_merged > # ovirt-engine-wildfly-overlay10_master_create-rpms-el7-x86_64_merged > # ovirt-engine-wildfly-overlay10_master_create-rpms-el6-x86_64_created > # ovirt-engine-wildfly-overlay10_master_create-rpms-el7-x86_64_created > # ovirt-engine-wildfly-overlay10_master_create-rpms-fc25-x86_64_merged > # ovirt-engine-wildfly-overlay10_master_create-rpms-fc25-x86_64_created -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100086)

1 0

[JIRA] (OVIRT-1554) Get rid of old 'create_rpms' jobs
by Barak Korren (oVirt JIRA) 03 Jun '18

03 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1554?page=com.atlassian.jira.… ] Barak Korren reopened OVIRT-1554: --------------------------------- > Get rid of old 'create_rpms' jobs > --------------------------------- > > Key: OVIRT-1554 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1554 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt CI > Reporter: Barak Korren > Assignee: infra > Labels: re-factor, standard-ci > > '*create_rpms*' jobs are the old kind of jobs that we used to have before STD-CI. We still have many of those laying around. > Here is the list for the time of writing these lines: > # vdsm_any_create-rpms_manual > # mom_any_create-rpms_manual_old > # qemu_4.1_create-rpms-el7-x86_64_merged > # qemu_4.1_create-rpms-el7-ppc64le_merged > # qemu_4.1_create-rpms-el7-x86_64_created > # qemu_4.1_create-rpms-el7-ppc64le_created > # qemu_master_create-rpms-el7-x86_64_created > # slf4j_master_create-rpms-el6-x86_64_merged > # qemu_master_create-rpms-el7-ppc64le_created > # slf4j_master_create-rpms-el6-x86_64_created > # ioprocess_0.15_create-rpms-el7-x86_64_merged > # ovirt-wgt_4.1_create-rpms-fc24-x86_64_merged > # ioprocess_0.15_create-rpms-el7-x86_64_created > # ovirt-wgt_4.1_create-rpms-fc24-x86_64_created > # ovirt-reports_3.6_create-rpms-el6-x86_64_merged > # ovirt-reports_3.6_create-rpms-el7-x86_64_merged > # ovirt-wgt_master_create-rpms-fc25-x86_64_merged > # py2exe-py2.7_4.1_create-rpms-fc24-x86_64_merged > # pywin32-py2.7_4.1_create-rpms-el7-x86_64_merged > # vcredist-x86_4.1_create-rpms-fc24-x86_64_merged > # ovirt-reports_3.6_create-rpms-el6-x86_64_created > # ovirt-reports_3.6_create-rpms-el7-x86_64_created > # ovirt-wgt_master_create-rpms-fc25-x86_64_created > # py2exe-py2.7_4.1_create-rpms-fc24-x86_64_created > # python-windows_4.1_create-rpms-el7-x86_64_merged > # pywin32-py2.7_4.1_create-rpms-el7-x86_64_created > # pywin32-py2.7_4.1_create-rpms-fc24-x86_64_merged > # vcredist-x86_4.1_create-rpms-fc24-x86_64_created > # ovirt-hosted-engine-ha_any_create-rpms_manual_old > # ovirt-vmconsole_3.6_create-rpms-el6-x86_64_merged > # ovirt-vmconsole_3.6_create-rpms-el7-x86_64_merged > # python-windows_4.1_create-rpms-el7-x86_64_created > # python-windows_4.1_create-rpms-fc24-x86_64_merged > # pywin32-py2.7_4.1_create-rpms-fc24-x86_64_created > # ovirt-vmconsole_3.6_create-rpms-el6-x86_64_created > # ovirt-vmconsole_3.6_create-rpms-el7-x86_64_created > # py2exe-py2.7_master_create-rpms-fc25-x86_64_merged > # python-windows_4.1_create-rpms-fc24-x86_64_created > # pywin32-py2.7_master_create-rpms-el7-x86_64_merged > # vcredist-x86_master_create-rpms-fc25-x86_64_merged > # vcredist-x86_master_create-rpms-fc26-x86_64_merged > # ovirt-host-deploy_3.6_create-rpms-el6-x86_64_merged > # ovirt-host-deploy_3.6_create-rpms-el7-x86_64_merged > # py2exe-py2.7_master_create-rpms-fc25-x86_64_created > # python-windows_master_create-rpms-el7-x86_64_merged > # pywin32-py2.7_master_create-rpms-el7-x86_64_created > # pywin32-py2.7_master_create-rpms-fc25-x86_64_merged > # pywin32-py2.7_master_create-rpms-fc26-x86_64_merged > # vcredist-x86_master_create-rpms-fc25-x86_64_created > # vcredist-x86_master_create-rpms-fc26-x86_64_created > # ovirt-host-deploy_3.6_create-rpms-el6-x86_64_created > # ovirt-host-deploy_3.6_create-rpms-el7-x86_64_created > # python-windows_master_create-rpms-el7-x86_64_created > # python-windows_master_create-rpms-fc25-x86_64_merged > # python-windows_master_create-rpms-fc26-x86_64_merged > # pywin32-py2.7_master_create-rpms-fc25-x86_64_created > # pywin32-py2.7_master_create-rpms-fc26-x86_64_created > # ovirt-log-collector_3.6_create-rpms-el6-x86_64_merged > # ovirt-log-collector_3.6_create-rpms-el7-x86_64_merged > # python-windows_master_create-rpms-fc25-x86_64_created > # python-windows_master_create-rpms-fc26-x86_64_created > # ovirt-log-collector_3.6_create-rpms-el6-x86_64_created > # ovirt-log-collector_3.6_create-rpms-el7-x86_64_created > # ovirt-engine-sdk-java_3.6_create-rpms-el6-x86_64_merged > # ovirt-engine-sdk-java_3.6_create-rpms-el7-x86_64_merged > # ovirt-engine-sdk-java_3.6_create-rpms-fc24-x86_64_merged > # ovirt-engine-wildfly10_4.1_create-rpms-el7-x86_64_merged > # ovirt-hosted-engine-ha_3.6_create-rpms-el7-x86_64_merged > # jasperreports-server_master_create-rpms-el6-x86_64_merged > # jasperreports-server_master_create-rpms-el7-x86_64_merged > # ovirt-engine-wildfly10_4.1_create-rpms-el7-x86_64_created > # ovirt-engine-wildfly10_4.1_create-rpms-fc24-x86_64_merged > # ovirt-hosted-engine-ha_3.6_create-rpms-el7-x86_64_created > # jasperreports-server_master_create-rpms-el6-x86_64_created > # jasperreports-server_master_create-rpms-el7-x86_64_created > # ovirt-engine-wildfly10_4.1_create-rpms-fc24-x86_64_created > # ovirt-engine-wildfly10_master_create-rpms-el7-x86_64_merged > # ovirt-engine-wildfly10_master_create-rpms-el7-x86_64_created > # ovirt-engine-wildfly10_master_create-rpms-fc25-x86_64_merged > # ovirt-engine-wildfly10_master_create-rpms-fc26-x86_64_merged > # nsis-simple-service-plugin_4.1_create-rpms-fc24-x86_64_merged > # ovirt-engine-wildfly10_master_create-rpms-fc25-x86_64_created > # ovirt-engine-wildfly10_master_create-rpms-fc26-x86_64_created > # nsis-simple-service-plugin_4.1_create-rpms-fc24-x86_64_created > # tmp_ovirt-hosted-engine-ha_master_create-rpms-el7-x86_64_tagged > # nsis-simple-service-plugin_master_create-rpms-fc25-x86_64_merged > # ovirt-engine-wildfly-overlay10_4.1_create-rpms-el6-x86_64_merged > # ovirt-engine-wildfly-overlay10_4.1_create-rpms-el7-x86_64_merged > # nsis-simple-service-plugin_master_create-rpms-fc25-x86_64_created > # ovirt-engine-wildfly-overlay10_4.1_create-rpms-el6-x86_64_created > # ovirt-engine-wildfly-overlay10_4.1_create-rpms-el7-x86_64_created > # ovirt-engine-wildfly-overlay10_4.1_create-rpms-fc24-x86_64_merged > # ovirt-engine-wildfly-overlay10_4.1_create-rpms-fc24-x86_64_created > # ovirt-engine-wildfly-overlay10_master_create-rpms-el6-x86_64_merged > # ovirt-engine-wildfly-overlay10_master_create-rpms-el7-x86_64_merged > # ovirt-engine-wildfly-overlay10_master_create-rpms-el6-x86_64_created > # ovirt-engine-wildfly-overlay10_master_create-rpms-el7-x86_64_created > # ovirt-engine-wildfly-overlay10_master_create-rpms-fc25-x86_64_merged > # ovirt-engine-wildfly-overlay10_master_create-rpms-fc25-x86_64_created -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100086)

1 0

[JIRA] (OVIRT-1811) tested rpms piling up
by Barak Korren (oVirt JIRA) 03 Jun '18

03 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1811?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1811: -------------------------------- Resolution: Duplicate Status: Done (was: To Do) Issue is being address in work on OVIRT-1277 > tested rpms piling up > --------------------- > > Key: OVIRT-1811 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1811 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Repositories Mgmt > Reporter: sbonazzo > Assignee: infra > > /var/www/html/repos/ovirt/tested/master is now 351G > This causes > http://jenkins.ovirt.org/view/Publishers/job/ovirt_master_publish-rpms_nigh… > to run for one hour downloading obsolete code. > Do we have something cleaning up tested repos? > If not, can we get one? > -- > SANDRO BONAZZOLA > ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D > Red Hat EMEA <https://www.redhat.com/> > <https://red.ht/sig> > TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100086)

1 0

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

03 Jun '18

A system test invoked by the "ovirt-4.2" change queue including change 91886,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/91886/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/2279/

2 1

[CQ]: d00d8ca (stage-gh-stdci2) failed "dummy-master" system tests
by oVirt Jenkins 03 Jun '18

03 Jun '18

Change d00d8ca (stage-gh-stdci2) is probably the reason behind recent system test failures in the "dummy-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://github.com/oVirt/stage-gh-stdci2/commit/d00d8cac105f7be15d2a0559522… For failed test results see: https://jenkins-staging.ovirt.org/job/dummy-master_change-queue-tester/149/

1 0

[CQ]: d00d8ca (stage-gh-stdci2) failed "dummy-master" system tests
by oVirt Jenkins 03 Jun '18

03 Jun '18

Change d00d8ca (stage-gh-stdci2) is probably the reason behind recent system test failures in the "dummy-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://github.com/oVirt/stage-gh-stdci2/commit/d00d8cac105f7be15d2a0559522… For failed test results see: https://jenkins-staging.ovirt.org/job/dummy-master_change-queue-tester/147/

1 0

[JIRA] (OVIRT-1993) Looking for a new task to help with
by sailesh baskar (oVirt JIRA) 03 Jun '18

03 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1993?page=com.atlassian.jira.… ] sailesh baskar commented on OVIRT-1993: --------------------------------------- Couldn't find any results for first time task.. can you help me?? > 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

[JIRA] (OVIRT-1295) Add job to auto-rebase patches that are ready to be merged
by eyal edri (oVirt JIRA) 03 Jun '18

03 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1295?page=com.atlassian.jira.… ] eyal edri updated OVIRT-1295: ----------------------------- Resolution: Won't Do Status: Done (was: To Do) > Add job to auto-rebase patches that are ready to be merged > ----------------------------------------------------------- > > Key: OVIRT-1295 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1295 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: eyal edri > Assignee: infra > Priority: Low > > We want to help stable branch maintainers to minimize the time needed for merging approved changes ( i.e CR +2 and VERIFY +1 ) and also to reduce the chance of merge conflicts. > A suggestion was made to create a job which will detect patches ready to be merged with the flags CR +2 and V +1 set and will auto rebase them, so when a maintainer is ready to submit a patch, hopefully the patch won't need a rebase and can be merged without further waiting for rebase or CI. > This approach might introduce challenges when working on patches that are dependent on other patches and a specific logic might be required to handle special cases. > [~tnisan(a)redhat.com][~ykaul][~dfediuck] I hope this conveys the need and requirement, please comment or add thoughts if I missed anything. > Initially we'll try enabling it for ovirt-engine on 4.1 branch. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100086)

1 0

[JIRA] (OVIRT-1295) Add job to auto-rebase patches that are ready to be merged
by Tal Nisan (oVirt JIRA) 03 Jun '18

03 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1295?page=com.atlassian.jira.… ] Tal Nisan commented on OVIRT-1295: ---------------------------------- How can I elaborate on the need? I never asked for it nor though it's needed :) Most of the time a rebase is not needed at all and we're good the way it is, you can close the ticket. > Add job to auto-rebase patches that are ready to be merged > ----------------------------------------------------------- > > Key: OVIRT-1295 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1295 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: eyal edri > Assignee: infra > Priority: Low > > We want to help stable branch maintainers to minimize the time needed for merging approved changes ( i.e CR +2 and VERIFY +1 ) and also to reduce the chance of merge conflicts. > A suggestion was made to create a job which will detect patches ready to be merged with the flags CR +2 and V +1 set and will auto rebase them, so when a maintainer is ready to submit a patch, hopefully the patch won't need a rebase and can be merged without further waiting for rebase or CI. > This approach might introduce challenges when working on patches that are dependent on other patches and a specific logic might be required to handle special cases. > [~tnisan(a)redhat.com][~ykaul][~dfediuck] I hope this conveys the need and requirement, please comment or add thoughts if I missed anything. > Initially we'll try enabling it for ovirt-engine on 4.1 branch. -- 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 eyal edri (oVirt JIRA) 03 Jun '18

03 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1549?page=com.atlassian.jira.… ] eyal edri commented on OVIRT-1549: ---------------------------------- [~danken(a)redhat.com] is this still needed? how often were we broken from this pkg or needed to consume it early so it will worth the time and resource invesment? > 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-1767) Look into replacing gitweb for oVirt Gerrit
by eyal edri (oVirt JIRA) 03 Jun '18

03 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1767?page=com.atlassian.jira.… ] eyal edri updated OVIRT-1767: ----------------------------- Priority: Low (was: Medium) > Look into replacing gitweb for oVirt Gerrit > ------------------------------------------- > > Key: OVIRT-1767 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1767 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Gerrit/git > Reporter: Barak Korren > Assignee: infra > Priority: Low > Labels: gerrit > > One of the faults of our Gerrit system is that the source browser look like it belongs to a different century. > There seems to be a Gerrit plugin which allows using Gitiles rather then gitweb in Gerrit: > https://gerrit-review.googlesource.com/Documentation/config-plugins.html#gi… > Gitiles itself seems to be a more modern Git UI then gitweb, at the very least is supports showing markdown files, which is a staple of modern source browsers: > https://gerrit.googlesource.com/gitiles/ > Another plugin to consider is the one for using GitBlit: > https://gerrit-review.googlesource.com/Documentation/config-plugins.html#gi… > Gitblit is another Java based Gir bowser: > http://gitblit.com/features.html -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100086)

1 0

[JIRA] (OVIRT-1811) tested rpms piling up
by eyal edri (oVirt JIRA) 03 Jun '18

03 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1811?page=com.atlassian.jira.… ] eyal edri commented on OVIRT-1811: ---------------------------------- [~bkorren(a)redhat.com] [~eyonasi(a)redhat.com] I guess this can linked to the retention ticket and closed as duplicate? > tested rpms piling up > --------------------- > > Key: OVIRT-1811 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1811 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Repositories Mgmt > Reporter: sbonazzo > Assignee: infra > > /var/www/html/repos/ovirt/tested/master is now 351G > This causes > http://jenkins.ovirt.org/view/Publishers/job/ovirt_master_publish-rpms_nigh… > to run for one hour downloading obsolete code. > Do we have something cleaning up tested repos? > If not, can we get one? > -- > SANDRO BONAZZOLA > ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D > Red Hat EMEA <https://www.redhat.com/> > <https://red.ht/sig> > TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100086)

1 0

[JIRA] (OVIRT-1647) standard-enqueue was stuck while trying to fetch from Gerrit, timeout didn't work
by eyal edri (oVirt JIRA) 03 Jun '18

03 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1647?page=com.atlassian.jira.… ] eyal edri updated OVIRT-1647: ----------------------------- Resolution: Cannot Reproduce Status: Done (was: To Do) > standard-enqueue was stuck while trying to fetch from Gerrit, timeout didn't work > --------------------------------------------------------------------------------- > > Key: OVIRT-1647 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1647 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: oVirt CI > Reporter: Daniel Belenky > Assignee: infra > > `standard-enqueue` Job was stuck for 22 hours while trying to fetch repository from Gerrit. > For some reason, the timeout didn't work. I'm opening the ticket to track to issue. > Link to Job run: [http://jenkins.ovirt.org/job/standard-enqueue/4720/|standard-enqueue/4720] [Marked to keep forever] > Console output: (I've aborted the Job) > {code:java} > Triggered by Gerrit: https://gerrit.ovirt.org/81650 > [Pipeline] timestamps > [Pipeline] { > [Pipeline] ansiColor > [Pipeline] { > [Pipeline] node > 13:56:56 Running on vm0090.workers-phx.ovirt.org in /home/jenkins/workspace/standard-enqueue > [Pipeline] { > [Pipeline] stage > [Pipeline] { (loading code) > [Pipeline] dir > 13:56:56 Running in /home/jenkins/workspace/standard-enqueue/jenkins > [Pipeline] { > [Pipeline] checkout > 13:57:01 Cloning the remote Git repository > 13:57:01 Cloning repository https://gerrit.ovirt.org/jenkins > 13:57:01 > git init /home/jenkins/workspace/standard-enqueue/jenkins # timeout=10 > 13:57:01 Fetching upstream changes from https://gerrit.ovirt.org/jenkins > 13:57:01 > git --version # timeout=10 > 14:07:01 ERROR: Timeout after 10 minutes > Aborted by Daniel > {code} -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100086)

1 0

[JIRA] (OVIRT-1615) Replace Artifactory with Nexus
by eyal edri (oVirt JIRA) 03 Jun '18

03 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1615?page=com.atlassian.jira.… ] eyal edri commented on OVIRT-1615: ---------------------------------- I don't see this as an immediate need to solve any issue we're facing, let's make sure we don't invest in it if not needed fro a specific task/value. > Replace Artifactory with Nexus > ------------------------------ > > Key: OVIRT-1615 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1615 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: General > Reporter: Barak Korren > Assignee: infra > Priority: Lowest > > Nexus is the main competitor to Artifactory. It has similar features. Lokking at documentation available about it, it looks like the open source version of it supports a much bigger feature set the Artifactory without requiring an upgrade to a payed version: > https://help.sonatype.com/display/NXRM3/Repository+Manager+Feature+Matrix > Of interest to us are the PyPi (Python) support, the NPM (Javascript) and the Docker support. > It seems that Nexus is available as a container, so we may try deploying it on OpenShift. > I think we need to plan and execute a migration to Nexus. > This ticket should server as a tracking ticket for the entire work. We will create blocker tickets to track needed steps. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100086)

1 0

[JIRA] (OVIRT-1615) Replace Artifactory with Nexus
by eyal edri (oVirt JIRA) 03 Jun '18

03 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1615?page=com.atlassian.jira.… ] eyal edri updated OVIRT-1615: ----------------------------- Priority: Lowest (was: Medium) > Replace Artifactory with Nexus > ------------------------------ > > Key: OVIRT-1615 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1615 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: General > Reporter: Barak Korren > Assignee: infra > Priority: Lowest > > Nexus is the main competitor to Artifactory. It has similar features. Lokking at documentation available about it, it looks like the open source version of it supports a much bigger feature set the Artifactory without requiring an upgrade to a payed version: > https://help.sonatype.com/display/NXRM3/Repository+Manager+Feature+Matrix > Of interest to us are the PyPi (Python) support, the NPM (Javascript) and the Docker support. > It seems that Nexus is available as a container, so we may try deploying it on OpenShift. > I think we need to plan and execute a migration to Nexus. > This ticket should server as a tracking ticket for the entire work. We will create blocker tickets to track needed steps. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100086)

1 0

[JIRA] (OVIRT-1591) follow up on ovirt-web-ui package location once github is supported
by eyal edri (oVirt JIRA) 03 Jun '18

03 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1591?page=com.atlassian.jira.… ] eyal edri updated OVIRT-1591: ----------------------------- Resolution: Won't Fix Status: Done (was: To Do) Maintainer isn't interested currently in moving, once there will be a need, adding ovirt-web-ui to STD-CI will be very easy. > follow up on ovirt-web-ui package location once github is supported > ------------------------------------------------------------------- > > Key: OVIRT-1591 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1591 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > > Currently we have no official location for the ovirt-web-ui package. > Barak is working on giving better support for github. > This ticket is to make sure that we remember to follow up on the ovirt-web-ui package once Barak's ticket is resolved and we have a proper solution for the ovirt-web-ui project. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100086)

1 0

[JIRA] (OVIRT-1575) Setup a development environment
by eyal edri (oVirt JIRA) 03 Jun '18

03 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1575?page=com.atlassian.jira.… ] eyal edri updated OVIRT-1575: ----------------------------- Resolution: Won't Do Status: Done (was: To Do) > Setup a development environment > ------------------------------- > > Key: OVIRT-1575 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1575 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: eyal edri > Assignee: infra > > https://github.com/kubevirt/kubevirt/blob/master/docs/getting-started.md -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100086)

1 0

[JIRA] (OVIRT-1554) Get rid of old 'create_rpms' jobs
by eyal edri (oVirt JIRA) 03 Jun '18

03 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1554?page=com.atlassian.jira.… ] eyal edri updated OVIRT-1554: ----------------------------- Resolution: Won't Do Status: Done (was: To Do) I don't see a huge benefit in pro-actively removing the old jobs, Any project which wants/needs to migrate to STD CI (v2 preferably) can open a ticket and we'll help, so gradually old jobs will be removed from CI. > Get rid of old 'create_rpms' jobs > --------------------------------- > > Key: OVIRT-1554 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1554 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt CI > Reporter: Barak Korren > Assignee: infra > Labels: re-factor, standard-ci > > '*create_rpms*' jobs are the old kind of jobs that we used to have before STD-CI. We still have many of those laying around. > Here is the list for the time of writing these lines: > # vdsm_any_create-rpms_manual > # mom_any_create-rpms_manual_old > # qemu_4.1_create-rpms-el7-x86_64_merged > # qemu_4.1_create-rpms-el7-ppc64le_merged > # qemu_4.1_create-rpms-el7-x86_64_created > # qemu_4.1_create-rpms-el7-ppc64le_created > # qemu_master_create-rpms-el7-x86_64_created > # slf4j_master_create-rpms-el6-x86_64_merged > # qemu_master_create-rpms-el7-ppc64le_created > # slf4j_master_create-rpms-el6-x86_64_created > # ioprocess_0.15_create-rpms-el7-x86_64_merged > # ovirt-wgt_4.1_create-rpms-fc24-x86_64_merged > # ioprocess_0.15_create-rpms-el7-x86_64_created > # ovirt-wgt_4.1_create-rpms-fc24-x86_64_created > # ovirt-reports_3.6_create-rpms-el6-x86_64_merged > # ovirt-reports_3.6_create-rpms-el7-x86_64_merged > # ovirt-wgt_master_create-rpms-fc25-x86_64_merged > # py2exe-py2.7_4.1_create-rpms-fc24-x86_64_merged > # pywin32-py2.7_4.1_create-rpms-el7-x86_64_merged > # vcredist-x86_4.1_create-rpms-fc24-x86_64_merged > # ovirt-reports_3.6_create-rpms-el6-x86_64_created > # ovirt-reports_3.6_create-rpms-el7-x86_64_created > # ovirt-wgt_master_create-rpms-fc25-x86_64_created > # py2exe-py2.7_4.1_create-rpms-fc24-x86_64_created > # python-windows_4.1_create-rpms-el7-x86_64_merged > # pywin32-py2.7_4.1_create-rpms-el7-x86_64_created > # pywin32-py2.7_4.1_create-rpms-fc24-x86_64_merged > # vcredist-x86_4.1_create-rpms-fc24-x86_64_created > # ovirt-hosted-engine-ha_any_create-rpms_manual_old > # ovirt-vmconsole_3.6_create-rpms-el6-x86_64_merged > # ovirt-vmconsole_3.6_create-rpms-el7-x86_64_merged > # python-windows_4.1_create-rpms-el7-x86_64_created > # python-windows_4.1_create-rpms-fc24-x86_64_merged > # pywin32-py2.7_4.1_create-rpms-fc24-x86_64_created > # ovirt-vmconsole_3.6_create-rpms-el6-x86_64_created > # ovirt-vmconsole_3.6_create-rpms-el7-x86_64_created > # py2exe-py2.7_master_create-rpms-fc25-x86_64_merged > # python-windows_4.1_create-rpms-fc24-x86_64_created > # pywin32-py2.7_master_create-rpms-el7-x86_64_merged > # vcredist-x86_master_create-rpms-fc25-x86_64_merged > # vcredist-x86_master_create-rpms-fc26-x86_64_merged > # ovirt-host-deploy_3.6_create-rpms-el6-x86_64_merged > # ovirt-host-deploy_3.6_create-rpms-el7-x86_64_merged > # py2exe-py2.7_master_create-rpms-fc25-x86_64_created > # python-windows_master_create-rpms-el7-x86_64_merged > # pywin32-py2.7_master_create-rpms-el7-x86_64_created > # pywin32-py2.7_master_create-rpms-fc25-x86_64_merged > # pywin32-py2.7_master_create-rpms-fc26-x86_64_merged > # vcredist-x86_master_create-rpms-fc25-x86_64_created > # vcredist-x86_master_create-rpms-fc26-x86_64_created > # ovirt-host-deploy_3.6_create-rpms-el6-x86_64_created > # ovirt-host-deploy_3.6_create-rpms-el7-x86_64_created > # python-windows_master_create-rpms-el7-x86_64_created > # python-windows_master_create-rpms-fc25-x86_64_merged > # python-windows_master_create-rpms-fc26-x86_64_merged > # pywin32-py2.7_master_create-rpms-fc25-x86_64_created > # pywin32-py2.7_master_create-rpms-fc26-x86_64_created > # ovirt-log-collector_3.6_create-rpms-el6-x86_64_merged > # ovirt-log-collector_3.6_create-rpms-el7-x86_64_merged > # python-windows_master_create-rpms-fc25-x86_64_created > # python-windows_master_create-rpms-fc26-x86_64_created > # ovirt-log-collector_3.6_create-rpms-el6-x86_64_created > # ovirt-log-collector_3.6_create-rpms-el7-x86_64_created > # ovirt-engine-sdk-java_3.6_create-rpms-el6-x86_64_merged > # ovirt-engine-sdk-java_3.6_create-rpms-el7-x86_64_merged > # ovirt-engine-sdk-java_3.6_create-rpms-fc24-x86_64_merged > # ovirt-engine-wildfly10_4.1_create-rpms-el7-x86_64_merged > # ovirt-hosted-engine-ha_3.6_create-rpms-el7-x86_64_merged > # jasperreports-server_master_create-rpms-el6-x86_64_merged > # jasperreports-server_master_create-rpms-el7-x86_64_merged > # ovirt-engine-wildfly10_4.1_create-rpms-el7-x86_64_created > # ovirt-engine-wildfly10_4.1_create-rpms-fc24-x86_64_merged > # ovirt-hosted-engine-ha_3.6_create-rpms-el7-x86_64_created > # jasperreports-server_master_create-rpms-el6-x86_64_created > # jasperreports-server_master_create-rpms-el7-x86_64_created > # ovirt-engine-wildfly10_4.1_create-rpms-fc24-x86_64_created > # ovirt-engine-wildfly10_master_create-rpms-el7-x86_64_merged > # ovirt-engine-wildfly10_master_create-rpms-el7-x86_64_created > # ovirt-engine-wildfly10_master_create-rpms-fc25-x86_64_merged > # ovirt-engine-wildfly10_master_create-rpms-fc26-x86_64_merged > # nsis-simple-service-plugin_4.1_create-rpms-fc24-x86_64_merged > # ovirt-engine-wildfly10_master_create-rpms-fc25-x86_64_created > # ovirt-engine-wildfly10_master_create-rpms-fc26-x86_64_created > # nsis-simple-service-plugin_4.1_create-rpms-fc24-x86_64_created > # tmp_ovirt-hosted-engine-ha_master_create-rpms-el7-x86_64_tagged > # nsis-simple-service-plugin_master_create-rpms-fc25-x86_64_merged > # ovirt-engine-wildfly-overlay10_4.1_create-rpms-el6-x86_64_merged > # ovirt-engine-wildfly-overlay10_4.1_create-rpms-el7-x86_64_merged > # nsis-simple-service-plugin_master_create-rpms-fc25-x86_64_created > # ovirt-engine-wildfly-overlay10_4.1_create-rpms-el6-x86_64_created > # ovirt-engine-wildfly-overlay10_4.1_create-rpms-el7-x86_64_created > # ovirt-engine-wildfly-overlay10_4.1_create-rpms-fc24-x86_64_merged > # ovirt-engine-wildfly-overlay10_4.1_create-rpms-fc24-x86_64_created > # ovirt-engine-wildfly-overlay10_master_create-rpms-el6-x86_64_merged > # ovirt-engine-wildfly-overlay10_master_create-rpms-el7-x86_64_merged > # ovirt-engine-wildfly-overlay10_master_create-rpms-el6-x86_64_created > # ovirt-engine-wildfly-overlay10_master_create-rpms-el7-x86_64_created > # ovirt-engine-wildfly-overlay10_master_create-rpms-fc25-x86_64_merged > # ovirt-engine-wildfly-overlay10_master_create-rpms-fc25-x86_64_created -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100086)

1 0

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

03 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-983?page=com.atlassian.jira.p… ] eyal edri commented on OVIRT-983: --------------------------------- [~bkorren(a)redhat.com] did we made progress on this during last year with V2 and BO? > 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

[CQ]: d00d8ca (stage-gh-stdci2) failed "dummy-master" system tests
by oVirt Jenkins 03 Jun '18

03 Jun '18

Change d00d8ca (stage-gh-stdci2) is probably the reason behind recent system test failures in the "dummy-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://github.com/oVirt/stage-gh-stdci2/commit/d00d8cac105f7be15d2a0559522… For failed test results see: https://jenkins-staging.ovirt.org/job/dummy-master_change-queue-tester/141/

1 0

[JIRA] (OVIRT-562) find a way not to fail CI jobs if git clone fails
by eyal edri (oVirt JIRA) 03 Jun '18

03 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-562?page=com.atlassian.jira.p… ] eyal edri updated OVIRT-562: ---------------------------- Resolution: Won't Do Status: Done (was: To Do) > find a way not to fail CI jobs if git clone fails > ------------------------------------------------- > > Key: OVIRT-562 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-562 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: eyal edri > Assignee: infra > Priority: Low > > We need to find away to tell gerrit trigger plugin not to put -1 if git clone fails (obviously an infra issue) -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100086)

1 0

[JIRA] (OVIRT-1113) Automate project Gerrit repo creation
by eyal edri (oVirt JIRA) 03 Jun '18

03 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1113?page=com.atlassian.jira.… ] eyal edri updated OVIRT-1113: ----------------------------- Priority: Low (was: Medium) > Automate project Gerrit repo creation > ------------------------------------- > > Key: OVIRT-1113 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1113 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Gerrit/git > Reporter: Barak Korren > Assignee: infra > Priority: Low > Labels: first_time_task > > Because the doc is annoying to follow manually, and its easy to automate Gerrit, the API is basically 'ssh'. > Long term if the automation is good we could make this "self service". -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100086)

1 0

[JIRA] (OVIRT-895) mailing list memberships reminder - do we need that?
by eyal edri (oVirt JIRA) 03 Jun '18

03 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-895?page=com.atlassian.jira.p… ] eyal edri updated OVIRT-895: ---------------------------- Resolution: Fixed Status: Done (was: To Do) Not sure this is an issue anymore, anyone can go to thier settings on the UI and update their preference. > mailing list memberships reminder - do we need that? > ---------------------------------------------------- > > Key: OVIRT-895 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-895 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Evgheni Dereveanchin > Assignee: infra > Priority: Low > > I'm subscribed to a bunch of lists and every month I get membership reminder emails. Do we have them for a reason? If not - I'd like to disable them (can be done per-list in the settings or globally across the Mailman instance) -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100086)

1 0

[JIRA] (OVIRT-1385) Support installing latest version of specific pkgs
by eyal edri (oVirt JIRA) 03 Jun '18

03 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1385?page=com.atlassian.jira.… ] eyal edri updated OVIRT-1385: ----------------------------- Resolution: Won't Do Status: Done (was: To Do) [~vojtech] as [~bkorren(a)redhat.com] mock_runner is in stabilization mode and we're not planning any new features there, if this is something that is still needed, we can check if its possible to support via V2 of future work planned for the CI > Support installing latest version of specific pkgs > -------------------------------------------------- > > Key: OVIRT-1385 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1385 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt CI > Reporter: Vojtech Szocs > Assignee: infra > Priority: Low > Labels: mock_runner.sh > > There are multiple oVirt projects (see below) which contain a {{build.packages.force}} (or similar) file, along with the following code in their build script: > {code} > # The "build.packages.force" file contains BuildRequires packages > # to be installed using their latest version. > # Force CI to get the latest version of these packages: > dependencies="$(sed -e '/^[ \t]*$/d' -e '/^#/d' automation/build.packages.force)" > yum-deprecated clean metadata || yum clean metadata > yum-deprecated -y install ${dependencies} || yum -y install ${dependencies} > {code} > Used in projects: ovirt-engine-dashboard, ovirt-engine-nodejs-modules, ovirt-web-ui > Is it possible for CI to support this out of the box, using {{.force}} file convention? (basically a suffix to standard {{.packages}} files) > I've looked at OVIRT-921 and IIUC the yum cache is cleaned every 2 days, so an alternative to above proposal would be to have this interval configurable per-project. > Not sure what's the best approach here, please advise. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100086)

1 0

[JIRA] (OVIRT-1399) Install Jenkins TAP results plugin
by eyal edri (oVirt JIRA) 03 Jun '18

03 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1399?page=com.atlassian.jira.… ] eyal edri updated OVIRT-1399: ----------------------------- Resolution: Won't Do Status: Done (was: To Do) > Install Jenkins TAP results plugin > ---------------------------------- > > Key: OVIRT-1399 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1399 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Reporter: Nadav Goldin > Assignee: infra > Priority: Low > > Please install the TAP Plugin - https://wiki.jenkins-ci.org/display/JENKINS/TAP+Plugin > It allows to display TAP test results, which we use in Lago(with bats). > Not urgent, can be done whenever time allows(with some other upgrade etc). -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100086)

1 0

[JIRA] (OVIRT-1500) CI on ovirt-engine patch succeeded, but didn't mark CI=+1 on gerrit
by eyal edri (oVirt JIRA) 03 Jun '18

03 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1500?page=com.atlassian.jira.… ] eyal edri updated OVIRT-1500: ----------------------------- Resolution: Fixed Status: Done (was: To Do) > CI on ovirt-engine patch succeeded, but didn't mark CI=+1 on gerrit > ------------------------------------------------------------------- > > Key: OVIRT-1500 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1500 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Gerrit/git, oVirt CI > Reporter: Allon Mureinik > Assignee: infra > Priority: Low > > In my recent engine patch https://gerrit.ovirt.org/#/c/78911 the CI passed, but was not marked as so in gerrit. > Looking through gerrit's history, here's what I *think* is going on: > 08:41 - patchset #1 is submitted > 08:41 - CI (check-patch) starts for both EL7 and fc25 > _At this point I noticed a typo in the commit method. I fixed it and posted patchset #2_ > 08:42 - patchset #2 is submitted > _CI was never triggered for patchset #2. Is this because the only difference between it and patchset #1 is the commit message?_ > 09:15 - CI for patchset #1 completes, and marks *patchset #1* with CI=+1. This is not inherited to patchset #2 for some reason. > Expected behavior: > If CI for patchset #1 passed and the only difference is the commit message (not the parent commit and not the content), I'd expect the CI score to be inherited. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100086)

1 0

[JIRA] (OVIRT-1295) Add job to auto-rebase patches that are ready to be merged
by eyal edri (oVirt JIRA) 03 Jun '18

03 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1295?page=com.atlassian.jira.… ] eyal edri commented on OVIRT-1295: ---------------------------------- [~tnisan(a)redhat.com] is this still needed? I didn't see any issues during 4.2 development which required an additional flow other than existing change queue. If so, can you elaborate more on the need, maybe as a user story so we'll understand the problem at hand. > Add job to auto-rebase patches that are ready to be merged > ----------------------------------------------------------- > > Key: OVIRT-1295 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1295 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: eyal edri > Assignee: infra > Priority: Low > > We want to help stable branch maintainers to minimize the time needed for merging approved changes ( i.e CR +2 and VERIFY +1 ) and also to reduce the chance of merge conflicts. > A suggestion was made to create a job which will detect patches ready to be merged with the flags CR +2 and V +1 set and will auto rebase them, so when a maintainer is ready to submit a patch, hopefully the patch won't need a rebase and can be merged without further waiting for rebase or CI. > This approach might introduce challenges when working on patches that are dependent on other patches and a specific logic might be required to handle special cases. > [~tnisan(a)redhat.com][~ykaul][~dfediuck] I hope this conveys the need and requirement, please comment or add thoughts if I missed anything. > Initially we'll try enabling it for ovirt-engine on 4.1 branch. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100086)

1 0

[JIRA] (OVIRT-1971) oVirt Bugzilla automation: Bugs didn't move to ON_QA [Bug 1542087]
by eyal edri (oVirt JIRA) 03 Jun '18

03 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1971?page=com.atlassian.jira.… ] eyal edri commented on OVIRT-1971: ---------------------------------- [~amarchuk] ping > oVirt Bugzilla automation: Bugs didn't move to ON_QA [Bug 1542087] > ------------------------------------------------------------------ > > Key: OVIRT-1971 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1971 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: eyal edri > Assignee: Anton Marchukov > Labels: bugzilla, > > Sending to infra-support to track this as a ticket. > On Fri, Apr 13, 2018 at 3:35 PM, Anton Marchukov <amarchuk(a)redhat.com> > wrote: > > Hello Greg. > > > > Thanks. > > > > Anton. > > > > > > On 13 April 2018 at 14:27:26, Greg Sheremeta (gshereme(a)redhat.com) wrote: > > > Thanks. I moved the rest (we had 3) > > > > > > On Fri, Apr 13, 2018 at 8:24 AM, Anton Marchukov > > > wrote: > > > > > > > Hello Greg. > > > > > > > > You are right and the patch is included in the tag. Sounds like there > > > > are some problems with detecting earlier changes. I moved to ON_QA > > > > manually while we check this. > > > > > > > > Anton. > > > > > > > > > > > > On 13 April 2018 at 14:16:30, Greg Sheremeta (gshereme(a)redhat.com) > > wrote: > > > > > > https://bugzilla.redhat.com/show_bug.cgi?id=1542087 > > > > > > > > > > > > > > > > -- > > > > > > GREG SHEREMETA > > > > > > SENIOR SOFTWARE ENGINEER - TEAM LEAD - RHV UX > > > > > > Red Hat NA > > > > > > > > > > > > gshereme(a)redhat.com IRC: gshereme > > > > > > > > _______________________________________________ > > Infra mailing list > > Infra(a)ovirt.org > > http://lists.ovirt.org/mailman/listinfo/infra > > > -- > Eyal edri > MANAGER > RHV DevOps > EMEA VIRTUALIZATION R&D > Red Hat EMEA <https://www.redhat.com/> > <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> > phone: +972-9-7692018 > irc: eedri (on #tlv #rhev-dev #rhev-integ) -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100086)

1 0

[JIRA] (OVIRT-1973) vdsm_master_check-patch-fc27 fail due to yum repo issues
by eyal edri (oVirt JIRA) 03 Jun '18

03 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1973?page=com.atlassian.jira.… ] eyal edri commented on OVIRT-1973: ---------------------------------- CentOS 7.5 is out, are you still experiencing any issues? > vdsm_master_check-patch-fc27 fail due to yum repo issues > -------------------------------------------------------- > > Key: OVIRT-1973 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1973 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Components: CI client projects > Reporter: danken > Assignee: infra > > Once in a while, jobs are failing due to > [MIRROR] kmod-kvdo-6.1.1.24-1.fc27.x86_64.rpm: Downloading successful, > but checksum doesn't match. Calculated: > 54996f8e7877b533bf43825853cd3c7cfd0f7df5cb6a1876e50c9ade7829dd73(sha256) > Expected: 7a8294588764bd2c14adaa7d24218cce344930c1ce62a24b17208d1cd629c461(sha256) > for example > http://jenkins.ovirt.org/job/vdsm_master_check-patch-fc27-x86_64/2830/conso… -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100086)

1 0

[CQ]: d00d8ca (stage-gh-stdci2) failed "dummy-master" system tests
by oVirt Jenkins 03 Jun '18

03 Jun '18

Change d00d8ca (stage-gh-stdci2) is probably the reason behind recent system test failures in the "dummy-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://github.com/oVirt/stage-gh-stdci2/commit/d00d8cac105f7be15d2a0559522… For failed test results see: https://jenkins-staging.ovirt.org/job/dummy-master_change-queue-tester/138/

1 0

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

03 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1993?page=com.atlassian.jira.… ] eyal edri commented on OVIRT-1993: ---------------------------------- Hi, were you able to choose any task to work on? > 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

[JIRA] (OVIRT-2017) Add fc28 slave to jenkins
by eyal edri (oVirt JIRA) 03 Jun '18

03 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2017?page=com.atlassian.jira.… ] eyal edri reassigned OVIRT-2017: -------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > Add fc28 slave to jenkins > ------------------------- > > Key: OVIRT-2017 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2017 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Lago > Reporter: Gal Ben Haim > Assignee: Evgheni Dereveanchin > > fc28 slave is required for lago's check-patch. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100086)

1 0

[CQ]: d00d8ca (stage-gh-stdci2) failed "dummy-master" system tests
by oVirt Jenkins 03 Jun '18

03 Jun '18

Change d00d8ca (stage-gh-stdci2) is probably the reason behind recent system test failures in the "dummy-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://github.com/oVirt/stage-gh-stdci2/commit/d00d8cac105f7be15d2a0559522… For failed test results see: https://jenkins-staging.ovirt.org/job/dummy-master_change-queue-tester/132/

2 1

[CQ]: 91195,19 (ovirt-engine) failed "ovirt-master" system tests
by oVirt Jenkins 03 Jun '18

03 Jun '18

Change 91195,19 (ovirt-engine) 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/91195/19 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/8019/

1 0