Re: [openstack-dev] [cinder][3rd-party ci] Voting INSPUR-CI

[Lenny Verkhovsky]

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 Mailing List 
Cc: wangyong2...@inspur.com; inspur...@inspur.com; jiaohao...@inspur.com
Subject: [openstack-dev] [cinder][3rd-party ci] Voting INSPUR-CI

Hi Team,

Looks like we incidentally made INSPUR-CI voting for Cinder. For now, it puts 
-1 for all patches. According to [1] please make it non-voting.


[1] 
https://wiki.openstack.org/wiki/Cinder/tested-3rdParty-drivers#When_thirdparty_CI_voting_will_be_required.3F


Regards,
Ivan Kolodyazhny,
http://blog.e0ne.info/
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [openstack-ansible] Live migration issue

[Lenny Verkhovsky]

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: 
c7a5e5d1-bc22-4143-a85a-ee5c3b6777b3] You may see the error "libvirt: QEMU 
error: Domain not found: no domain with matching name." This error can be 
safely ignored.


-Original Message-
From: fabrice grelaud [mailto:fabrice.grel...@u-bordeaux.fr] 
Sent: Wednesday, January 25, 2017 1:06 PM
To: OpenStack Development Mailing List (not for usage questions) 

Subject: [openstack-dev] [openstack-ansible] Live migration issue

Hi osa team,

i ‘ve got live migration issue in one direction but not in other.
I deploy openstack with OSA, ubuntu trusty, stable/newton branch, 14.0.5 tag.

My 2 compute node are same host type and have nova-compute and cinder-volume 
(our ceph cluster as backend) services.

No problem to live migrate instance from Compute 2 to Compute 1 whereas the 
reverse is not true.
See log below:

Live migration instance Compute 2 to 1: OK

Compute 2 log
2017-01-25 11:00:15.621 28309 INFO nova.virt.libvirt.migration 
[req-6f21e4a4-28a8-48e3-bf2f-2e1ad3b52470 0329776bd1634978a7fed35a70c77479 
7531f209e3514e3f98eb58aafa480285 - - -] [instance: 
c7a5e5d1-bc22-4143-a85a-ee5c3b6777b3] Increasing downtime to 46 ms after 0 sec 
elapsed time
2017-01-25 11:00:15.787 28309 INFO nova.virt.libvirt.driver 
[req-6f21e4a4-28a8-48e3-bf2f-2e1ad3b52470 0329776bd1634978a7fed35a70c77479 
7531f209e3514e3f98eb58aafa480285 - - -] [instance: 
c7a5e5d1-bc22-4143-a85a-ee5c3b6777b3] Migration running for 0 secs, memory 100% 
remaining; (bytes processed=0, remaining=0, total=0)
2017-01-25 11:00:17.737 28309 INFO nova.compute.manager [-] [instance: 
c7a5e5d1-bc22-4143-a85a-ee5c3b6777b3] VM Paused (Lifecycle Event)
2017-01-25 11:00:17.794 28309 INFO nova.virt.libvirt.driver 
[req-6f21e4a4-28a8-48e3-bf2f-2e1ad3b52470 0329776bd1634978a7fed35a70c77479 
7531f209e3514e3f98eb58aafa480285 - - -] [instance: 
c7a5e5d1-bc22-4143-a85a-ee5c3b6777b3] Migration operation has completed
2017-01-25 11:00:17.795 28309 INFO nova.compute.manager 
[req-6f21e4a4-28a8-48e3-bf2f-2e1ad3b52470 0329776bd1634978a7fed35a70c77479 
7531f209e3514e3f98eb58aafa480285 - - -] [instance: 
c7a5e5d1-bc22-4143-a85a-ee5c3b6777b3] _post_live_migration() is started..
2017-01-25 11:00:17.815 28309 INFO oslo.privsep.daemon 
[req-6f21e4a4-28a8-48e3-bf2f-2e1ad3b52470 0329776bd1634978a7fed35a70c77479 
7531f209e3514e3f98eb58aafa480285 - - -] Running privsep helper: ['sudo', 
'nova-rootwrap', '/etc/nova/rootwrap.conf', 'privsep-helper', '--config-file', 
'/etc/nova/nova.conf', '--privsep_context', 'os_brick.privileged.default', 
'--privsep_sock_path', '/tmp/tmpfL96lI/privsep.sock']
2017-01-25 11:00:18.387 28309 INFO oslo.privsep.daemon 
[req-6f21e4a4-28a8-48e3-bf2f-2e1ad3b52470 0329776bd1634978a7fed35a70c77479 
7531f209e3514e3f98eb58aafa480285 - - -] Spawned new privsep daemon via rootwrap
2017-01-25 11:00:18.395 28309 INFO oslo.privsep.daemon [-] privsep daemon 
starting
2017-01-25 11:00:18.396 28309 INFO oslo.privsep.daemon [-] privsep process 
running with uid/gid: 0/0
2017-01-25 11:00:18.396 28309 INFO oslo.privsep.daemon [-] privsep process 
running with capabilities (eff/prm/inh): CAP_SYS_ADMIN/CAP_SYS_ADMIN/none
2017-01-25 11:00:18.396 28309 INFO oslo.privsep.daemon [-] privsep daemon 
running as pid 28815
2017-01-25 11:00:18.397 28309 INFO nova.compute.manager 
[req-aa0997d7-bf5f-480f-abc5-beadd2d03409 - - - - -] [instance: 
c7a5e5d1-bc22-4143-a85a-ee5c3b6777b3] During sync_power_state the instance has 
a pending task (migrating). Skip.
2017-01-25 11:00:18.538 28309 INFO nova.compute.manager 
[req-115a99b8-48ef-43d5-908b-5ff7aadc3df4 - - - - -] Running instance usage 
audit for host p-oscompute02 from 2017-01-25 09:00:00 to 2017-01-25 10:00:00. 2 
instances.
2017-01-25 11:00:18.691 28309 INFO nova.compute.resource_tracker 
[req-115a99b8-48ef-43d5-908b-5ff7aadc3df4 - - - - -] Auditing locally available 
compute resources for node p-oscompute02.openstack.local
2017-01-25 11:00:19.634 28309 INFO nova.compute.resource_tracker 
[req-115a99b8-48ef-43d5-908b-5ff7aadc3df4 - - - - -] Total usable vcpus: 40, 
total allocated vcpus: 4
2017-01-25 11:00:19.635 28309 INFO nova.compute.resource_tracker 
[req-115a99b8-48ef-43d5-908b-5ff7aadc3df4 - - - - -] Final resource view: 
name=p-oscompute02.openstack.local phys_ram=128700MB used_ram=6144MB 
phys_disk=33493GB used_disk=22GB total_vcpus=40 used_vcpus=4 pci_stats=[]
2017-01-25 11:00:19.709 28309 INFO nova.compute.resource_tracker 
[req-115a99b8-48ef-43d5-908b-5ff7aadc3df4 - - - - -] Compute_service record 
updated for p-oscompute02:p-oscompute02.openstack.local
2017-01-25 11:00:20.163 28309 INFO os_vif 
[req-6f21e4a4-28a8-48e3-bf2f-2e1ad3b52470 0329776bd1634978a7fed35a70c77479 

Re: [openstack-dev] [Infra] Gerrit performance time

[Lenny Verkhovsky]

+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
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [infra][nodepool][ci][keystone]

[Lenny Verkhovsky]

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 master devstack

[1] http://docs.openstack.org/infra/openstackci/third_party_ci.html
[2] http://paste.openstack.org/show/593963/
[3] http://paste.openstack.org/show/593959/
[4] http://paste.openstack.org/show/593960/
[5] http://paste.openstack.org/show/593964/
2017-01-05 00:17:00.034 185101 DEBUG keystone.middleware.auth 
[req-ba4a1c04-5ac1-47b6-ae11-641f3feb4209 - - - - -] There is either no auth 
token in the request or the certificate issuer is not trusted. No auth context 
will be set. fill_context /opt/stack/keystone/keystone/middleware/auth.py:188
2017-01-05 00:17:00.035 185101 INFO keystone.common.wsgi 
[req-ba4a1c04-5ac1-47b6-ae11-641f3feb4209 - - - - -] POST 
http://10.224.33.32/identity/v3/auth/tokens
2017-01-05 00:17:00.046 185101 ERROR keystone.common.wsgi 
[req-ba4a1c04-5ac1-47b6-ae11-641f3feb4209 - - - - -] object of type 'NoneType' 
has no len()


2017-01-05 00:17:00.046 185101 TRACE keystone.common.wsgi TypeError: object 
of type 'NoneType' has no len()


Thanks.
Lenny  (lennyb)
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [devstack]VersionConflict exception during stack.sh - resend with explanation.

[Lenny Verkhovsky]

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: Wednesday, December 7, 2016 8:21 AM
To: OpenStack Development Mailing List (not for usage questions) 

Subject: Re: [openstack-dev] [devstack]VersionConflict exception during 
stack.sh - resend with explanation.

Thanks Tony for reply
This is Jenkins third party.  So it is doing unstack and removing repo and 
stack again from master branch.  

It has been running OK and then it was disable for about a month.  Now when we 
reenabled it, it has this versionconflict one-by-one.  After I manually 
installed the required version for a lot of modules, it is OK now.  But I was 
just wondering why it won’t install the required package automatically instead 
of throwing exception?

You can look at our ci http://192.133.158.2:8080/job/cisco_zm_cinder/, look at 
all the failed cases yesterday.  I manually invoked pip install –c –e …   it 
will throw exception, is this really expected?  If it is not replace the 
modules with the required version, this kind of failure will happen again if 
somebody changed the requirement or constraints.

localadmin@ubuntu-dmz:/opt/stack/horizon$ sudo -H http_proxy= https_proxy= 
no_proxy= PIP_FIND_LINKS= SETUPTOOLS_SYS_PATH_TECHNIQUE=rewrite 
/usr/local/bin/pip2.7 install -c /opt/stack/requirements/upper-constraints.txt 
-v -e /opt/stack/horizon Ignoring dnspython3: markers 'python_version == "3.4"' 
don't match your environment Ignoring dnspython3: markers 'python_version == 
"3.5"' don't match your environment Obtaining file:///opt/stack/horizon
  Running setup.py (path:/opt/stack/horizon/setup.py) egg_info for package from 
file:///opt/stack/horizon
Running command python setup.py egg_info
running egg_info
writing requirements to horizon.egg-info/requires.txt
writing horizon.egg-info/PKG-INFO
writing top-level names to horizon.egg-info/top_level.txt
writing dependency_links to horizon.egg-info/dependency_links.txt
writing pbr to horizon.egg-info/pbr.json
[pbr] Processing SOURCES.txt
[pbr] In git context, generating filelist from git
warning: no files found matching 'AUTHORS'
warning: no files found matching 'ChangeLog'
warning: no previously-included files matching '*.pyc' found anywhere in 
distribution
reading manifest template 'MANIFEST.in'
warning: no files found matching '*.scss' under directory 'doc'
warning: no files found matching '*.js' under directory 'doc'
warning: no files found matching '*.html' under directory 'doc'
warning: no files found matching '*.conf' under directory 'doc'
warning: no files found matching '*.jpg' under directory 'doc'
warning: no files found matching '*.gif' under directory 'doc'
warning: no files found matching '*.csv' under directory 'horizon'
warning: no files found matching '*.template' under directory 'horizon'
warning: no files found matching '*.mo' under directory 'horizon'
warning: no files found matching '*.mo' under directory 
'openstack_dashboard'
warning: no files found matching '*.eot' under directory 
'openstack_dashboard'
warning: no files found matching '*.ttf' under directory 
'openstack_dashboard'
warning: no files found matching '*.woff' under directory 
'openstack_dashboard'
warning: no files found matching 'AUTHORS'
warning: no files found matching 'ChangeLog'
warning: no files found matching 'doc/source/_templates/.placeholder'
warning: no previously-included files found matching 
'openstack_dashboard/local/local_settings.py'
writing manifest file 'horizon.egg-info/SOURCES.txt'
  Source in /opt/stack/horizon has version 11.0.0.0b2.dev67, which satisfies 
requirement horizon==11.0.0.0b2.dev67 from file:///opt/stack/horizon Cleaning 
up...
Exception:
Traceback (most recent call last):
  File "/usr/local/lib/python2.7/dist-packages/pip/basecommand.py", line 215, 
in main
status = self.run(options, args)
  File "/usr/local/lib/python2.7/dist-packages/pip/commands/install.py", line 
335, in run
wb.build(autobuilding=True)
  File "/usr/local/lib/python2.7/dist-packages/pip/wheel.py", line 749, in build
self.requirement_set.prepare_files(self.finder)
  File "/usr/local/lib/python2.7/dist-packages/pip/req/req_set.py", line 380, 
in prepare_files
ignore_dependencies=self.ignore_dependencies))
  File "/usr/local/lib/python2.7/dist-packages/pip/req/req_set.py", line 521, 
in _prepare_file
req_to_install.check_if_exists()
  File "/usr/local/lib/python2.7/dist-packages/pip/req/req_install.py", line 
1036, in check_if_exists
self.req.name
  File 
"/usr/local/lib/python2.7/dist-packages/pip/_vendor/pkg_resources/__init__.py", 
line 558, in get_distribution
dist = 

Re: [openstack-dev] [cinder] [third-party][ci] devstack failures

[Lenny Verkhovsky]

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 SIGINT 0 git clone git://git.openstack.org/openstack/horizon.git 
/opt/stack/horizon --branch master
2016-12-05 01:19:17.358 | Cloning into '/opt/stack/horizon'...
2016-12-05 03:20:41.160 | fatal: read error: Connection reset by peer
2016-12-05 03:20:41.165 | fatal: early EOF



From: Apoorva Deshpande [mailto:apps.d...@gmail.com]
Sent: Monday, December 5, 2016 7:43 AM
To: openstack-dev@lists.openstack.org
Subject: [openstack-dev] [cinder] [third-party][ci] devstack failures

Hello,

I am encountering devstack failures on our Cinder CI [1]. Could you please help 
me debug this? Last successful devstack installation was [2].
[https://ssl.gstatic.com/ui/v1/icons/mail/images/cleardot.gif]

[1] http://openstack-ci.tintri.com/tintri/refs-changes-23-405223-4/
[2] http://openstack-ci.tintri.com/tintri/refs-changes-95-393395-7/

thanks,
@apoorva
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [openstack][neutron] DHCP agent: advertise SLAAC prefixes Exceptions

[Lenny Verkhovsky]

This is also a latest dnsmask for uname -a
Linux cloudx-24.rdmz.labs.mlnx 3.10.0-327.el7.x86_64 #1 SMP Thu Oct 29 17:29:29 
EDT 2015 x86_64 x86_64 x86_64 GNU/Linux
bash-4.2$ cat /etc/redhat-release
Red Hat Enterprise Linux Server release 7.2 (Maipo)


#neutron-sanity-check  --config-file /etc/neutron/neutron.conf --config-file 
/etc/neutron/dhcp_agent.ini
Guru meditation now registers SIGUSR1 and SIGUSR2 by default for backward 
compatibility. SIGUSR1 will no longer be registered in a future release, so 
please use SIGUSR2 to generate reports.
2016-11-24 17:17:06.623 17608 INFO neutron.common.config [-] Logging enabled!
2016-11-24 17:17:06.623 17608 INFO neutron.common.config [-] 
/usr/bin/neutron-sanity-check version 10.0.0.0b2.dev118
2016-11-24 17:17:08.479 INFO oslo_rootwrap.client [-] Spawned new rootwrap 
daemon process with pid=17621
2016-11-24 17:17:08.580 INFO neutron.agent.ovsdb.native.vlog [-] 
tcp:127.0.0.1:6640: connecting...
2016-11-24 17:17:08.580 INFO neutron.agent.ovsdb.native.vlog [-] 
tcp:127.0.0.1:6640: connected
2016-11-24 17:17:09.296 ERROR neutron.cmd.sanity_check [-] The installed 
version of dnsmasq is too old. Please update to at least version 2.67.
2016-11-24 17:17:09.298 INFO oslo_rootwrap.client [-] Stopping rootwrap daemon 
process with pid=17621



> -Original Message-
> From: Ihar Hrachyshka [mailto:ihrac...@redhat.com]
> Sent: Thursday, November 24, 2016 4:41 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
> 
> 
> > On 24 Nov 2016, at 15:31, Jens Rosenboom <j.rosenb...@x-ion.de> wrote:
> >
> > 2016-11-24 15:08 GMT+01:00 Lenny Verkhovsky <len...@mellanox.com>:
> >> Hi,
> >>
> >> The DHCP Agent commit[1] added a lot of exceptions into Mellanox CI
> >
> > What OS is the CI running on? Can you show the output of "dnsmasq
> > --version" and "neutron-sanity-check" on a CI node?
> 
> I think you need to pass --config-file /etc/neutron/neutron.conf --config-file
> /etc/neutron/dhcp_agent.ini to the tool to make it trigger the dnsmasq version
> check you probably expect to fail.
> 
> That said, I believe that check should be removed:
> https://review.openstack.org/#/c/402003/
> 
> Ihar
> 
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [openstack][neutron] DHCP agent: advertise SLAAC prefixes Exceptions

[Lenny Verkhovsky]

RH7.2

#dnsmasq --version
Dnsmasq version 2.66  Copyright (c) 2000-2013 Simon Kelley
Compile time options: IPv6 GNU-getopt DBus no-i18n IDN DHCP DHCPv6 no-Lua TFTP 
no-conntrack ipset auth
This software comes with ABSOLUTELY NO WARRANTY.
Dnsmasq is free software, and you are welcome to redistribute it
under the terms of the GNU General Public License, version 2 or 3.

#neutron-sanity-check
Guru meditation now registers SIGUSR1 and SIGUSR2 by default for backward 
compatibility. SIGUSR1 will no longer be registered in a future release, so 
please use SIGUSR2 to generate reports.
2016-11-24 16:37:39.512 17367 INFO neutron.common.config [-] Logging enabled!
2016-11-24 16:37:39.513 17367 INFO neutron.common.config [-] 
/usr/bin/neutron-sanity-check version 10.0.0.0b2.dev118


> -Original Message-
> From: Jens Rosenboom [mailto:j.rosenb...@x-ion.de]
> Sent: Thursday, November 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 <len...@mellanox.com>:
> > Hi,
> >
> > The DHCP Agent commit[1] added a lot of exceptions into Mellanox CI
> 
> What OS is the CI running on? Can you show the output of "dnsmasq --version"
> and "neutron-sanity-check" on a CI node?
> 
> 
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [openstack][neutron] DHCP agent: advertise SLAAC prefixes Exceptions

[Lenny Verkhovsky]

10x


> -Original Message-
> From: Ihar Hrachyshka [mailto:ihrac...@redhat.com]
> Sent: Thursday, November 24, 2016 4:16 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
> 
> 
> > On 24 Nov 2016, at 15:08, Lenny Verkhovsky <len...@mellanox.com> wrote:
> >
> > Hi,
> > The DHCP Agent commit[1] added a lot of exceptions into Mellanox CI
> >
> >
> > [1] https://review.openstack.org/#/c/393007/
> 
> We probably revert the patch: https://review.openstack.org/#/c/401985/
> 
> Ihar
> 
> 
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [openstack][neutron] DHCP agent: advertise SLAAC prefixes Exceptions

[Lenny Verkhovsky]

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-7b36-4afe-8969-ca7b931abd82 - -] Running command (rootwrap 
daemon): ['ip', 'netns', 'exec', 'qdhcp-cffeeda9-94b5-41bf-998e-d87c7a3a25a1', 
'dnsmasq', '--no-hosts', '', '--strict-order', '--except-interface=lo', 
'--pid-file=/opt/stack/data/neutron/dhcp/cffeeda9-94b5-41bf-998e-d87c7a3a25a1/pid',
 
'--dhcp-hostsfile=/opt/stack/data/neutron/dhcp/cffeeda9-94b5-41bf-998e-d87c7a3a25a1/host',
 
'--addn-hosts=/opt/stack/data/neutron/dhcp/cffeeda9-94b5-41bf-998e-d87c7a3a25a1/addn_hosts',
 
'--dhcp-optsfile=/opt/stack/data/neutron/dhcp/cffeeda9-94b5-41bf-998e-d87c7a3a25a1/opts',
 
'--dhcp-leasefile=/opt/stack/data/neutron/dhcp/cffeeda9-94b5-41bf-998e-d87c7a3a25a1/leases',
 '--dhcp-match=set:ipxe,175', '--enable-ra', '--ra-param=tapf5c8ccfc-b4,0,0', 
'--bind-interfaces', '--interface=tapf5c8ccfc-b4', 
'--dhcp-range=set:tag0,172.0.0.0,static,86400s', 
'--dhcp-option-force=option:mtu,1500', '--dhcp-lease-max=64', '--conf-file=', 
'--domain=openstacklocal'] execute_rootwrap_daemon 
/opt/stack/neutron/neutron/agent/linux/utils.py:108

2016-11-23 06:37:49.979 28150 ERROR neutron.agent.linux.utils 
[req-ec66fd16-7b36-4afe-8969-ca7b931abd82 - -] Exit code: 1; Stdin: ; Stdout: ; 
Stderr:

dnsmasq: bad command line options: try --help



2016-11-23 06:37:49.980 28150 ERROR neutron.agent.dhcp.agent 
[req-ec66fd16-7b36-4afe-8969-ca7b931abd82 - -] Unable to enable dhcp for 
cffeeda9-94b5-41bf-998e-d87c7a3a25a1.

2016-11-23 06:37:49.980 28150 ERROR neutron.agent.dhcp.agent Traceback (most 
recent call last):

2016-11-23 06:37:49.980 28150 ERROR neutron.agent.dhcp.agent   File 
"/opt/stack/neutron/neutron/agent/dhcp/agent.py", line 115, in call_driver

2016-11-23 06:37:49.980 28150 ERROR neutron.agent.dhcp.agent 
getattr(driver, action)(**action_kwargs)

2016-11-23 06:37:49.980 28150 ERROR neutron.agent.dhcp.agent   File 
"/opt/stack/neutron/neutron/agent/linux/dhcp.py", line 216, in enable

2016-11-23 06:37:49.980 28150 ERROR neutron.agent.dhcp.agent 
self.spawn_process()

2016-11-23 06:37:49.980 28150 ERROR neutron.agent.dhcp.agent   File 
"/opt/stack/neutron/neutron/agent/linux/dhcp.py", line 437, in spawn_process

2016-11-23 06:37:49.980 28150 ERROR neutron.agent.dhcp.agent 
self._spawn_or_reload_process(reload_with_HUP=False)

2016-11-23 06:37:49.980 28150 ERROR neutron.agent.dhcp.agent   File 
"/opt/stack/neutron/neutron/agent/linux/dhcp.py", line 451, in 
_spawn_or_reload_process

2016-11-23 06:37:49.980 28150 ERROR neutron.agent.dhcp.agent 
pm.enable(reload_cfg=reload_with_HUP)

2016-11-23 06:37:49.980 28150 ERROR neutron.agent.dhcp.agent   File 
"/opt/stack/neutron/neutron/agent/linux/external_process.py", line 94, in enable

2016-11-23 06:37:49.980 28150 ERROR neutron.agent.dhcp.agent 
run_as_root=self.run_as_root)

2016-11-23 06:37:49.980 28150 ERROR neutron.agent.dhcp.agent   File 
"/opt/stack/neutron/neutron/agent/linux/ip_lib.py", line 882, in execute

2016-11-23 06:37:49.980 28150 ERROR neutron.agent.dhcp.agent 
log_fail_as_error=log_fail_as_error, **kwargs)

2016-11-23 06:37:49.980 28150 ERROR neutron.agent.dhcp.agent   File 
"/opt/stack/neutron/neutron/agent/linux/utils.py", line 147, in execute

2016-11-23 06:37:49.980 28150 ERROR neutron.agent.dhcp.agent raise 
ProcessExecutionError(msg, returncode=returncode)

2016-11-23 06:37:49.980 28150 ERROR neutron.agent.dhcp.agent 
ProcessExecutionError: Exit code: 1; Stdin: ; Stdout: ; Stderr:

2016-11-23 06:37:49.980 28150 ERROR neutron.agent.dhcp.agent dnsmasq: bad 
command line options: try --help

2016-11-23 06:37:49.980 28150 ERROR neutron.agent.dhcp.agent

2016-11-23 06:37:49.980 28150 ERROR neutron.agent.dhcp.agent

Please advice
Lenny.
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [nova] Nova-MultiJob CI (non-voting) request to comment

[Lenny Verkhovsky]

Matt, Chris,
Thanks, your filtering suggestion will be added when possible.

> -Original Message-
> From: Matt Riedemann [mailto:mrie...@linux.vnet.ibm.com]
> Sent: Friday, November 04, 2016 9:42 PM
> To: openstack-dev@lists.openstack.org
> Subject: Re: [openstack-dev] [nova] 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 tests
> are skipped.
> >
> 
> I think this was mentioned at the summit. In general we have a major gap in
> multinode testing for NFV features like PCI so this would be a welcome
> addition. As noted elsewhere there are other ares of nova to expand the
> coverage for this, like I'd recommend any changes to
> nova/compute/* and nova/network/* to be tested under this. But starting
> small makes sense.
> 
> --
> 
> Thanks,
> 
> Matt Riedemann
> 
> 
> __
> 
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-
> requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [nova] Nova-MultiJob CI (non-voting) request to comment

[Lenny Verkhovsky]

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 tests 
are skipped.

> -Original Message-
> From: Matt Riedemann [mailto:mrie...@linux.vnet.ibm.com]
> Sent: Friday, November 04, 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 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] tempest/ scenario
> >
> > [4]
> > http://13.69.151.247/98/348498/6/check-sriov-tempest/Nova-ML2-Sriov-
> Mu
> > ltinode/46e401e/testr_results.html.gz
> >
> > [5] https://review.openstack.org/#/c/348498/6
> >
> >
> >
> >
> >
> > Thanks
> >
> > Lenny (aka lennyb on irc)
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> __
> 
> >  OpenStack Development Mailing List (not for usage questions)
> > Unsubscribe:
> > openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> >
> 
> What's different about this job configuration from the other Mellanox CIs
> that already run against nova?
> 
> --
> 
> Thanks,
> 
> Matt Riedemann
> 
> 
> __
> 
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-
> requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] Nova-MultiJob CI (non-voting) request to comment

[Lenny Verkhovsky]

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] tempest/ scenario
[4] 
http://13.69.151.247/98/348498/6/check-sriov-tempest/Nova-ML2-Sriov-Multinode/46e401e/testr_results.html.gz
[5] https://review.openstack.org/#/c/348498/6


Thanks
Lenny (aka lennyb on irc)





__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] Running a skipped tempest test: test_connectivity_between_vms_on_different_networks

[Lenny Verkhovsky]

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_network_basic_ops.TestNetworkBasicOps.test_connectivity_between_vms_on_different_networks




From: Yossi Tamarov [mailto:yossi.tama...@gmail.com]
Sent: Wednesday, October 19, 2016 10:49 PM
To: openstack-dev@lists.openstack.org
Subject: [openstack-dev] Running a skipped tempest test: 
test_connectivity_between_vms_on_different_networks

Hello everyone,
Is there a way to force this tempest test to run?
tempest.scenario.test_network_basic_ops.TestNetworkBasicOps.test_connectivity_between_vms_on_different_networks

Currently, I'm trying to run the next command, which is followed by the next 
outputץ
Thanks for any help,
Joseph.
 [root@devel tempest]# ostestr --regex 
'(?!.*\[.*\bslow\b.*\])('tempest.scenario.test_network_basic_ops.TestNetworkBasicOps.test_connectivity_between_vms_on_different_networks')'
running=OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \
OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-500} \
OS_TEST_LOCK_PATH=${OS_TEST_LOCK_PATH:-${TMPDIR:-'/tmp'}} \
${PYTHON:-python} -m subunit.run discover -t ${OS_TOP_LEVEL:-./} 
${OS_TEST_PATH:-./tempest/test_discover} --list
running=OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} \
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} \
OS_TEST_TIMEOUT=${OS_TEST_TIMEOUT:-500} \
OS_TEST_LOCK_PATH=${OS_TEST_LOCK_PATH:-${TMPDIR:-'/tmp'}} \
${PYTHON:-python} -m subunit.run discover -t ${OS_TOP_LEVEL:-./} 
${OS_TEST_PATH:-./tempest/test_discover}  --load-list /tmp/tmphXpVFo
{0} 
tempest.scenario.test_network_basic_ops.TestNetworkBasicOps.test_connectivity_between_vms_on_different_networks
 ... SKIPPED: Skipped until Bug: 1610994 is resolved.

==
Totals
==
Ran: 1 tests in 6. sec.
 - Passed: 0
 - Skipped: 1
 - Expected Fail: 0
 - Unexpected Success: 0
 - Failed: 0
Sum of execute time for each test: 0.0006 sec.

==
Worker Balance
==
 - Worker 0 (1 tests) => 0:00:00.000619

No tests were successful during the run

Slowest Tests:

Test id 

  Runtime (s)

  ---
tempest.scenario.test_network_basic_ops.TestNetworkBasicOps.test_connectivity_between_vms_on_different_networks[compute,id-1546850e-fbaa-42f5-8b5f-03d8a6a95f15,network]
  0.001

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] SRIOV-port refused to bind

[Lenny Verkhovsky]

Hi Murali,

Try adding filters to nova.conf
scheduler_available_filters=nova.scheduler.filters.all_filters
scheduler_default_filters = RetryFilter, AvailabilityZoneFilter, RamFilter, 
ComputeFilter, ComputeCapabilitiesFilter, ImagePropertiesFilter, 
PciPassthroughFilter

is it possible to upload all neutron and nova logs and neutron and nova config 
files?

Here[1] you can see local.conf from Mellanox CI as an example

[1] 
http://13.69.151.247/26/382126/1/check-nova/Nova-ML2-Sriov/b835c17/local.conf.gz

From: Murali B [mailto:mbi...@gmail.com]
Sent: Thursday, September 29, 2016 10:46 PM
To: Lenny Verkhovsky <len...@mellanox.com>; OpenStack Development Mailing List 
(not for usage questions) <openstack-dev@lists.openstack.org>
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-Passthrough-For-Networking and set the 
"intel_iommu=on".

Here is the output for the VF's config

root@A1-22932-compute1:~# cat /proc/cmdline
BOOT_IMAGE=/vmlinuz-4.2.0-42-generic 
root=UUID=ff1b5507-414f-4c96-9fbe-cc3c02c682fc ro intel_iommu=on igbe.max_vfs=2 
pci=assign-busses quiet splash vt.handoff=7

root@A1-22932-compute1:~# lspci | grep Ether
03:00.0 Ethernet controller: Intel Corporation 82576 Gigabit Network Connection 
(rev 01)
03:00.1 Ethernet controller: Intel Corporation 82576 Gigabit Network Connection 
(rev 01)
04:10.0 Ethernet controller: Intel Corporation 82576 Virtual Function (rev 01)
04:10.1 Ethernet controller: Intel Corporation 82576 Virtual Function (rev 01)
04:10.2 Ethernet controller: Intel Corporation 82576 Virtual Function (rev 01)
04:10.3 Ethernet controller: Intel Corporation 82576 Virtual Function (rev 01)
08:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network Connection
09:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network Connection

root@A1-22932-compute1:~# ls /sys/bus/pci/devices/\:04\:10.0/net/
eth1


Please find the config here http://pastebin.com/Tfaez4Je

here are the logs on controller http://pastebin.com/e3s1LaMw

here is the nova-compute log http://pastebin.com/qRzG6Tif

Thanks
-Murali





__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] SRIOV-port refused to bind

[Lenny Verkhovsky]

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...@gmail.com]
Sent: Thursday, September 29, 2016 5:52 AM
To: OpenStack Development Mailing List (not for usage questions) 

Subject: [openstack-dev] SRIOV-port refused to bind

Hi

I am using the SRIOV on mitaka. When I try to launch the VM with SRIOV port its 
failed.

When I see the neutrn-server.log I see that below message on controller.

ddf81 - - -] Refusing to bind due to unsupported vnic_type: direct bind_port 
/usr/lib/python2.7/dist-packages/neutron/plugins/ml2/drivers/mech_agent.py:65
2016-09-28 18:55:18.384 16531 ERROR neutron.plugins.ml2.managers 
[req-443e9b6a-45c6-4b30-aa50-52a9b0a4926c 7d0ef58dd1214f54983c9d843fec0bde 
238c9900a2ae4b57b01fa72abdeddf81 - - -] Failed to bind port 
e96eadf3-5501-442a-8bcc-0b4d64617b26 on host A1-22932-compute1 for vnic_type 
direct using segments [{'segmentation_id': 123, 'physical_network': 
u'physnet1', 'id': u'30b77081-d02c-4e29-a41a-f8997c1f9f66', 'network_type': 
u'vlan'}]

On compute node I see the below error.

2016-09-28 18:55:18.688 7651 ERROR nova.compute.manager [instance: 
4c737a89-51b8-4504-a208-05f2da178482] flavor, virt_type, self._host)
2016-09-28 18:55:18.688 7651 ERROR nova.compute.manager [instance: 
4c737a89-51b8-4504-a208-05f2da178482]   File 
"/usr/lib/python2.7/dist-packages/nova/virt/libvirt/vif.py", line 447, in 
get_config
2016-09-28 18:55:18.688 7651 ERROR nova.compute.manager [instance: 
4c737a89-51b8-4504-a208-05f2da178482] _("Unexpected vif_type=%s") % 
vif_type)
2016-09-28 18:55:18.688 7651 ERROR nova.compute.manager [instance: 
4c737a89-51b8-4504-a208-05f2da178482] NovaException: Unexpected 
vif_type=binding_failed

Could somebody help me to come-out this issue.


Thanks
-Murali
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [all][infra] NOT_REGISTERED to be or not to be

[Lenny Verkhovsky]

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 some important CI comments, it can rechecked later or 
sent an email to CI owner.

[1] No valid slaves
   Not all jobs are registered due to zuul restart for instance

[2] 
http://eavesdrop.openstack.org/irclogs/%23openstack-meeting/%23openstack-meeting.2016-08-01.log.html


Thanks.
Lenny
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tempest][SR-IOV] tempest breaks Mellanox CI

[Lenny Verkhovsky]

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, 2016 at 11:16 AM Moshe Levi 
> wrote:

Hi all,



A recent change  [1]  in tempest broke all Mellanox CIs.

This is the second time it happened.

After the first time it happened we decided that  Mellanox CI  will comment on 
tempest.

On this time I saw that Mellanox CI was commenting on that  patch with a 
failure but was still got approved - [2] Enabling Mellanox CI as commenting on  
tempest requires  us physical resources  such as servers/NICS because it tests 
SR-IOV.

So I am wandering  what can be done in the future to prevent this from happen 
again.
A message to the DL is a good way to raise awareness on this.
Ensuring the job stability is also important, too many failures will decrease 
the attention on it - that said I don't have numbers for Mellanox CI failure 
rates, so it may be that the pass rate is already good enough.



Anyway we proposed the following fix to tempest [3]
Thanks for fixing this, and sorry about the inconvenience.
Even with the fix in, the Mellanox CI job failed, which if unfortunate.
I issued a re-check.

Andrea Frittoli





[1] - https://review.openstack.org/#/c/320495/

[2] - 
http://13.69.151.247/95/320495/20/check-sriov-tempest/Tempest-Sriov/825304c/testr_results.html.gz

[3] - https://review.openstack.org/#/c/330331/



__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: 
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [cinder] changes in Mellanox Cinder CI

[Lenny Verkhovsky]

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://wiki.openstack.org/wiki/ThirdPartySystems/Mellanox_CI
[3] mlnx-openstack...@dev.mellanox.co.il
[4] Nova, Neutron, Cinder, Tempest, Ironic(future)
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [nova] Is the Intel SRIOV CI running and if so, what does it test?

[Lenny Verkhovsky]

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


-Original Message-
From: Matt Riedemann [mailto:mrie...@linux.vnet.ibm.com] 
Sent: Wednesday, March 30, 2016 6:22 PM
To: OpenStack Development Mailing List (not for usage questions) 

Cc: shaohe.f...@intel.com
Subject: [openstack-dev] [nova] Is the Intel SRIOV CI running and if so, what 
does it test?

Intel has a few third party CIs in the third party systems wiki [1].

I was talking with Moshe Levi today about expanding coverage for mellanox CI in 
nova, today they run an SRIOV CI for vnic type 'direct'. 
I'd like them to also start running their 'macvtap' CI on the same nova changes 
(that job only runs in neutron today I think).

I'm trying to see what we have for coverage on these different NFV 
configurations, and because of limited resources to run NFV CI, don't want to 
duplicate work here.

So I'm wondering what the various Intel NFV CI jobs run, specifically the Intel 
Networking CI [2], Intel NFV CI [3] and Intel SRIOV CI [4].

 From the wiki it looks like the Intel Networking CI tests ovs-dpdk but only 
for Neutron. Could that be expanded to also test on Nova changes that hit a 
sub-set of the nova tree?

I really don't know what the latter two jobs test as far as configuration is 
concerned, the descriptions in the wikis are pretty empty (please update those 
to be more specific).

Please also include in the wiki the recheck method for each CI so I don't have 
to dig through Gerrit comments to find one.

[1] https://wiki.openstack.org/wiki/ThirdPartySystems
[2] https://wiki.openstack.org/wiki/ThirdPartySystems/Intel-Networking-CI
[3] https://wiki.openstack.org/wiki/ThirdPartySystems/Intel-NFV-CI
[4] https://wiki.openstack.org/wiki/ThirdPartySystems/Intel-SRIOV-CI

-- 

Thanks,

Matt Riedemann


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Tempest][cinder] jenkins fails due to server fault

[Lenny Verkhovsky]

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 tempest_lib to 
tempest.lib
2016-03-18 11:06:56.149 |   DeprecationWarning)
2016-03-18 11:06:56.322 | Traceback (most recent call last):
2016-03-18 11:06:56.322 |   File ".tox/venv/bin/tempest", line 10, in 
2016-03-18 11:06:56.322 | sys.exit(main())
2016-03-18 11:06:56.322 |   File "/opt/stack/tempest/tempest/cmd/main.py", line 
48, in main
2016-03-18 11:06:56.322 | return the_app.run(argv)
2016-03-18 11:06:56.322 |   File 
"/opt/stack/tempest/.tox/venv/local/lib/python2.7/site-packages/cliff/app.py", 
line 226, in run
2016-03-18 11:06:56.322 | result = self.run_subcommand(remainder)
2016-03-18 11:06:56.322 |   File 
"/opt/stack/tempest/.tox/venv/local/lib/python2.7/site-packages/cliff/app.py", 
line 309, in run_subcommand
2016-03-18 11:06:56.322 | subcommand = 
self.command_manager.find_command(argv)
2016-03-18 11:06:56.322 |   File 
"/opt/stack/tempest/.tox/venv/local/lib/python2.7/site-packages/cliff/commandmanager.py",
 line 75, in find_command
2016-03-18 11:06:56.322 | cmd_factory = cmd_ep.resolve()
2016-03-18 11:06:56.322 |   File 
"/opt/stack/tempest/.tox/venv/local/lib/python2.7/site-packages/pkg_resources/__init__.py",
 line 2208, in resolve
2016-03-18 11:06:56.323 | module = __import__(self.module_name, 
fromlist=['__name__'], level=0)
2016-03-18 11:06:56.323 |   File 
"/opt/stack/tempest/tempest/cmd/verify_tempest_config.py", line 29, in 
2016-03-18 11:06:56.323 | from tempest import clients
2016-03-18 11:06:56.323 |   File "/opt/stack/tempest/tempest/clients.py", line 
158, in 
2016-03-18 11:06:56.323 | from 
tempest.services.volume.v1.json.backups_client import BackupsClient
2016-03-18 11:06:56.323 |   File 
"/opt/stack/tempest/tempest/services/volume/v1/json/backups_client.py", line 
16, in 
2016-03-18 11:06:56.323 | from tempest.services.volume.base import 
base_backups_client
2016-03-18 11:06:56.323 |   File 
"/opt/stack/tempest/tempest/services/volume/base/base_backups_client.py", line 
21, in 
2016-03-18 11:06:56.323 | from tempest.lib.common import rest_client
2016-03-18 11:06:56.323 | ImportError: No module named lib.common
2016-03-18 11:06:56.348 | ERROR: InvocationError: 
'/opt/stack/tempest/.tox/venv/bin/tempest verify-config -uro 
../../../tmp/tmp.c1QPWmYfhW'
2016-03-18 11:06:56.349 | ___ summary 

2016-03-18 11:06:56.349 | ERROR:   venv: commands failed



[1] 
http://144.76.193.39/ci-artifacts/284106/3/Tempest-Sriov/logs/stack.sh.log.gz

From: Ivan Kolodyazhny [mailto:e...@e0ne.info]
Sent: Tuesday, March 22, 2016 1:39 PM
To: OpenStack Development Mailing List (not for usage questions) 

Subject: Re: [openstack-dev] [Tempest][cinder] jenkins fails due to server fault

Poornima,

Both Masayuki commented in the review request. For more details you can check 
cinder-api logs.

Regards,
Ivan Kolodyazhny,
http://blog.e0ne.info/

On Mon, Mar 21, 2016 at 8:18 AM, Poornima Kshirsagar 
> wrote:
Hi,

Wrote a Tempest test to check force_delete_backup method [1].

Check the tempest test run was successful see [2]

However jenkins fails with below trace back



Captured traceback:
2016-03-18 09:14:16.884 | ~~~
2016-03-18 09:14:16.884 | Traceback (most recent call last):
2016-03-18 09:14:16.884 |   File 
"tempest/api/volume/admin/test_volumes_backup.py", line 55, in 
test_volume_backup_create_and_force_delete_when_available
2016-03-18 09:14:16.884 | 
self.backups_adm_client.force_delete_backup(backup['id'])
2016-03-18 09:14:16.884 |   File 
"tempest/services/volume/base/base_backups_client.py", line 119, in 
force_delete_backup
2016-03-18 09:14:16.884 | resp, body = self.post('backups/%s/action' % 
(backup_id), post_body)
2016-03-18 09:14:16.884 |   File "tempest/lib/common/rest_client.py", line 
259, in post
2016-03-18 09:14:16.885 | return self.request('POST', url, 
extra_headers, headers, body)
2016-03-18 09:14:16.885 |   File "tempest/lib/common/rest_client.py", line 
642, in request
2016-03-18 09:14:16.885 | resp, resp_body)
2016-03-18 09:14:16.885 |   File "tempest/lib/common/rest_client.py", line 
761, in _error_checker
2016-03-18 09:14:16.885 | message=message)
2016-03-18 09:14:16.885 | tempest.lib.exceptions.ServerFault: Got server 
fault
2016-03-18 09:14:16.885 | Details: The server has either erred or is 
incapable of performing the requested operation.
2016-03-18 09:14:16.886 |



is this known issue  how do i fix it?



[1] https://review.openstack.org/#/c/284106/

[2] http://paste.openstack.org/show/491221/

Re: [openstack-dev] [Nova] PCI CI is down

[Lenny Verkhovsky]

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: [openstack-dev] [Nova] PCI CI is down

Hey Nova,

It seems the a bug [1] sneaked in that made the PCI CI jobs fail 100% of the 
time so they got turned off.

Fix for the bug should be making it's way through the queue soon, but it was 
hinted on the review that there may be further problems. I'd like to help fix 
these issues ASAP as the regression seems fairly fresh, but debugging is hard 
since the CI is offline (instead of just non-voting) so I can't really access 
any logs.

It'd be great if someone from the team helping out with the Intel PCI CI would 
bring it back online as a non-voting job so that we can have feedback which 
will surely help us fix it more quickly.

Cheers,
Nikola

[1] https://bugs.launchpad.net/nova/+bug/1535367

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [OpenStack-Infra] Gerrit Upgrade to ver 2.11, completed.

[Lenny Verkhovsky]

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 a proper rest query to for CI name?
Currently there is only account_id field in Gerrit response and it's not really 
human readable.

Lennyb.


-Original Message-
From: Zaro [mailto:zaro0...@gmail.com] 
Sent: Tuesday, December 22, 2015 3:21 AM
To: OpenStack Development Mailing List (not for usage questions) 

Subject: Re: [openstack-dev] [OpenStack-Infra] Gerrit Upgrade to ver 2.11, 
completed.

Hit '?' and it says '/' is find, give that a try.

Looks like in Gerrit 2.11 the 'f' to get a popup of the list of files is only 
available in unified diff view.  I don't remember if it was available in 
side-by-side view on Gerrit 2.8.

-Khai


On Mon, Dec 21, 2015 at 5:04 PM, Carl Baldwin  wrote:
> I also really miss being able to pull up the list of files in diff 
> view with the 'f' key.  Any equivalent?
>
> Carl
>
> On Mon, Dec 21, 2015 at 4:07 PM, Carl Baldwin  wrote:
>> I noticed a couple of things today while reviewing a largish page [1].
>> First, when I search for something using the browser's builtin search 
>> (Chrome, Mac OSX Yosemite), it doesn't seem to find occurrences that 
>> are not in the visible portion of the page.  For example, when I 
>> search for DNSDOMAIN, I get 1 hit from the top of the file.  The file 
>> actually has almost 30 hits for this string.  For example, scroll 
>> down to about L310 in the file.  You'll see them all over the place 
>> (and now Chrome's search finds these hits if you try again).  I use 
>> to use search within a file with the old gerrit and never noticed 
>> this problem.
>>
>> The other thing that I found annoying is when I scroll the page with 
>> my trackpad, it now jumps around sometimes to a different part of the 
>> page.  For example, I'll scroll up to find a spot in the file and 
>> when I think I've arrived, it will jump back down the file a bit.  It 
>> is disorienting.  Of course, now it isn't doing it anymore so it 
>> doesn't seem to be all the time.  It was behaving this way for a good 
>> 20 minutes trying to get through this file.
>>
>> Carl
>>
>> Carl
>>
>> [1] https://review.openstack.org/#/c/212213/36/neutron/db/dns_db.py
>>
>> On Thu, Dec 17, 2015 at 8:17 PM, Brian Haley  wrote:
>>> On 2015-12-16 16:24, openstack-dev-requ...@lists.openstack.org wrote:

 Thanks to everyone for their patience while we upgraded to Gerrit 
 2.11.  I'm happy to announce that we were able to successfully 
 completed this task at around 21:00 UTC.  You may hack away once more.

 If you encounter any problems, please let us know here or in 
 #openstack-infra on Freenode.
>>>
>>>
>>> I'm still undecided on 2.11, have to give it more time, but I have 
>>> noticed one thing that's annoying...
>>>
>>> Trying to copy text from a review no longer works easily.  When I 
>>> highlight text there's a little "bubble" pop-up of {press c to 
>>> comment}, which seems to interfere with both my three-button mouse copy 
>>> buffer, as well as Ctrl-C.
>>> Call me a nitpicker, but having to highlight text, right-button 
>>> click, Copy, right-button click, Paste, is a pain.
>>>
>>> Maybe someone has a simple work-around for that.
>>>
>>> -Brian
>>>
>>> 
>>> __ OpenStack Development Mailing List (not for usage questions)
>>> Unsubscribe: 
>>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
> __
>  OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: 
> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [Infra][Nova] Request for voting permissions for Third-party Mellanox CI system

[Lenny Verkhovsky]

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-Sriov/

Thanks.
L.

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tempest] Mellanox CI request to comment

[Lenny Verkhovsky]

Thanks, Matt,
We will start non-voting commenting as you suggested.

-Original Message-
From: Matthew Treinish [mailto:mtrein...@kortar.org] 
Sent: Monday, August 10, 2015 6:15 PM
To: OpenStack Development Mailing List (not for usage questions) 
openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [tempest] 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 tempest commits.

As long as it's not leaving -1 votes on failures (at least to start) I 
personally don't have any issue with your ci commenting on tempest changes.
There have been a couple external CI systems that have commented on tempest 
changes in the past, although there aren't too many right now.

-Matt Treinish

 
 We are running SR-IOV tempest tests on Mellanox HW.
 
 Our CI results can be viewed here[2]
 Our CI 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
 

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [tempest] Mellanox CI request to comment

[Lenny Verkhovsky]

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 tempest commits.

We are running SR-IOV tempest tests on Mellanox HW.

Our CI results can be viewed here[2]
Our CI 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

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [nova] [oslo] troubling passing of unit tests on broken code

[Lenny Verkhovsky]

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 usage questions)
Subject: [openstack-dev] [nova] [oslo] troubling passing of unit tests on 
broken code

Just a heads up that this recently merged code is wrong:

https://review.openstack.org/#/c/192760/14/nova/tests/unit/db/test_migrations.py,cm

and here it is failing tests on my local env, as it does on my CI, as would be 
expected, there's a lot more if I keep it running:

http://paste.openstack.org/show/412236/

However, utterly weirdly, all those tests *pass* with the same versions of 
everything in the gate:

http://paste.openstack.org/show/412236/


I have no idea why this is.  This might be on the oslo.db side within 
the test_migrations logic, not really sure.If someone feels like 
digging in, that would be great.

The failure occurs with both Alembic 0.7.7 and Alembic 0.8 as yet unreleased.  
I have a feeling that releasing Alembic 0.8 may or may not bump this failure to 
be more widespread, just because of its apparent heisenbuggy nature, and I'm 
really hoping to release 0.8 next week.  It was supposed to be this week but I 
got sidetracked.



__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] ThirdPartyCI: Tempest job fails with Unexpected termination of the channel

[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)
Subject: [openstack-dev] ThirdPartyCI: Tempest job fails with Unexpected 
termination of the channel

Short story:
- all runs of the tempest job are failing after ~ 1,5 - 2 hrs with  FATAL: 
java.io.IOException: Unexpected termination of the channel and jenkins logs 
SEVERE: I/O error in channel d-p-c-local_01-1655 java.io.IOException: 
Unexpected termination of the channel

Long story:
- Host is 4 core Intel Xeon, 32GB RAM, 3x1TB HDD
-- devstack is 2015.1.1, networking is done via n-net
- Jenkins master is a VM, 2 core, 8 GB RAM, 500 GB disk
-- not managed through devstack, but using virsh, networking done manually via 
iptables
- test slaves are VMs, m1.large (4 VCPU, 8 GB RAM, trusty), managed by nodepool

Load on master is usually around 6-7, memory usage around 90%, little swapping.

I tried increasing ClientAliveInterval/ServerAliveInterval and 
ClientAliveCountMax/ServerAliveCountMax on both the Jenkins VM and on the test 
vm (using the job to configure), but it still fails with the above mentioned 
error.

On the host, dmesg is full of: (not sure if directly related to this)
[1037245.231196] br100: port 2(vnet1) entered disabled state
followed by
[1037259.147672] br100: port 2(vnet1) entered forwarding state

I think it might be something related to networking on the host itself but i 
couldn't figure it yet.

Any suggestion on what to try next?

Thanks,
Eduard

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [nova] Mellanox CI Issues

[Lenny Verkhovsky]

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 Mailing List (not for usage questions)
Cc: Moshe Levi; Lenny Verkhovsky
Subject: [nova] Mellanox CI Issues

Hi,

Mellanox CI has been broken for a while now. Test runs are reported as 
successful after an impossibly short less-than-a-minute run. Could the owners 
of this please take a look and address the problem? At least disabling 
commenting while working on the issue would be helpful.

Also, on success, the bot doesn't post the log files, which is (a) inconsistent 
with other test bots and (b) not very helpful for validating that success is 
real. This is especially relevant right now, given that we know the success 
reports are erroneous at the moment.

This is the second time (in recent memory) that Mellanox CI has gone off the 
rails for a decent amount of time without being noticed by the owners. If this 
continues, I'll be in favor of removing commenting privileges for this account 
and will be hesitant to throw in my support for re-enabling it. Running CI 
against gerrit comes with serious responsibility for monitoring!

Thanks!

--Dan

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] Mellanox request for permission for Nova CI

[Lenny Verkhovsky]

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] 
Sent: Monday, May 04, 2015 6:20 PM
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] Mellanox request for permission for Nova CI



On 5/3/2015 10:32 AM, Lenny Verkhovsky wrote:
 Hi Dan and the team,

 Here you can see full logs and tempest.conf  
 http://144.76.193.39/ci-artifacts/Check-MLNX-Nova-ML2-Sriov-driver_POR
 T_20150503_1854/ ( suspend-resume test is skipped and we are checking 
 this issue )

 Except of running Tempest API on Mellanox flavor VM we are also 
 running 
 tempest.scenario.test_network_advanced_server_ops.TestNetworkAdvancedS
 erverOps 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
 Fax:+972 72 257 9400

 -Original Message-
 From: Dan Smith [mailto:d...@danplanet.com]
 Sent: Friday, April 24, 2015 7:43 PM
 To: OpenStack Development Mailing List (not for usage questions)
 Subject: Re: [openstack-dev] Mellanox request for permission for Nova 
 CI

 Hi Lenny,

 Is there anything missing for us to start 'non-voting' Nova CI ?

 Sorry for the slow response from the team.

 The results that you've posted look good to me. A quick scan of the tempest 
 results don't seem to indicate any new tests that are specifically testing 
 SRIOV things. I assume this is mostly implied because of the flavor you're 
 configuring for testing, right?

 Could you also persist the tempest.conf just so it's easy to see?

 Regardless of the above, I think that the results look clean enough to start 
 commenting on patches, IMHO. So, count me as +1.

 --Dan

 __
  OpenStack Development Mailing List (not for usage questions)
 Unsubscribe: 
 openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

 __
  OpenStack Development Mailing List (not for usage questions)
 Unsubscribe: 
 openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


+1 for non-voting on nova changes from me.  Looks like it's running
tests from the tempest repo and not a private third party repo which is good.

-- 

Thanks,

Matt Riedemann


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] Mellanox request for permission for Nova CI

[Lenny Verkhovsky]

Hi Dan and the team,

Here you can see full logs and tempest.conf  
http://144.76.193.39/ci-artifacts/Check-MLNX-Nova-ML2-Sriov-driver_PORT_20150503_1854/
( suspend-resume test is skipped and we are checking this issue )

Except of running Tempest API on Mellanox flavor VM we are also running 
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
Fax:+972 72 257 9400

-Original Message-
From: Dan Smith [mailto:d...@danplanet.com] 
Sent: Friday, April 24, 2015 7:43 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] Mellanox request for permission for Nova CI

Hi Lenny,

 Is there anything missing for us to start 'non-voting' Nova CI ?

Sorry for the slow response from the team.

The results that you've posted look good to me. A quick scan of the tempest 
results don't seem to indicate any new tests that are specifically testing 
SRIOV things. I assume this is mostly implied because of the flavor you're 
configuring for testing, right?

Could you also persist the tempest.conf just so it's easy to see?

Regardless of the above, I think that the results look clean enough to start 
commenting on patches, IMHO. So, count me as +1.

--Dan

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [neutron-lbaas] [third-party] trying to set up 3rd party CI, neutron-lbaas tox fails to import some neutron

[Lenny Verkhovsky]

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: OpenStack Development Mailing List (not for usage questions)
Subject: [openstack-dev] [neutron-lbaas] [third-party] trying to set up 3rd 
party CI, neutron-lbaas tox fails to import some neutron


Hi all



I am having trouble running tox tests on neutron-lbaas on a default clone. I 
can see from the tox logs that it downloads the neutron egg just fine, however, 
when running some of the tests it gets import errors when trying to import from 
the neutron side of things.



I checked the neutron repo and it does indeed seem like the files its trying to 
import do not exist within the neutron repo tox downloads. Some neutron files 
do successfully import apparently but majority are referencing files that do 
not exist in the location its referencing.



Am I missing something fundamental here?



I included some of the errors below just to give an idea of what fails.



Any help would be appreciated



I am using Ubuntu Server 14.04.2 LTS



Thanks

Shane





py27 runtests: PYTHONHASHSEED='0'
py27 runtests: commands[0] | sh tools/pretty_tox.sh
running testr
Non-zero exit code (2) from test listing.
error: testr failed (3)
running=OS_STDOUT_CAPTURE=${OS_STDOUT_CAPTURE:-1} 
OS_STDERR_CAPTURE=${OS_STDERR_CAPTURE:-1} OS_LOG_CAPTURE=${OS_LOG_CAPTURE:-1} 
${PYTHON:-python} -m subunit.run discover -t ./ 
${OS_TEST_PATH:-./neutron_lbaas/tests/unit} --list
--- import errors ---
Failed to import test module: neutron_lbaas.tests.unit.agent.test_agent
Traceback (most recent call last):
  File 
/home/shane/work/neutron-lbaas/.tox/py27/lib/python2.7/site-packages/unittest2/loader.py,
 line 445, in _find_test_path
module = self._get_module_from_name(name)
  File 
/home/shane/work/neutron-lbaas/.tox/py27/lib/python2.7/site-packages/unittest2/loader.py,
 line 384, in _get_module_from_name
__import__(name)
  File neutron_lbaas/tests/unit/agent/test_agent.py, line 21, in module
from neutron_lbaas.tests import base
  File neutron_lbaas/tests/base.py, line 18, in module
from neutron.tests.unit.db import test_db_base_plugin_v2
ImportError: cannot import name test_db_base_plugin_v2

Failed to import test module: neutron_lbaas.tests.unit.agent.test_agent_api
Traceback (most recent call last):
  File 
/home/shane/work/neutron-lbaas/.tox/py27/lib/python2.7/site-packages/unittest2/loader.py,
 line 445, in _find_test_path
module = self._get_module_from_name(name)
  File 
/home/shane/work/neutron-lbaas/.tox/py27/lib/python2.7/site-packages/unittest2/loader.py,
 line 384, in _get_module_from_name
__import__(name)
  File neutron_lbaas/tests/unit/agent/test_agent_api.py, line 21, in module
from neutron_lbaas.tests import base
  File neutron_lbaas/tests/base.py, line 18, in module
from neutron.tests.unit.db import test_db_base_plugin_v2
ImportError: cannot import name test_db_base_plugin_v2

Failed to import test module: neutron_lbaas.tests.unit.agent.test_agent_manager
Traceback (most recent call last):
  File 
/home/shane/work/neutron-lbaas/.tox/py27/lib/python2.7/site-packages/unittest2/loader.py,
 line 445, in _find_test_path
module = self._get_module_from_name(name)
  File 
/home/shane/work/neutron-lbaas/.tox/py27/lib/python2.7/site-packages/unittest2/loader.py,
 line 384, in _get_module_from_name
__import__(name)
  File neutron_lbaas/tests/unit/agent/test_agent_manager.py, line 24, in 
module
from neutron_lbaas.tests import base
  File neutron_lbaas/tests/base.py, line 18, in module
from neutron.tests.unit.db import test_db_base_plugin_v2
ImportError: cannot import name test_db_base_plugin_v2

Failed to import test module: 
neutron_lbaas.tests.unit.common.cert_manager.test_barbican
Traceback (most recent call last):
  File 
/home/shane/work/neutron-lbaas/.tox/py27/lib/python2.7/site-packages/unittest2/loader.py,
 line 445, in _find_test_path
module = self._get_module_from_name(name)
  File 
/home/shane/work/neutron-lbaas/.tox/py27/lib/python2.7/site-packages/unittest2/loader.py,
 line 384, in _get_module_from_name
__import__(name)
  File neutron_lbaas/tests/unit/common/cert_manager/test_barbican.py, line 
26, in module
from neutron_lbaas.tests import base
  File neutron_lbaas/tests/base.py, line 18, in module
from neutron.tests.unit.db import test_db_base_plugin_v2
ImportError: cannot import name test_db_base_plugin_v2

Failed to import test module: 
neutron_lbaas.tests.unit.common.cert_manager.test_local
Traceback (most recent call last):
  File 
/home/shane/work/neutron-lbaas/.tox/py27/lib/python2.7/site-packages/unittest2/loader.py,
 line 445, in _find_test_path
module = self._get_module_from_name(name)
  File 
/home/shane/work/neutron-lbaas/.tox/py27/lib/python2.7/site

Re: [openstack-dev] [third-party][infra] Third-Party CI Operators: Let's use a common CI Solution!

[Lenny Verkhovsky]

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)
Subject: Re: [openstack-dev] [third-party][infra] Third-Party CI Operators: 
Let's use a common CI Solution!

Hello Ramy

Take me in account ☺
We used puppet modules located in system-config to install zuul and nodepool. 
Also there were a lot manual configuration.
Maybe someday  there will be a “green button” to set it up in moment.

Thanks!

From: Asselin, Ramy [mailto:ramy.asse...@hp.com]
Sent: Monday, April 20, 2015 8:17 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: [openstack-dev] [third-party][infra] Third-Party CI Operators: Let's 
use a common CI Solution!

All Third-Party CI operators:

We’ve got 85 Third Party CI systems registered in the wiki[1], all of them 
running a variety of closed  open-source solutions.
Instead of individually maintaining all those similar solutions, let’s join 
together and collectively maintain a single solution.

If that sounds good to you, there’s an Infra-spec that’s been approved [2] to 
refactor much of what the Infrastructure team uses for the upstream “Jenkins” 
CI to be more easily reusable by many of us.

We’ve got stories defined [3], and a few patches submitted. We’re using the 
gerrit-topic “downstream-puppet” [4].

For example, we’ve got the first part under review for the “Log Server”, which 
creates your own version of http://logs.openstack.org/

If anyone is interested in migrating towards a common solution, reply, or ping 
me IRC (asselin) on Freenode #openstack-infra, or join some of the third party 
ci meetings [5].

Thanks!
Ramy

[1] https://wiki.openstack.org/wiki/ThirdPartySystems
[2] 
http://specs.openstack.org/openstack-infra/infra-specs/specs/openstackci.html
[3] https://storyboard.openstack.org/#!/story/2000101
[4] https://review.openstack.org/#/q/topic:downstream-puppet,n,z
[5] 
https://wiki.openstack.org/wiki/Meetings/ThirdParty#Weekly_Third_Party_meetings


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] Mellanox request for permission for Nova CI

[Lenny Verkhovsky]

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: Michael Still [mailto:mi...@stillhq.com] 
Sent: Wednesday, April 01, 2015 11:57 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] Mellanox request for permission for Nova CI

This looks good to me, but it would be interesting to see what Sean or Matt 
thought.

Michael

On Thu, Apr 2, 2015 at 3:25 AM, Joe Gordon joe.gord...@gmail.com wrote:


 On Wed, Apr 1, 2015 at 8:28 AM, Lenny Verkhovsky len...@mellanox.com
 wrote:



 Hi all,



 We had some issues with presentation of the logs, now it looks ok.



 You can see Nova CI logs here
 http://144.76.193.39/ci-artifacts/Check-MLNX-Nova-ML2-Sriov-driver_20
 150401_1102/

 Tempest output is
 http://144.76.193.39/ci-artifacts/Check-MLNX-Nova-ML2-Sriov-driver_20
 150401_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.


 Thanks, that looks a lot better. I would like to get a second opinion 
 from another nova-core but this looks like enough to start commenting 
 on nova patches.








 Lenny Verkhovsky

 SW Engineer,  Mellanox Technologies

 www.mellanox.com



 Office:+972 74 712 9244

 Mobile:  +972 54 554 0233

 Fax:+972 72 257 9400



 From: Joe Gordon [mailto:joe.gord...@gmail.com]
 Sent: Thursday, March 26, 2015 3:29 PM


 To: OpenStack Development Mailing List (not for usage questions)
 Subject: Re: [openstack-dev] Mellanox request for permission for Nova 
 CI





 On Thu, Mar 19, 2015 at 5:52 AM, Nurit Vilosny nur...@mellanox.com
 wrote:

 Hi Joe,

 Sorry for the late response.

 Here are some latest logs for the Nova CI:


 http://144.76.193.39/ci-artifacts/Check-MLNX-Nova-ML2-Sriov-driver_20
 150318_1650/


 http://144.76.193.39/ci-artifacts/Check-MLNX-Nova-ML2-Sriov-driver_20
 150318_1506/


 http://144.76.193.39/ci-artifacts/37/165437/1/check-nova/Check-MLNX-N
 ova-ML2-Sriov-driver/e90a677/


 http://144.76.193.39/ci-artifacts/Check-MLNX-Nova-ML2-Sriov-driver_20
 150318_1851/





 I couldn't find the equivalent of:
 http://logs.openstack.org/68/135768/9/check/check-tempest-dsvm-full/f
 6c95de/logs/testr_results.html.gz



 Also what tests are running and how do they actually check if sriov works?



 I can provide more if needed.



 Thanks,

 Nurit.



 From: Joe Gordon [mailto:joe.gord...@gmail.com]
 Sent: Wednesday, March 11, 2015 7:50 PM
 To: OpenStack Development Mailing List (not for usage questions)
 Subject: Re: [openstack-dev] Mellanox request for permission for Nova 
 CI







 On Wed, Mar 11, 2015 at 12:49 AM, Nurit Vilosny nur...@mellanox.com
 wrote:

 Hi ,

 I would like to ask for a CI permission to start commenting on Nova 
 branch.

 Mellanox is engaged in pci pass-through features for quite some time now.

 We have an operating Neutron CI for  ~2 years, and since the pci 
 pass-through features are part of Nova as well, we would like to 
 start monitoring Nova’s patches.

 Our CI had been silently running locally over the past couple of 
 weeks, and I would like to step ahead, and start commenting in a non-voting 
 mode.

 During this period we will be closely monitor our systems and be 
 ready to solve any problem that might occur.



 Do you have a link to the output of your testing system, so we can 
 check what its testing etc.





 Thanks,

 Nurit Vilosny

 SW Cloud Solutions Manager



 Mellanox Technologies

 13 Zarchin St. Raanana, Israel

 Office: 972-74-712-9410

 Cell: 972-54-4713000

 Fax: 972-74-712-9111






 _
 _ OpenStack Development Mailing List (not for usage questions)
 Unsubscribe: 
 openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev




 _
 _ OpenStack Development Mailing List (not for usage questions)
 Unsubscribe: 
 openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev




 _
 _ OpenStack Development Mailing List (not for usage questions)
 Unsubscribe: 
 openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



 __
  OpenStack Development Mailing List (not for usage questions)
 Unsubscribe: 
 openstack-dev-requ...@lists.openstack.org

Re: [openstack-dev] Mellanox request for permission for Nova CI

[Lenny Verkhovsky]

Hi all,

We had some issues with presentation of the logs, now it looks ok.

You can see Nova CI logs here 
http://144.76.193.39/ci-artifacts/Check-MLNX-Nova-ML2-Sriov-driver_20150401_1102/
Tempest output is 
http://144.76.193.39/ci-artifacts/Check-MLNX-Nova-ML2-Sriov-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 Verkhovsky
SW Engineer,  Mellanox Technologies
www.mellanox.comhttp://www.mellanox.com

Office:+972 74 712 9244
Mobile:  +972 54 554 0233
Fax:+972 72 257 9400

From: Joe Gordon [mailto:joe.gord...@gmail.com]
Sent: Thursday, March 26, 2015 3:29 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] Mellanox request for permission for Nova CI


On Thu, Mar 19, 2015 at 5:52 AM, Nurit Vilosny 
nur...@mellanox.commailto:nur...@mellanox.com wrote:
Hi Joe,
Sorry for the late response.
Here are some latest logs for the Nova CI:
http://144.76.193.39/ci-artifacts/Check-MLNX-Nova-ML2-Sriov-driver_20150318_1650/
http://144.76.193.39/ci-artifacts/Check-MLNX-Nova-ML2-Sriov-driver_20150318_1506/
http://144.76.193.39/ci-artifacts/37/165437/1/check-nova/Check-MLNX-Nova-ML2-Sriov-driver/e90a677/
http://144.76.193.39/ci-artifacts/Check-MLNX-Nova-ML2-Sriov-driver_20150318_1851/


I couldn't find the equivalent of: 
http://logs.openstack.org/68/135768/9/check/check-tempest-dsvm-full/f6c95de/logs/testr_results.html.gz

Also what tests are running and how do they actually check if sriov works?

I can provide more if needed.

Thanks,
Nurit.

From: Joe Gordon [mailto:joe.gord...@gmail.commailto:joe.gord...@gmail.com]
Sent: Wednesday, March 11, 2015 7:50 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] Mellanox request for permission for Nova CI



On Wed, Mar 11, 2015 at 12:49 AM, Nurit Vilosny 
nur...@mellanox.commailto:nur...@mellanox.com wrote:
Hi ,
I would like to ask for a CI permission to start commenting on Nova branch.
Mellanox is engaged in pci pass-through features for quite some time now.
We have an operating Neutron CI for  ~2 years, and since the pci pass-through 
features are part of Nova as well, we would like to start monitoring Nova’s 
patches.
Our CI had been silently running locally over the past couple of weeks, and I 
would like to step ahead, and start commenting in a non-voting mode.
During this period we will be closely monitor our systems and be ready to solve 
any problem that might occur.

Do you have a link to the output of your testing system, so we can check what 
its testing etc.


Thanks,
Nurit Vilosny
SW Cloud Solutions Manager

Mellanox Technologies
13 Zarchin St. Raanana, Israel
Office: 972-74-712-9410
Cell: 972-54-4713000
Fax: 972-74-712-9111



__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: 
openstack-dev-requ...@lists.openstack.org?subject:unsubscribehttp://openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: 
openstack-dev-requ...@lists.openstack.org?subject:unsubscribehttp://openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] Cinder Third-Party CI: adding Mellanox CI to Wiki

[Lenny Verkhovsky]

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/Mellanox_Cinder_CI

Thanks.
Lenny Verkhovsky
SW Engineer,  Mellanox Technologies
www.mellanox.comhttp://www.mellanox.com

Office:+972 74 712 9244
Mobile:  +972 54 554 0233
Fax:+972 72 257 9400
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] Cinder Third-Party CI: adding Mellanox CI to Wiki

[Lenny Verkhovsky]

Thanks, done,
I thought it need’s community approval.
Have a great day…


Lenny Verkhovsky
SW Engineer,  Mellanox Technologies
www.mellanox.comhttp://www.mellanox.com

Office:+972 74 712 9244
Mobile:  +972 54 554 0233
Fax:+972 72 257 9400

From: Deepak Shetty [mailto:dpkshe...@gmail.com]
Sent: Wednesday, March 25, 2015 9:22 AM
To: OpenStack Development Mailing List (not for usage questions)
Cc: Murad Awawdeh
Subject: Re: [openstack-dev] Cinder Third-Party CI: adding Mellanox CI to Wiki



On Wed, Mar 25, 2015 at 12:41 PM, Lenny Verkhovsky 
len...@mellanox.commailto:len...@mellanox.com wrote:
Hi All,
Please add Mellanox Cinder CI to this page
https://wiki.openstack.org/wiki/Cinder/third-party-ci-status

Lenny,
  You should be able to edit and add this yourself, once you login with your ID 
on that page
thanx,
deepak


Driver name: iSER-LIO, iSER-ISCSI
Contact: Lenny Verkhovsky cinder...@mellanox.commailto:cinder...@mellanox.com
Status: voting and reporting
Issues: none

Reference https://wiki.openstack.org/wiki/ThirdPartySystems/Mellanox_Cinder_CI

Thanks.
Lenny Verkhovsky
SW Engineer,  Mellanox Technologies
www.mellanox.comhttp://www.mellanox.com

Office:+972 74 712 9244
Mobile:  +972 54 554 0233
Fax:+972 72 257 9400

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: 
openstack-dev-requ...@lists.openstack.org?subject:unsubscribehttp://openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev