You can do it in your Zuul layout.yaml configuration file
Ex:
- name: Nova-ML2-Sriov
branch: ^(master|stable/ocata|stable/newton|stable/pike).*$
voting: false
skip-if:
From: Ivan Kolodyazhny [mailto:e...@e0ne.info]
Sent: Monday, September 18, 2017 1:05 PM
To: OpenStack Development Ma
Hi,
What domain name are you using?
Check for 'Traceback' and ' ERROR ' in the logs, maybe you will get a hint
2017-01-25 11:00:21.215 28309 INFO nova.compute.manager
[req-6f21e4a4-28a8-48e3-bf2f-2e1ad3b52470 0329776bd1634978a7fed35a70c77479
7531f209e3514e3f98eb58aafa480285 - - -] [instance:
+1
From: Gary Kotton [mailto:gkot...@vmware.com]
Sent: Thursday, January 12, 2017 9:05 AM
To: OpenStack List
Subject: [openstack-dev] [Infra] Gerrit performance time
Hi,
It takes forever to access gerrit. Anyone else hitting this issue?
Thanks
Gary
___
Hi Devs,
We are bringing up new CI using latest CI Solution[1]
And we are facing some issues[2] with connection nodepool[3] to devstack
provider[4]
Due to keystone authentication error[5], looks like some missing info in the
nodepool.yaml
Please advise.
p.s. provider was done by bringing up mas
Hi Wanjing,
We had some similar issues in our CI, especially after we are running one of
the stable branches.
The current workaround we’d found is removing all pip packs after devstack
./clean.sh
Thanks
Lenny.
-Original Message-
From: Wanjing Xu (waxu) [mailto:w...@cisco.com]
Sent: Wed
Hello Apoorva,
According to the log you have issue with remote git cloning,
We are facing similar issues from time to time and as a workaround started to
use local git mirror instead of rerunning such jobs.
2016-12-05 01:19:17.356 | + functions-common:git_timed:598 :
timeout -s SIGIN
uestions) d...@lists.openstack.org>
> Subject: Re: [openstack-dev] [openstack][neutron] DHCP agent: advertise SLAAC
> prefixes Exceptions
>
>
> > On 24 Nov 2016, at 15:31, Jens Rosenboom wrote:
> >
> > 2016-11-24 15:08 GMT+01:00 Lenny Verkhovsky :
> >>
vember 24, 2016 4:32 PM
> To: OpenStack Development Mailing List (not for usage questions) d...@lists.openstack.org>
> Subject: Re: [openstack-dev] [openstack][neutron] DHCP agent: advertise SLAAC
> prefixes Exceptions
>
> 2016-11-24 15:08 GMT+01:00 Lenny Verkhovsky :
> > Hi
eutron] DHCP agent: advertise SLAAC
> prefixes Exceptions
>
>
> > On 24 Nov 2016, at 15:08, Lenny Verkhovsky wrote:
> >
> > Hi,
> > The DHCP Agent commit[1] added a lot of exceptions into Mellanox CI
> >
> >
> > [1] https://review.openstack.org/#/c/393007
Hi,
The DHCP Agent commit[1] added a lot of exceptions into Mellanox CI
[1] https://review.openstack.org/#/c/393007/
[2]
http://13.69.151.247/41/346041/24/check-cinder/Cinder-ISER-ISCSI/ec78a29/logs/q-dhcp.log.gz
[3] 2016-11-23 06:37:49.950 28150 DEBUG neutron.agent.linux.utils
[req-ec66fd16-
] Nova-MultiJob CI (non-voting) request
> to comment
>
> On 11/4/2016 2:04 AM, Lenny Verkhovsky wrote:
> > It uses 2 physical servers with 2 compute nodes And runs migration
> > tests only.
> > Other Mellanox CI jobs run on a single allinone server, thus migration test
2016 1:45 AM
> To: openstack-dev@lists.openstack.org
> Subject: Re: [openstack-dev] [nova] Nova-MultiJob CI (non-voting) request
> to comment
>
> On 11/3/2016 3:45 AM, Lenny Verkhovsky wrote:
> > Hi,
> >
> > We would like Mellanox[1] MultiNode CI job to start com
Hi,
We would like Mellanox[1] MultiNode CI job to start commenting as 'non voting'
job on partial nova[2] and tempest[3] code.
This Job runs few migration tests[4] and an example of its run can be seen
here[5].
[1] https://wiki.openstack.org/wiki/ThirdPartySystems/Mellanox_CI
[2] nova/pci
[3] t
Hi Joseph,
You can try deleting line[1] in
tempest/tempest/scenario/test_network_basic_ops.py
And rerunning the test [2]
[1]
https://github.com/openstack/tempest/blob/b6508962595dc1dcf351ec5a7316401786625fea/tempest/scenario/test_network_basic_ops.py#L416
[2] testr run
tempest.scenario.test_ne
: Lenny Verkhovsky ; OpenStack Development Mailing List
(not for usage questions)
Subject: Re: [openstack-dev] SRIOV-port refused to bind
Hi Lenny Verkhovsky,
Thank you for your response.
I am using the Mitaka version of openstack. I followed the
https://wiki.openstack.org/wiki/SR-IOV
HI,
Did you configured everything according to
https://wiki.openstack.org/wiki/SR-IOV-Passthrough-For-Networking?
( including intel_iommu=on ) ?
Can you attach more logs and config files of the nova/neutron/neutron plugins
Are you working with devstack or distro?
From: Murali B [mailto:mbi...@gm
Hi,
Currently in some cases[1] CI sets a comment on the patch set as NOT_REGISTERED.
Those comments are very hard to monitor for CI operators and have noisy value
for the developers.
Maybe a better solution is not commenting in such cases at all as discussed in
[2].
If a developer is missing
Thanks,
We are investigating the failure.
From: Andrea Frittoli [mailto:andrea.fritt...@gmail.com]
Sent: Thursday, June 16, 2016 2:02 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [tempest][SR-IOV] tempest breaks Mellanox CI
On Thu, Jun 16, 20
Hi all,
We are about to merge Mellanox Cinder CI setup[1] with Mellanox CI[2].
Please note that Mellanox CI[2] will use one account[3] for all its OpenStack
CI activity[4]
FYI.
Lenny Verkhovsky ( lennyb )
[1] https://wiki.openstack.org/wiki/ThirdPartySystems/Mellanox_Cinder_CI
[2] https
As approved in [1] we've added Nova-Macvtap job as part of Mellanox Nova
non-voting CI
Our wiki page is [2]
[1]
http://eavesdrop.openstack.org/irclogs/%23openstack-nova/%23openstack-nova.2016-03-30.log.html
[2] https://wiki.openstack.org/wiki/ThirdPartySystems/Mellanox_CI
Best Regards
Lenny
Also our Mellanox CI failed See log[1]
Looks like missing function
/opt/stack/tempest/.tox/venv/local/lib/python2.7/site-packages/tempest_lib/__init__.py:28:
DeprecationWarning: tempest-lib is deprecated for future bug-fixes and code
changes in favor of tempest. Please change your imports from t
Nikola,
I guess Mellanox CI ( running, failing , non-voting ) can assist on this issue.
Since we found it and opened a bug.
-Original Message-
From: Nikola Đipanov [mailto:ndipa...@redhat.com]
Sent: Wednesday, January 20, 2016 4:41 PM
To: OpenStack Development Mailing List
Subject: [ope
Hi,
After Upgrading to 2.11 seems that
lastcomment (
https://github.com/openstack/third-party-ci-tools/tree/master/monitoring/lastcomment-scoreboard
)
monitoring tool stopped working
I've posted a small patch https://review.openstack.org/#/c/259083/ to fix the
issue,
But I wander if there is
Hi all,
Mellanox Nova CI[1] is asking for 'voting' permissions on Nova project.
We are running as 'non voting' CI more than 6 month already[2]
And feel quite confident about its stability.
[1] https://wiki.openstack.org/wiki/ThirdPartySystems/Mellanox_CI
[2] http://144.76.193.39:8080/job/Nova-ML2-
] Mellanox CI request to comment
On Mon, Aug 10, 2015 at 10:56:00AM +, Lenny Verkhovsky wrote:
> Hi all,
> Lately we discovered a bug[1] in tempest after the code was merged.
> To minimize such things in the future we are asking permission for our
> CI to comment as non-voting CI to tem
Hi,
Had you tried removing oslo_db package?
I saw a similar issues and usually uninstalling or upgrading packages solved
the problem
L.
-Original Message-
From: Mike Bayer [mailto:mba...@redhat.com]
Sent: Saturday, August 08, 2015 1:43 AM
To: OpenStack Development Mailing List (not for
page can be viewed here[3]
[1] https://review.openstack.org/#/c/209553/1
[2] http://144.76.193.39/ci-artifacts/Nova-ML2-Sriov_1864
[3] https://wiki.openstack.org/wiki/ThirdPartySystems/Mellanox_CI
Thanks.
Lenny Verkhovsky
Can you check dmesg –T to see at least if the messages are not too old?
Are you using port2 as a connection to VM?
Lenny Verkhovsky
From: Eduard Matei [mailto:eduard.ma...@cloudfounders.com]
Sent: Wednesday, June 10, 2015 10:34 AM
To: OpenStack Development Mailing List (not for usage questions
Hi Dan,
I disabled Mellanox Nova CI from commenting and will check this issue first
thing tomorrow morning.
Thanks and my deepest apologies.
Lenny Verkhovsky
-Original Message-
From: Dan Smith [mailto:d...@danplanet.com]
Sent: Monday, June 01, 2015 7:41 PM
To: OpenStack Development
Thanks Matt,
We will start Nova non-voting commenting.
Lenny Verkhovsky
SW Engineer, Mellanox Technologies
www.mellanox.com
Office:+972 74 712 9244
Mobile: +972 54 554 0233
Fax:+972 72 257 9400
-Original Message-
From: Matt Riedemann [mailto:mrie...@linux.vnet.ibm.com
tempest.scenario.test_network_advanced_server_ops.TestNetworkAdvancedServerOps
With configured port_vnic_type = direct
We will add more tests in the future.
Thanks in advance.
Lenny Verkhovsky
SW Engineer, Mellanox Technologies
www.mellanox.com
Office:+972 74 712 9244
Mobile: +972 54 554 0233
Hi,
We had some issues with tox lately,
The fix was removing ~/.pip and some other packages from this folder that were
used as cache for pip
And reinstalling devstack.
Lenny Verkhovsky
From: Shane McGough [mailto:smcgo...@kemptechnologies.com]
Sent: Wednesday, April 22, 2015 1:30 PM
To
Hi Ramy,
Will there be any discussions of this issue on the Vancouver Summit?
Lenny Verkhovsky
SW Engineer, Mellanox Technologies
From: Nikolay Fedotov (nfedotov) [mailto:nfedo...@cisco.com]
Sent: Tuesday, April 21, 2015 8:10 PM
To: OpenStack Development Mailing List (not for usage questions
Sean, Matt,
Is there anything missing for us to start 'non-voting' Nova CI ?
Thanks.
Lenny Verkhovsky
SW Engineer, Mellanox Technologies
www.mellanox.com
Office:+972 74 712 9244
Mobile: +972 54 554 0233
Fax:+972 72 257 9400
-Original Message-
From: Mic
-driver_20150401_1102/testr_results.html.gz
We are currently running tempest api tests on Mellanox HW using SRiOV
configuration,
We are working to add tempest scenario tests with port direct configuration for
SRiOV
We are also planning to extend tests with our in-house tests developments.
Lenny
Thanks, done,
I thought it need’s community approval.
Have a great day…
Lenny Verkhovsky
SW Engineer, Mellanox Technologies
www.mellanox.com<http://www.mellanox.com>
Office:+972 74 712 9244
Mobile: +972 54 554 0233
Fax:+972 72 257 9400
From: Deepak Shetty [mailto:
Hi All,
Please add Mellanox Cinder CI to this page
https://wiki.openstack.org/wiki/Cinder/third-party-ci-status
Driver name: iSER-LIO, iSER-ISCSI
Contact: Lenny Verkhovsky cinder...@mellanox.com
Status: voting and reporting
Issues: none
Reference https://wiki.openstack.org/wiki/ThirdPartySystems
37 matches
Mail list logo
