[openstack-dev] [devstack][mitaka] Unable stack.sh on ubuntu 14.04.5LTS (TypeError: 'Documentation' object is not iterable)
Hi
I am consistently getting the following error when I run stack.sh on my vagrant
VM with Ubuntu 14.04.5 OS. I tried to upgrade setuptools and distribute, but
none of them were able to solve this error. Can you plz help me how to resolve
this error. Plz let me know if u need further data here...
Thanks
Srikanth
2016-10-29 21:52:27.289 | Configuring Horizon
+./stack.sh:main:1057 configure_horizon
+lib/horizon:configure_horizon:79 setup_develop /opt/stack/horizon
+inc/python:setup_develop:271 local project_dir=/opt/stack/horizon
+inc/python:setup_develop:272 local extras=
+inc/python:setup_develop:273 _setup_package_with_constraints_edit
/opt/stack/horizon -e
+inc/python:_setup_package_with_constraints_edit:303 local
project_dir=/opt/stack/horizon
+inc/python:_setup_package_with_constraints_edit:304 local flags=-e
+inc/python:_setup_package_with_constraints_edit:305 local extras=
+inc/python:_setup_package_with_constraints_edit:307 '[' -n
/opt/stack/requirements ']'
+inc/python:_setup_package_with_constraints_edit:309 local name
++inc/python:_setup_package_with_constraints_edit:310 awk '/^name.*=/ {print
$3}' /opt/stack/horizon/setup.cfg
+inc/python:_setup_package_with_constraints_edit:310 name=horizon
+inc/python:_setup_package_with_constraints_edit:312
/opt/stack/requirements/.venv/bin/edit-constraints
/opt/stack/requirements/upper-constraints.txt -- horizon '-e
file:///opt/stack/horizon#egg=horizon'
+inc/python:_setup_package_with_constraints_edit:316 setup_package
/opt/stack/horizon -e
+inc/python:setup_package:332 local project_dir=/opt/stack/horizon
+inc/python:setup_package:333 local flags=-e
+inc/python:setup_package:334 local extras=
+inc/python:setup_package:338 [[ -n -e ]]
+inc/python:setup_package:338 [[ -z '' ]]
+inc/python:setup_package:338 [[ ! -e =~ ^-.* ]]
+inc/python:setup_package:343 [[ ! -z '' ]]
+inc/python:setup_package:347 pip_install -e /opt/stack/horizon
+inc/python:pip_install:84 local xtrace result
++inc/python:pip_install:85 set +o
++inc/python:pip_install:85 grep xtrace
+inc/python:pip_install:85 xtrace='set -o xtrace'
+inc/python:pip_install:86 set +o xtrace
+inc/python:pip_install:155sudo -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
--upgrade -e /opt/stack/horizon
Ignoring dnspython3: markers u"python_version=='3.4'" don't match your
environment
Obtaining file:///opt/stack/horizon
Obtaining horizon from file:///opt/stack/horizon#egg=horizon (from -c
/opt/stack/requirements/upper-constraints.txt (line 1))
Requirement already up-to-date: Babel===2.2.0 in
/usr/local/lib/python2.7/dist-packages (from -c
/opt/stack/requirements/upper-constraints.txt (line 3))
...
Requirement already up-to-date: python-openstackclient===2.3.0 in
/usr/local/lib/python2.7/dist-packages (from -c
/opt/stack/requirements/upper-constraints.txt (line 305))
Requirement already up-to-date: python-swiftclient===3.0.0 in
/usr/local/lib/python2.7/dist-packages (from -c
/opt/stack/requirements/upper-constraints.txt (line 313))
Requirement already up-to-date: pytz===2015.7 in
/usr/local/lib/python2.7/dist-packages (from -c
/opt/stack/requirements/upper-constraints.txt (line 316))
Collecting rcssmin===1.0.6 (from -c
/opt/stack/requirements/upper-constraints.txt (line 320))
Using cached rcssmin-1.0.6.tar.gz
Complete output from command python setup.py egg_info:
running egg_info
creating pip-egg-info/rcssmin.egg-info
writing pip-egg-info/rcssmin.egg-info/PKG-INFO
writing top-level names to pip-egg-info/rcssmin.egg-info/top_level.txt
writing dependency_links to
pip-egg-info/rcssmin.egg-info/dependency_links.txt
writing manifest file 'pip-egg-info/rcssmin.egg-info/SOURCES.txt'
warning: manifest_maker: standard file '-c' not found
Traceback (most recent call last):
File "", line 1, in
File "/tmp/pip-build-T8bWPt/rcssmin/setup.py", line 42, in
setup()
File "/tmp/pip-build-T8bWPt/rcssmin/setup.py", line 33, in setup
return run(script_args=args, ext=ext, manifest_only=_manifest)
File "_setup/py2/setup.py", line 421, in run
return _core.setup(**kwargs)
File "/usr/lib/python2.7/distutils/core.py", line 151, in setup
dist.run_commands()
File "/usr/lib/python2.7/distutils/dist.py", line 953, in run_commands
self.run_command(cmd)
File "/usr/lib/python2.7/distutils/dist.py", line 972, in run_command
cmd_obj.run()
File "build/bdist.linux-x86_64/egg/setuptools/command/egg_info.py", line
279, in run
File
[openstack-dev] [glance] Ocata design summit notes
For those who couldn't attend the Glance design sessions in Barcelona, here's a quick synopsis of what was discussed. 1. glance_store refactoring (Fishbowl) The aim of the glance_store is to present a unified interface to a variety of backend storage technologies supported by different drivers. The current interface is very image-centric and hence not as useful as it could be for projects other than Glance to consume it. At this point, the primary project other than Glance that uses glance_store is Glare. Given that it's not clear at this point whether there will be development in Glare during the Ocata cycle, we'll postpone any refactoring of glance_store in Ocata and re-consider the situation at the PTG in February 2017. Short term, we'll patch the README in the repository to provide some context to people looking at glance_store. For more details, see the session etherpad: https://etherpad.openstack.org/p/ocata-glance-glance-store-refactoring --- 2. Image Locations (Fishbowl) The ability to set image locations is required for efficient use of the rbd and cinder storage backends. "Multiple locations" enters into the picture because any use of locations is currently tied to the show_multiple_locations configuration setting (i.e., you have to allow multiple locations in order to get the functionality at all). Further, there are some clouds actually using multiple locations (as a way to fake availability zones in Glance). The show_multiple_locations option was deprecated in Newton, so can't be removed until Pike anyway. Further, we'd like to get more clarity on the use cases for image locations before more work is done on them so we can make sure we implement a robust solution. Some of the operators present took the action item to propose a user story to the Product Working Group's repository as a way to kickstart this effort. For more details, see the session etherpad: https://etherpad.openstack.org/p/ocata-glance-image-locations --- 3. Service Tokens (Work session) There was a useful cross-project session on cross-service communication that outlined some new developments in keystone that should make it easy to improve Glance's handling of tokens. Erno will monitor the keystone work and come up with an assessment of what will be required on the Glance side when that's done, and we'll see when it makes sense to schedule this. For more details, see the session etherpad: https://etherpad.openstack.org/p/ocata-glance-service-tokens --- 4. Glance Prioritization and Roadmap (Work session) The Glance priorities for Ocata are: 1 Image import 2 Community images 3 Rolling Upgrades + Zero Downtime DB migrations 4 "Community Goal" - remove incubated oslo code Other important work will be glanceclient support for the Community Images changes and glanceclient support for image import. We also discussed milestones, among those please note: week of Nov07: Glance spec proposal freeze (patch must be up) week of Nov21: Glance spec freeze (Ocata specs must be merged) Other milestones are noted on the etherpad. For more details, see the session etherpad: https://etherpad.openstack.org/p/ocata-glance-prioritization-and-roadmap __ 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] [packstack] Proposal to add Alfredo Moralejo as core reviewer
> I'd like to propose Alfredo Moralejo (amoralej in #Freenode) as a core > reviewer for Packstack. +1 With Alfredo in packstack-core, Spanish-speaking population will gain relative majority and we should totally rename it to Packistack ;) Cheers, Alan __ 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] [TripleO] Your draft logo & a sneak peek
On 27.10.2016 19:54, Ryan Brady wrote: > > How is the current draft logo expressive? What does it express to you? To me it appears like an stylized owl with a three-quarter circle as opened wings, and with lines of three nested O's. Cheers, Sven __ 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] [acceleration]Follow up action items from Ocata Design Summit
Hi Team, First of all thank you so much for attending the session and providing such animated debate and discussion. I would like to follow up some of our unfinished action items from the session. 1. Please provide your opinion on the project renaming on https://etherpad.openstack.org/p/nomad-ocata-design-session before the end of next week. Just write down +1 after your preferred name. After next Friday when we have a consensus then I could provide this as a supporting material to the infra team for the repo renaming. 2. Let's start our bi-weekly meeting on Nov 9th, for which we could all take the next week off as a summit break. 3. I will try to setup the irc channels before Nov 9th, at the mean time if you have any item you want to discuss, just shoot an email to the openstack-dev mailinglist with [acceleration] in the subject. Thank you very much and wish you all safe trip back home :) -- Zhipeng (Howard) Huang Standard Engineer IT Standard & Patent/IT Prooduct Line Huawei Technologies Co,. Ltd Email: huangzhip...@huawei.com Office: Huawei Industrial Base, Longgang, Shenzhen (Previous) Research Assistant Mobile Ad-Hoc Network Lab, Calit2 University of California, Irvine Email: zhipe...@uci.edu Office: Calit2 Building Room 2402 OpenStack, OPNFV, OpenDaylight, OpenCompute Aficionado __ 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] [neutron][fwaas] neutron-fwaas meeting time change
Hello neutron-fwaas team, With the expiration of Daylight Savings Time imminent in the USA, I would like to propose that we change the meeting time for the neutron-fwaas IRC meeting from the current value of 0400 UTC. Here are a few proposals: First proposed time: 1300 UTC Tokyo (UTC+0900): 10:00 PM Bengaluru (UTC+0530): 6:30 PM US Eastern (UTC-0400): 9:00 AM US Pacific (UTC-0700): 6:00 AM Second proposed time: 0100 UTC Tokyo (UTC+0900): 10:00 AM Bengaluru (UTC+0530): 6:30 AM US Eastern (UTC-0400): 9:00 PM US Pacific (UTC-0700): 6:00 PM Please weigh in on which time works best for you. Our next team meeting on 10/2 will be at the same time as usual, and we can discuss the change then. Thanks so much, --N. __ 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
