[Yahoo-eng-team] [Bug 1688556] Re: devstack breaks on neutron setup
reinstalled ubuntu (brand new VM) and problem disappeared. No idea what
was wrong but I'm past this now.
** Changed in: neutron
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1688556
Title:
devstack breaks on neutron setup
Status in neutron:
Invalid
Bug description:
Brand new tree, 2017-05-05, devstack breaks with a dependency
inconsistency in python-neutronclient.
See file attached for devstack output.
Obtaining file:///opt/stack/python-neutronclient
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 = get_provider(dist)
File
"/usr/local/lib/python2.7/dist-packages/pip/_vendor/pkg_resources/__init__.py",
line 432, in get_provider
return working_set.find(moduleOrReq) or require(str(moduleOrReq))[0]
File
"/usr/local/lib/python2.7/dist-packages/pip/_vendor/pkg_resources/__init__.py",
line 968, in require
needed = self.resolve(parse_requirements(requirements))
File
"/usr/local/lib/python2.7/dist-packages/pip/_vendor/pkg_resources/__init__.py",
line 859, in resolve
raise VersionConflict(dist, req).with_context(dependent_req)
ContextualVersionConflict: (keystoneauth1 2.19.0
(/usr/local/lib/python2.7/dist-packages),
Requirement.parse('keystoneauth1>=2.20.0'), set(['python-neutronclient']))
+inc/python:pip_install:1 exit_trap
+./stack.sh:exit_trap:492 local r=2
++./stack.sh:exit_trap:493 jobs -p
+./stack.sh:exit_trap:493 jobs=
+./stack.sh:exit_trap:496 [[ -n '' ]]
+./stack.sh:exit_trap:502 kill_spinner
+./stack.sh:kill_spinner:388 '[' '!' -z '' ']'
+./stack.sh:exit_trap:504 [[ 2 -ne 0 ]]
+./stack.sh:exit_trap:505 echo 'Error on exit'
Error on exit
+./stack.sh:exit_trap:506 generate-subunit 1493989949 89 fail
+./stack.sh:exit_trap:507 [[ -z /opt/stack/logs ]]
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1688556/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1688556] [NEW] devstack breaks on neutron setup
Public bug reported:
Brand new tree, 2017-05-05, devstack breaks with a dependency
inconsistency in python-neutronclient.
See file attached for devstack output.
Obtaining file:///opt/stack/python-neutronclient
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 = get_provider(dist)
File
"/usr/local/lib/python2.7/dist-packages/pip/_vendor/pkg_resources/__init__.py",
line 432, in get_provider
return working_set.find(moduleOrReq) or require(str(moduleOrReq))[0]
File
"/usr/local/lib/python2.7/dist-packages/pip/_vendor/pkg_resources/__init__.py",
line 968, in require
needed = self.resolve(parse_requirements(requirements))
File
"/usr/local/lib/python2.7/dist-packages/pip/_vendor/pkg_resources/__init__.py",
line 859, in resolve
raise VersionConflict(dist, req).with_context(dependent_req)
ContextualVersionConflict: (keystoneauth1 2.19.0
(/usr/local/lib/python2.7/dist-packages),
Requirement.parse('keystoneauth1>=2.20.0'), set(['python-neutronclient']))
+inc/python:pip_install:1 exit_trap
+./stack.sh:exit_trap:492 local r=2
++./stack.sh:exit_trap:493 jobs -p
+./stack.sh:exit_trap:493 jobs=
+./stack.sh:exit_trap:496 [[ -n '' ]]
+./stack.sh:exit_trap:502 kill_spinner
+./stack.sh:kill_spinner:388 '[' '!' -z '' ']'
+./stack.sh:exit_trap:504 [[ 2 -ne 0 ]]
+./stack.sh:exit_trap:505 echo 'Error on exit'
Error on exit
+./stack.sh:exit_trap:506 generate-subunit 1493989949 89 fail
+./stack.sh:exit_trap:507 [[ -z /opt/stack/logs ]]
** Affects: neutron
Importance: Undecided
Status: New
** Attachment added: "neutron.txt"
https://bugs.launchpad.net/bugs/1688556/+attachment/4872295/+files/neutron.txt
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1688556
Title:
devstack breaks on neutron setup
Status in neutron:
New
Bug description:
Brand new tree, 2017-05-05, devstack breaks with a dependency
inconsistency in python-neutronclient.
See file attached for devstack output.
Obtaining file:///opt/stack/python-neutronclient
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 = get_provider(dist)
File
"/usr/local/lib/python2.7/dist-packages/pip/_vendor/pkg_resources/__init__.py",
line 432, in get_provider
return working_set.find(moduleOrReq) or require(str(moduleOrReq))[0]
File
"/usr/local/lib/python2.7/dist-packages/pip/_vendor/pkg_resources/__init__.py",
line 968, in require
needed = self.resolve(parse_requirements(requirements))
File
"/usr/local/lib/python2.7/dist-packages/pip/_vendor/pkg_resources/__init__.py",
line 859, in resolve
raise VersionConflict(dist, req).with_context(dependent_req)
ContextualVersionConflict: (keystoneauth1 2.19.0
(/usr/local/lib/python2.7/dist-packages),
Requirement.parse('keystoneauth1>=2.20.0'), set(['python-neutronclient']))
+inc/python:pip_install:1 exit_trap
+./stack.sh:exit_trap:492
[Yahoo-eng-team] [Bug 1652511] [NEW] enabling nova-lxd plugin breaks devstack
Public bug reported: I enabled nova-lxd plugin in my devstack environment, like so ... # Enable LXD for container virtualization enable_plugin nova-lxd http://git.openstack.org/openstack/nova-lxd.git devstack fails as below. Very reproducible. This is on tip of master as of 12/25/16. 2016-12-25 08:12:58.930 INFO migrate.versioning.api [req-8a919e4c-893b-4602-9fe1-76ceb2727827 None None] done No hosts found to map to cell, exiting. Error on exit World dumping... see /opt/stack/logs/worlddump-2016-12-25-131259.txt for details ** Affects: nova Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1652511 Title: enabling nova-lxd plugin breaks devstack Status in OpenStack Compute (nova): New Bug description: I enabled nova-lxd plugin in my devstack environment, like so ... # Enable LXD for container virtualization enable_plugin nova-lxd http://git.openstack.org/openstack/nova-lxd.git devstack fails as below. Very reproducible. This is on tip of master as of 12/25/16. 2016-12-25 08:12:58.930 INFO migrate.versioning.api [req-8a919e4c-893b-4602-9fe1-76ceb2727827 None None] done No hosts found to map to cell, exiting. Error on exit World dumping... see /opt/stack/logs/worlddump-2016-12-25-131259.txt for details To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1652511/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1323975] Re: do not use default=None for config options
** No longer affects: trove -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1323975 Title: do not use default=None for config options Status in Aodh: Fix Released Status in Barbican: Fix Released Status in castellan: Fix Released Status in Ceilometer: Fix Released Status in Cinder: Fix Released Status in congress: Fix Released Status in Designate: Fix Released Status in Freezer: New Status in Glance: Fix Released Status in glance_store: Fix Released Status in Gnocchi: Fix Released Status in heat: Fix Released Status in OpenStack Identity (keystone): Fix Released Status in Magnum: Fix Released Status in Manila: Fix Released Status in Mistral: Fix Released Status in Murano: Fix Released Status in neutron: Fix Released Status in OpenStack Compute (nova): Fix Released Status in oslo-incubator: Fix Released Status in oslo.messaging: Fix Released Status in Rally: Fix Released Status in Sahara: Fix Released Status in zaqar: Fix Released Bug description: In the cfg module default=None is set as the default value. It's not necessary to set it again when defining config options. To manage notifications about this bug go to: https://bugs.launchpad.net/aodh/+bug/1323975/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1629133] Re: New neutron subnet pool support breaks multinode testing.
** Also affects: trove Importance: Undecided Status: New ** Changed in: trove Status: New => In Progress -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1629133 Title: New neutron subnet pool support breaks multinode testing. Status in networking-bgpvpn: New Status in devstack: Fix Released Status in Ironic: Fix Committed Status in ironic-python-agent: Confirmed Status in Magnum: In Progress Status in Manila: New Status in neutron: Incomplete Status in OpenStack DBaaS (Trove): In Progress Bug description: The new subnet pool support in devstack breaks multinode testing bceause it results in the route for 10.0.0.0/8 being set to via br-ex when the host has interfaces that are actually on 10 nets and that is where we need the routes to go out. Multinode testing is affected because it uses these 10 net addresses to run the vxlan overlays between hosts. For many years devstack-gate has set FIXED_RANGE to ensure that the networks devstack uses do not interfere with the underlying test host's networking. However this setting was completely ignored when setting up the subnet pools. I think the correct way to fix this is to use a much smaller subnet pool range to avoid conflicting with every possible 10.0.0.0/8 network in the wild, possibly by defaulting to the existing FIXED_RANGE information. Using the existing information will help ensure that anyone with networks in 10.0.0.0/8 will continue to work if they have specified a range that doesn't conflict using this variable. In addition to this we need to clearly document what this new stuff in devstack does and how people can work around it should they conflict with the new defaults we end up choosing. I have proposed https://review.openstack.org/379543 which mostly works except it fails one tempest test that apparently depends on this new subnet pool stuff. Specifically the V6 range isn't large enough aiui. To manage notifications about this bug go to: https://bugs.launchpad.net/bgpvpn/+bug/1629133/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1082248] Re: Use uuidutils instead of uuid.uuid4()
** No longer affects: trove -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1082248 Title: Use uuidutils instead of uuid.uuid4() Status in Cinder: New Status in OpenStack Dashboard (Horizon): In Progress Status in Ironic: Fix Released Status in ironic-python-agent: In Progress Status in OpenStack Identity (keystone): New Status in kuryr: In Progress Status in kuryr-libnetwork: In Progress Status in Magnum: New Status in Mistral: Invalid Status in Murano: New Status in networking-ovn: In Progress Status in neutron: Fix Released Status in OpenStack Compute (nova): In Progress Status in Sahara: Fix Released Status in senlin: In Progress Status in tacker: In Progress Bug description: Openstack common has a wrapper for generating uuids. We should only use that function when generating uuids for consistency. To manage notifications about this bug go to: https://bugs.launchpad.net/cinder/+bug/1082248/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1629726] Re: recompiled pycparser 2.14 breaks Cinder db sync and Nova UTs
** Also affects: trove Importance: Undecided Status: New ** Changed in: trove Importance: Undecided => Critical ** Changed in: trove Status: New => Confirmed -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1629726 Title: recompiled pycparser 2.14 breaks Cinder db sync and Nova UTs Status in Cinder: Confirmed Status in heat: Confirmed Status in Ironic: Confirmed Status in Manila: Confirmed Status in OpenStack Compute (nova): Confirmed Status in OpenStack DBaaS (Trove): Confirmed Bug description: http://logs.openstack.org/76/380876/1/check/gate-grenade-dsvm-ubuntu- xenial/3d5e102/logs/grenade.sh.txt.gz#_2016-10-02_23_32_34_069 2016-10-02 23:32:34.069 | + lib/cinder:init_cinder:421 : /usr/local/bin/cinder-manage --config-file /etc/cinder/cinder.conf db sync 2016-10-02 23:32:34.691 | Traceback (most recent call last): 2016-10-02 23:32:34.691 | File "/usr/local/bin/cinder-manage", line 6, in 2016-10-02 23:32:34.691 | from cinder.cmd.manage import main 2016-10-02 23:32:34.691 | File "/opt/stack/old/cinder/cinder/cmd/manage.py", line 77, in 2016-10-02 23:32:34.691 | from cinder import db 2016-10-02 23:32:34.691 | File "/opt/stack/old/cinder/cinder/db/__init__.py", line 20, in 2016-10-02 23:32:34.691 | from cinder.db.api import * # noqa 2016-10-02 23:32:34.691 | File "/opt/stack/old/cinder/cinder/db/api.py", line 43, in 2016-10-02 23:32:34.691 | from cinder.api import common 2016-10-02 23:32:34.691 | File "/opt/stack/old/cinder/cinder/api/common.py", line 30, in 2016-10-02 23:32:34.691 | from cinder import utils 2016-10-02 23:32:34.691 | File "/opt/stack/old/cinder/cinder/utils.py", line 40, in 2016-10-02 23:32:34.691 | from os_brick import encryptors 2016-10-02 23:32:34.691 | File "/usr/local/lib/python2.7/dist-packages/os_brick/encryptors/__init__.py", line 16, in 2016-10-02 23:32:34.691 | from os_brick.encryptors import nop 2016-10-02 23:32:34.691 | File "/usr/local/lib/python2.7/dist-packages/os_brick/encryptors/nop.py", line 16, in 2016-10-02 23:32:34.691 | from os_brick.encryptors import base 2016-10-02 23:32:34.691 | File "/usr/local/lib/python2.7/dist-packages/os_brick/encryptors/base.py", line 19, in 2016-10-02 23:32:34.691 | from os_brick import executor 2016-10-02 23:32:34.691 | File "/usr/local/lib/python2.7/dist-packages/os_brick/executor.py", line 21, in 2016-10-02 23:32:34.691 | from os_brick.privileged import rootwrap as priv_rootwrap 2016-10-02 23:32:34.691 | File "/usr/local/lib/python2.7/dist-packages/os_brick/privileged/__init__.py", line 13, in 2016-10-02 23:32:34.691 | from oslo_privsep import capabilities as c 2016-10-02 23:32:34.691 | File "/usr/local/lib/python2.7/dist-packages/oslo_privsep/capabilities.py", line 73, in 2016-10-02 23:32:34.691 | ffi.cdef(CDEF) 2016-10-02 23:32:34.692 | File "/usr/local/lib/python2.7/dist-packages/cffi/api.py", line 105, in cdef 2016-10-02 23:32:34.692 | self._cdef(csource, override=override, packed=packed) 2016-10-02 23:32:34.692 | File "/usr/local/lib/python2.7/dist-packages/cffi/api.py", line 119, in _cdef 2016-10-02 23:32:34.692 | self._parser.parse(csource, override=override, **options) 2016-10-02 23:32:34.692 | File "/usr/local/lib/python2.7/dist-packages/cffi/cparser.py", line 299, in parse 2016-10-02 23:32:34.692 | self._internal_parse(csource) 2016-10-02 23:32:34.692 | File "/usr/local/lib/python2.7/dist-packages/cffi/cparser.py", line 304, in _internal_parse 2016-10-02 23:32:34.692 | ast, macros, csource = self._parse(csource) 2016-10-02 23:32:34.692 | File "/usr/local/lib/python2.7/dist-packages/cffi/cparser.py", line 260, in _parse 2016-10-02 23:32:34.692 | ast = _get_parser().parse(csource) 2016-10-02 23:32:34.692 | File "/usr/local/lib/python2.7/dist-packages/cffi/cparser.py", line 40, in _get_parser 2016-10-02 23:32:34.692 | _parser_cache = pycparser.CParser() 2016-10-02 23:32:34.692 | File "/usr/local/lib/python2.7/dist-packages/pycparser/c_parser.py", line 87, in __init__ 2016-10-02 23:32:34.692 | outputdir=taboutputdir) 2016-10-02 23:32:34.692 | File "/usr/local/lib/python2.7/dist-packages/pycparser/c_lexer.py", line 66, in build 2016-10-02 23:32:34.692 | self.lexer = lex.lex(object=self, **kwargs) 2016-10-02 23:32:34.692 | File "/usr/local/lib/python2.7/dist-packages/pycparser/ply/lex.py", line 911, in lex 2016-10-02 23:32:34.692 | lexobj.readtab(lextab, ldict) 2016-10-02 23:32:34.692 | File "/usr/local/lib/python2.7/dist-packages/pycparser/ply/lex.py", line 233, in readtab 2016-10-02 23:32:34.692 | titem.append((re.compile(pat, lextab._lexreflags | re.VERBOSE),
[Yahoo-eng-team] [Bug 1614361] Re: tox.ini needs to be updated as openstack infra now supports upper constraints
This is no longer a bug in Trove. ** Changed in: trove Status: In Progress => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1614361 Title: tox.ini needs to be updated as openstack infra now supports upper constraints Status in Cinder: In Progress Status in Designate: Fix Released Status in Glance: In Progress Status in heat: In Progress Status in OpenStack Dashboard (Horizon): In Progress Status in Ironic Inspector: Fix Released Status in Mistral: Fix Released Status in Murano: Fix Released Status in networking-ovn: Invalid Status in octavia: In Progress Status in python-muranoclient: Fix Released Status in tacker: In Progress Status in OpenStack DBaaS (Trove): Invalid Status in vmware-nsx: In Progress Status in zaqar: Fix Released Status in Zaqar-ui: Fix Released Bug description: Openstack infra now supports upper constraints for releasenotes, cover, venv targets. tox.ini uses install_command for these targets, which can now be safely removed. Reference for mail that details this support: http://lists.openstack.org/pipermail/openstack-dev/2016-August/101474.html To manage notifications about this bug go to: https://bugs.launchpad.net/cinder/+bug/1614361/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1600109] Re: Unit tests should not perform logging, but some tests still use
This is not a bug (in Trove). ** Changed in: trove Status: Incomplete => Invalid ** Changed in: trove Assignee: haobing1 (haobing1) => (unassigned) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1600109 Title: Unit tests should not perform logging,but some tests still use Status in Ceilometer: Incomplete Status in Cinder: Incomplete Status in Glance: Incomplete Status in OpenStack Identity (keystone): Won't Fix Status in Magnum: Incomplete Status in OpenStack Compute (nova): Invalid Status in python-cinderclient: Incomplete Status in python-glanceclient: Incomplete Status in python-keystoneclient: Won't Fix Status in python-neutronclient: Incomplete Status in python-novaclient: Invalid Status in python-rackclient: Incomplete Status in python-swiftclient: Incomplete Status in rack: Incomplete Status in OpenStack Object Storage (swift): Incomplete Status in OpenStack DBaaS (Trove): Invalid Bug description: We shuld remove the logging To manage notifications about this bug go to: https://bugs.launchpad.net/ceilometer/+bug/1600109/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1602373] Re: nova cloud-init doesn't always land files that one expects
** Project changed: nova => cloud-init
** Summary changed:
- nova cloud-init doesn't always land files that one expects
+ cloud-init doesn't always land files that one expects
** Description changed:
Trove launches instances using the servers.create() API with some files.
Trove provides a dictionary of files that it wants on the instance and
- most of the time this works.
+ most of the time this works. Nova passes them to the launched VM as
+ metadata on config drive.
- Sometimes though, it doesn't. With some help from jroll and mriedem, I
- gathered the following information.
+ Sometimes though, it doesn't.
When injection fails, I see a cloud-init.log that looks like this:
https://gist.github.com/amrith/7566d8fef4b6e813cca77e5e3b1f1d5a
When injection succeeds, I see a cloud-init.log that looks like this:
https://gist.github.com/amrith/50d9e3050d88ec51e13b0a510bd718c3
Observe that the one that succeeds properly injects three files:
/etc/injected_files (which is something I added just for debugging)
/etc/trove/conf.d/... two files here ...
On a machine where this injection failed:
root@m10:/tmp/zz/openstack/content# ls -l /etc/trove
total 4
drwxr-xr-x 2 amrith root 4096 Jul 12 16:55 conf.d
root@m10:/tmp/zz/openstack/content# ls -l /etc/trove/conf.d/
total 4
root@m10:/tmp/zz/openstack/content#
Clearly, no files made it over. Yet, the files are definitely there on
the config drive ...
I've mounted the config drive.
root@m10:/tmp/zz/openstack/content# mount | grep zz
/dev/sr0 on /tmp/zz type iso9660 (ro,relatime)
root@m10:/tmp/zz/openstack/content# cd /tmp/zz
root@m10:/tmp/zz# find .
.
./ec2
./ec2/2009-04-04
./ec2/2009-04-04/meta-data.json
./ec2/latest
./ec2/latest/meta-data.json
./openstack
./openstack/2012-08-10
./openstack/2012-08-10/meta_data.json
./openstack/2013-04-04
./openstack/2013-04-04/meta_data.json
./openstack/2013-10-17
./openstack/2013-10-17/meta_data.json
./openstack/2013-10-17/vendor_data.json
./openstack/2015-10-15
./openstack/2015-10-15/meta_data.json
./openstack/2015-10-15/network_data.json
./openstack/2015-10-15/vendor_data.json
./openstack/2016-06-30
./openstack/2016-06-30/meta_data.json
./openstack/2016-06-30/network_data.json
./openstack/2016-06-30/vendor_data.json
./openstack/content
./openstack/content/
./openstack/content/0001
./openstack/content/0002
./openstack/latest
./openstack/latest/meta_data.json
./openstack/latest/network_data.json
./openstack/latest/vendor_data.json
-
root@m10:/tmp/zz# cd openstack/latest/
root@m10:/tmp/zz/openstack/latest# cat meta_data.json
{"files": [{"path": "/etc/injected_files", "content_path": "/content/"},
{"path": "/etc/trove/conf.d/guest_info.conf", "content_path": "/content/0001"},
{"path": "/etc/trove/conf.d/trove-guestagent.conf", "content_path":
"/content/0002"}], "admin_pass": "pf2ng7tT8JSt", "random_seed":
"uSNqQ3udiKspue4y8R8b4gg33Qe6klYYJa8ebvDS0t4i88rq2Owu4yC8TysAfsmsYpno0rbWpWisiTQ3raAOPsx+kGgkrunM9UR5khs/1XRh60tlpKJVIHZnKpLv4PcisLKL2DDoHaaFLV9lPcVtZi3iTqKu6RhcwFyhh+A0mD0xg2G89qACD/RNhWiAuQs4X8le+qgIeoRb3wwg7+4dpujLiqKyx7edDgs9zaEsng21YxO0kv47PiwQf7GoIXObR3xtBYClQQfWQ8a1o35gpDPkPSowqHNKJIxFnIrdFgVHBK5EFTAmwN2JY/GcLwQxLydK02+aalem+bznOpsa1Jl86rNAI9pwltyFYDVz8CGwy46pNYtCOJ2W5WZ+wF4KssE0LkxeWcq7w7CXoFCgz42k13ki0gcHYHw0ieJTMULQT3k65gLwGL2/EsJrZjgil5AaCQhLBLkY2sPhHKYs0k+331QttHHs7PjoX/0as63iNiY62M10givhwyrPDaeYSOAidD0PfRpvVZVcQym/jgKmytV6ZU8DBDwAujGtHjdXK4AovcAvqc96H97arahQr/1SHk8RktyedYjqLC6iYwbSFSHTs+7Fb07MspWKQ2cJLlpmytd/lcZHYAElF/b0VBhR8/eU0dUqdpxjvfGsx8T9/rflMaM5wrDlhad/ikQ=",
"uuid": "38731f42-6
11e-465f-b3e4-1e80aa623caf", "availability_zone": "nova", "hostname":
"m10.novalocal", "launch_index": 0, "devices": [], "project_id":
"eeec3236ef004821a77ccbd26b81f18f", "name": "m10"}
root@m10:/tmp/zz/openstack/latest#
Sure enough, the files I want are in content/, 0001 and 0002
root@m10:/tmp/zz/openstack/content# ls -l
total 4
-r--r--r-- 1 root root 1329 Jul 12 16:55
-r--r--r-- 1 root root 127 Jul 12 16:55 0001
-r--r--r-- 1 root root 1050 Jul 12 16:55 0002
** Changed in: cloud-init
Status: Invalid => New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/1602373
Title:
cloud-init doesn't always land files that one expects
Status in cloud-init:
New
Bug description:
Trove launches instances using the servers.create() API with some
files. Trove provides a dictionary of files that it wants on the
instance and most of the
[Yahoo-eng-team] [Bug 1602373] [NEW] cloud-init doesn't always land files that one expects
Public bug reported:
Trove launches instances using the servers.create() API with some files.
Trove provides a dictionary of files that it wants on the instance and
most of the time this works. Nova passes them to the launched VM as
metadata on config drive.
Sometimes though, it doesn't.
When injection fails, I see a cloud-init.log that looks like this:
https://gist.github.com/amrith/7566d8fef4b6e813cca77e5e3b1f1d5a
When injection succeeds, I see a cloud-init.log that looks like this:
https://gist.github.com/amrith/50d9e3050d88ec51e13b0a510bd718c3
Observe that the one that succeeds properly injects three files:
/etc/injected_files (which is something I added just for debugging)
/etc/trove/conf.d/... two files here ...
On a machine where this injection failed:
root@m10:/tmp/zz/openstack/content# ls -l /etc/trove
total 4
drwxr-xr-x 2 amrith root 4096 Jul 12 16:55 conf.d
root@m10:/tmp/zz/openstack/content# ls -l /etc/trove/conf.d/
total 4
root@m10:/tmp/zz/openstack/content#
Clearly, no files made it over. Yet, the files are definitely there on
the config drive ...
I've mounted the config drive.
root@m10:/tmp/zz/openstack/content# mount | grep zz
/dev/sr0 on /tmp/zz type iso9660 (ro,relatime)
root@m10:/tmp/zz/openstack/content# cd /tmp/zz
root@m10:/tmp/zz# find .
.
./ec2
./ec2/2009-04-04
./ec2/2009-04-04/meta-data.json
./ec2/latest
./ec2/latest/meta-data.json
./openstack
./openstack/2012-08-10
./openstack/2012-08-10/meta_data.json
./openstack/2013-04-04
./openstack/2013-04-04/meta_data.json
./openstack/2013-10-17
./openstack/2013-10-17/meta_data.json
./openstack/2013-10-17/vendor_data.json
./openstack/2015-10-15
./openstack/2015-10-15/meta_data.json
./openstack/2015-10-15/network_data.json
./openstack/2015-10-15/vendor_data.json
./openstack/2016-06-30
./openstack/2016-06-30/meta_data.json
./openstack/2016-06-30/network_data.json
./openstack/2016-06-30/vendor_data.json
./openstack/content
./openstack/content/
./openstack/content/0001
./openstack/content/0002
./openstack/latest
./openstack/latest/meta_data.json
./openstack/latest/network_data.json
./openstack/latest/vendor_data.json
root@m10:/tmp/zz# cd openstack/latest/
root@m10:/tmp/zz/openstack/latest# cat meta_data.json
{"files": [{"path": "/etc/injected_files", "content_path": "/content/"},
{"path": "/etc/trove/conf.d/guest_info.conf", "content_path": "/content/0001"},
{"path": "/etc/trove/conf.d/trove-guestagent.conf", "content_path":
"/content/0002"}], "admin_pass": "pf2ng7tT8JSt", "random_seed":
"uSNqQ3udiKspue4y8R8b4gg33Qe6klYYJa8ebvDS0t4i88rq2Owu4yC8TysAfsmsYpno0rbWpWisiTQ3raAOPsx+kGgkrunM9UR5khs/1XRh60tlpKJVIHZnKpLv4PcisLKL2DDoHaaFLV9lPcVtZi3iTqKu6RhcwFyhh+A0mD0xg2G89qACD/RNhWiAuQs4X8le+qgIeoRb3wwg7+4dpujLiqKyx7edDgs9zaEsng21YxO0kv47PiwQf7GoIXObR3xtBYClQQfWQ8a1o35gpDPkPSowqHNKJIxFnIrdFgVHBK5EFTAmwN2JY/GcLwQxLydK02+aalem+bznOpsa1Jl86rNAI9pwltyFYDVz8CGwy46pNYtCOJ2W5WZ+wF4KssE0LkxeWcq7w7CXoFCgz42k13ki0gcHYHw0ieJTMULQT3k65gLwGL2/EsJrZjgil5AaCQhLBLkY2sPhHKYs0k+331QttHHs7PjoX/0as63iNiY62M10givhwyrPDaeYSOAidD0PfRpvVZVcQym/jgKmytV6ZU8DBDwAujGtHjdXK4AovcAvqc96H97arahQr/1SHk8RktyedYjqLC6iYwbSFSHTs+7Fb07MspWKQ2cJLlpmytd/lcZHYAElF/b0VBhR8/eU0dUqdpxjvfGsx8T9/rflMaM5wrDlhad/ikQ=",
"uuid": "38731f42-611
e-465f-b3e4-1e80aa623caf", "availability_zone": "nova", "hostname":
"m10.novalocal", "launch_index": 0, "devices": [], "project_id":
"eeec3236ef004821a77ccbd26b81f18f", "name": "m10"}
root@m10:/tmp/zz/openstack/latest#
Sure enough, the files I want are in content/, 0001 and 0002
root@m10:/tmp/zz/openstack/content# ls -l
total 4
-r--r--r-- 1 root root 1329 Jul 12 16:55
-r--r--r-- 1 root root 127 Jul 12 16:55 0001
-r--r--r-- 1 root root 1050 Jul 12 16:55 0002
** Affects: cloud-init
Importance: Undecided
Status: New
** Attachment added: "this is the cloud-init log file when injection succeeds"
https://bugs.launchpad.net/bugs/1602373/+attachment/4699588/+files/50d9e3050d88ec51e13b0a510bd718c3-ef60b84e3347f585010397361b62889e146d3cae.zip
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1602373
Title:
cloud-init doesn't always land files that one expects
Status in cloud-init:
New
Bug description:
Trove launches instances using the servers.create() API with some
files. Trove provides a dictionary of files that it wants on the
instance and most of the time this works. Nova passes them to the
launched VM as metadata on config drive.
Sometimes though, it doesn't.
When injection fails, I see a cloud-init.log that looks like this:
https://gist.github.com/amrith/7566d8fef4
[Yahoo-eng-team] [Bug 1600109] Re: Unit tests should not perform logging, but some tests still use
marking incomplete for Trove per IRC chat with keystone folks. ** Changed in: trove Status: Opinion => Incomplete -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1600109 Title: Unit tests should not perform logging,but some tests still use Status in Ceilometer: Incomplete Status in Cinder: Incomplete Status in Glance: Incomplete Status in glance_store: New Status in OpenStack Identity (keystone): Incomplete Status in Magnum: Incomplete Status in neutron: New Status in OpenStack Compute (nova): Incomplete Status in os-brick: New Status in python-cinderclient: New Status in python-glanceclient: New Status in python-heatclient: New Status in python-keystoneclient: Incomplete Status in python-neutronclient: New Status in python-novaclient: New Status in python-rackclient: New Status in python-swiftclient: New Status in rack: New Status in Rally: Incomplete Status in OpenStack Object Storage (swift): Incomplete Status in tempest: New Status in OpenStack DBaaS (Trove): Incomplete Bug description: We shuld remove the logging To manage notifications about this bug go to: https://bugs.launchpad.net/ceilometer/+bug/1600109/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1600109] Re: Unit tests should not perform logging, but some tests still use
Without more details about this, it is hard to tell what this bug is about. How can code not perform logging just because it is in unit tests? Heck, some tests actually verify that messages are being logged. ** Changed in: trove Status: New => Opinion -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1600109 Title: Unit tests should not perform logging,but some tests still use Status in Ceilometer: New Status in Cinder: New Status in Glance: New Status in glance_store: New Status in OpenStack Identity (keystone): New Status in Magnum: New Status in neutron: New Status in OpenStack Compute (nova): New Status in os-brick: New Status in python-cinderclient: New Status in python-glanceclient: New Status in python-heatclient: New Status in python-keystoneclient: New Status in python-neutronclient: New Status in python-novaclient: New Status in python-rackclient: New Status in python-swiftclient: New Status in rack: New Status in Rally: New Status in OpenStack Object Storage (swift): New Status in tempest: New Status in OpenStack DBaaS (Trove): Opinion Bug description: We shuld remove the logging To manage notifications about this bug go to: https://bugs.launchpad.net/ceilometer/+bug/1600109/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1347337] Re: intermittent failures in call to execute() with exception ValueError: I/O operation on closed file
** No longer affects: cinder
** No longer affects: glance
** No longer affects: nova
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1347337
Title:
intermittent failures in call to execute() with exception ValueError:
I/O operation on closed file
Status in Oslo - a Library of Common OpenStack Code:
In Progress
Status in Openstack Database (Trove):
New
Bug description:
This happened just once, so I'm opening a tracking bug to see if we hit this
again.
The details of the run:
2014-07-22 23:41:56.663 | py27 runtests: commands[1] | python setup.py testr
--slowest
2014-07-22 23:41:57.027 | running testr
2014-07-22 23:41:59.231 | No handlers could be found for logger
trove.guestagent.backup.backupagent
2014-07-22 23:41:59.397 | No handlers could be found for logger
trove.guestagent.backup.backupagent
2014-07-22 23:41:59.906 | No handlers could be found for logger
trove.guestagent.backup.backupagent
2014-07-22 23:42:00.257 | No handlers could be found for logger
trove.conductor.manager
2014-07-22 23:42:01.015 | No handlers could be found for logger
trove.guestagent.api
2014-07-22 23:42:01.695 | No handlers could be found for logger
trove.guestagent.backup.backupagent
2014-07-22 23:42:02.514 | No handlers could be found for logger
trove.guestagent.backup.backupagent
2014-07-22 23:42:03.094 | No handlers could be found for logger
trove.guestagent.strategies.storage.swift
2014-07-22 23:42:13.834 | running=${PYTHON:-python} -m subunit.run discover
./trove/tests/unittests --list
2014-07-22 23:42:13.834 | running=${PYTHON:-python} -m subunit.run discover
./trove/tests/unittests --load-list /tmp/tmp.Ss0It4yOgb/tmpVCBlup
2014-07-22 23:42:13.834 | running=${PYTHON:-python} -m subunit.run discover
./trove/tests/unittests --load-list /tmp/tmp.Ss0It4yOgb/tmpeEa7fi
2014-07-22 23:42:13.834 | running=${PYTHON:-python} -m subunit.run discover
./trove/tests/unittests --load-list /tmp/tmp.Ss0It4yOgb/tmpEudlCu
2014-07-22 23:42:13.834 | running=${PYTHON:-python} -m subunit.run discover
./trove/tests/unittests --load-list /tmp/tmp.Ss0It4yOgb/tmpIVQ9rl
2014-07-22 23:42:13.834 | running=${PYTHON:-python} -m subunit.run discover
./trove/tests/unittests --load-list /tmp/tmp.Ss0It4yOgb/tmpROt36p
2014-07-22 23:42:13.834 | running=${PYTHON:-python} -m subunit.run discover
./trove/tests/unittests --load-list /tmp/tmp.Ss0It4yOgb/tmpmDS72J
2014-07-22 23:42:13.834 | running=${PYTHON:-python} -m subunit.run discover
./trove/tests/unittests --load-list /tmp/tmp.Ss0It4yOgb/tmpDaJo98
2014-07-22 23:42:13.834 | running=${PYTHON:-python} -m subunit.run discover
./trove/tests/unittests --load-list /tmp/tmp.Ss0It4yOgb/tmpMMzRbw
2014-07-22 23:42:13.834 |
==
2014-07-22 23:42:13.834 | FAIL:
guestagent.test_mongodb_manager.GuestAgentMongoDBManagerTest.test_prepare_from_backup
2014-07-22 23:42:13.835 | tags: worker-5
2014-07-22 23:42:13.835 |
--
2014-07-22 23:42:13.835 | Traceback (most recent call last):
2014-07-22 23:42:13.835 | File
/home/jenkins/workspace/gate-trove-python27/trove/tests/unittests/guestagent/test_mongodb_manager.py,
line 58, in test_prepare_from_backup
2014-07-22 23:42:13.835 |
self._prepare_dynamic(backup_id='backup_id_123abc')
2014-07-22 23:42:13.835 | File
/home/jenkins/workspace/gate-trove-python27/trove/tests/unittests/guestagent/test_mongodb_manager.py,
line 91, in _prepare_dynamic
2014-07-22 23:42:13.835 | backup_info=backup_info)
2014-07-22 23:42:13.835 | File
trove/guestagent/datastore/mongodb/manager.py, line 66, in prepare
2014-07-22 23:42:13.835 | operating_system.update_owner('mongodb',
'mongodb', mount_point)
2014-07-22 23:42:13.835 | File
trove/guestagent/common/operating_system.py, line 109, in update_owner
2014-07-22 23:42:13.835 | run_as_root=True, root_helper=sudo)
2014-07-22 23:42:13.836 | File trove/common/utils.py, line 278, in
execute_with_timeout
2014-07-22 23:42:13.836 | return execute(*args, **kwargs)
2014-07-22 23:42:13.836 | File trove/openstack/common/processutils.py,
line 186, in execute
2014-07-22 23:42:13.836 | result = obj.communicate()
2014-07-22 23:42:13.836 | File /usr/lib/python2.7/subprocess.py, line
799, in communicate
2014-07-22 23:42:13.836 | return self._communicate(input)
2014-07-22 23:42:13.836 | File /usr/lib/python2.7/subprocess.py, line
1396, in _communicate
2014-07-22 23:42:13.836 | self.stdin.flush()
2014-07-22 23:42:13.836 | File
/home/jenkins/workspace/gate-trove-python27/.tox/py27/local/lib/python2.7/site-packages/eventlet/greenio.py,
line 419, in _operationOnClosedFile
2014-07-22 23:42:13.836 | raise ValueError(I/O operation on
[Yahoo-eng-team] [Bug 1347337] Re: Intermittent failure in unittest: GuestAgentMongoDBManagerTest.test_prepare_from_backup
The backtrace you are likely to see will include
File path to/processutils.py, line 186, in execute
result = obj.communicate()
File /usr/lib/python2.7/subprocess.py, line 799, in communicate
return self._communicate(input)
File /usr/lib/python2.7/subprocess.py, line 1396, in _communicate
self.stdin.flush()
File
/opt/stack/trove/.tox/py27/local/lib/python2.7/site-packages/eventlet/greenio.py,
line 419, in_operationOnClosedFile
raise ValueError(I/O operation on closed file)
ValueError: I/O operation on closed file
** Also affects: nova
Importance: Undecided
Status: New
** Also affects: trove
Importance: Undecided
Status: New
** Also affects: cinder
Importance: Undecided
Status: New
** Changed in: trove
Assignee: (unassigned) = Amrith (amrith)
** Also affects: glance
Importance: Undecided
Status: New
** Also affects: neutron
Importance: Undecided
Status: New
** Summary changed:
- Intermittent failure in unittest:
GuestAgentMongoDBManagerTest.test_prepare_from_backup
+ intermittent failures in call to execute() with exception ValueError: I/O
operation on closed file
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1347337
Title:
intermittent failures in call to execute() with exception ValueError:
I/O operation on closed file
Status in Cinder:
New
Status in OpenStack Image Registry and Delivery Service (Glance):
New
Status in OpenStack Neutron (virtual network service):
New
Status in OpenStack Compute (Nova):
New
Status in Oslo - a Library of Common OpenStack Code:
In Progress
Status in Openstack Database (Trove):
New
Bug description:
This happened just once, so I'm opening a tracking bug to see if we hit this
again.
The details of the run:
2014-07-22 23:41:56.663 | py27 runtests: commands[1] | python setup.py testr
--slowest
2014-07-22 23:41:57.027 | running testr
2014-07-22 23:41:59.231 | No handlers could be found for logger
trove.guestagent.backup.backupagent
2014-07-22 23:41:59.397 | No handlers could be found for logger
trove.guestagent.backup.backupagent
2014-07-22 23:41:59.906 | No handlers could be found for logger
trove.guestagent.backup.backupagent
2014-07-22 23:42:00.257 | No handlers could be found for logger
trove.conductor.manager
2014-07-22 23:42:01.015 | No handlers could be found for logger
trove.guestagent.api
2014-07-22 23:42:01.695 | No handlers could be found for logger
trove.guestagent.backup.backupagent
2014-07-22 23:42:02.514 | No handlers could be found for logger
trove.guestagent.backup.backupagent
2014-07-22 23:42:03.094 | No handlers could be found for logger
trove.guestagent.strategies.storage.swift
2014-07-22 23:42:13.834 | running=${PYTHON:-python} -m subunit.run discover
./trove/tests/unittests --list
2014-07-22 23:42:13.834 | running=${PYTHON:-python} -m subunit.run discover
./trove/tests/unittests --load-list /tmp/tmp.Ss0It4yOgb/tmpVCBlup
2014-07-22 23:42:13.834 | running=${PYTHON:-python} -m subunit.run discover
./trove/tests/unittests --load-list /tmp/tmp.Ss0It4yOgb/tmpeEa7fi
2014-07-22 23:42:13.834 | running=${PYTHON:-python} -m subunit.run discover
./trove/tests/unittests --load-list /tmp/tmp.Ss0It4yOgb/tmpEudlCu
2014-07-22 23:42:13.834 | running=${PYTHON:-python} -m subunit.run discover
./trove/tests/unittests --load-list /tmp/tmp.Ss0It4yOgb/tmpIVQ9rl
2014-07-22 23:42:13.834 | running=${PYTHON:-python} -m subunit.run discover
./trove/tests/unittests --load-list /tmp/tmp.Ss0It4yOgb/tmpROt36p
2014-07-22 23:42:13.834 | running=${PYTHON:-python} -m subunit.run discover
./trove/tests/unittests --load-list /tmp/tmp.Ss0It4yOgb/tmpmDS72J
2014-07-22 23:42:13.834 | running=${PYTHON:-python} -m subunit.run discover
./trove/tests/unittests --load-list /tmp/tmp.Ss0It4yOgb/tmpDaJo98
2014-07-22 23:42:13.834 | running=${PYTHON:-python} -m subunit.run discover
./trove/tests/unittests --load-list /tmp/tmp.Ss0It4yOgb/tmpMMzRbw
2014-07-22 23:42:13.834 |
==
2014-07-22 23:42:13.834 | FAIL:
guestagent.test_mongodb_manager.GuestAgentMongoDBManagerTest.test_prepare_from_backup
2014-07-22 23:42:13.835 | tags: worker-5
2014-07-22 23:42:13.835 |
--
2014-07-22 23:42:13.835 | Traceback (most recent call last):
2014-07-22 23:42:13.835 | File
/home/jenkins/workspace/gate-trove-python27/trove/tests/unittests/guestagent/test_mongodb_manager.py,
line 58, in test_prepare_from_backup
2014-07-22 23:42:13.835 |
self._prepare_dynamic(backup_id='backup_id_123abc')
2014-07-22 23:42:13.835 | File
/home/jenkins/workspace/gate-trove-python27/trove/tests/unittests/guestagent/test_mongodb_manager.py,
line 91, in _prepare_dynamic
2014-07-22 23:42:13.835
