Please contact your support team if you have a question or need assistance for any Rackspace products, services, or articles.
This question is not answered.
I am getting below error , anybody has a clue ?
# openstack-ansible setup-hosts.yml
Variable files: "-e @/etc/openstack_deploy/user_secrets.yml -e @/etc/openstack_deploy/user_variables.yml "ERROR: Inventory script (inventory/dynamic_inventory.py) had an execution error: Traceback (most recent call last): File "/opt/openstack-ansible/playbooks/inventory/dynamic_inventory.py", line 1044, in <module> main() File "/opt/openstack-ansible/playbooks/inventory/dynamic_inventory.py", line 988, in main skel_setup(environment, dynamic_inventory) File "/opt/openstack-ansible/playbooks/inventory/dynamic_inventory.py", line 408, in skel_setup for _key, _value in value.iteritems():AttributeError: 'str' object has no attribute 'iteritems'
Which tag are you deploying from? Is this the first time you ran this playbook? Did you modify anything in /etc/openstack_deploy/env.d? Have you tried writing a little debug statement in dynamic_inventory.py to see what the value of "value" is before that for loop is invoked?
I have edited swift.yaml from /etc/openstack_deploy/env.d & appended below contents
drives: - name: sdc - name: sdd - name: sdemount_point: /srv/node
i will add debug statement in script & let u know.
Those changes should be made to conf.d/swift.yml, not env.d/swift.yml.
env.d describes the layout of containers in the environment. You probably won't need to adjust these files, unless you are an advanced user with very special requirements for your environment.
conf.d describes how to configure those containers. These files are meant to be edited by most deployers, just like openstack_user_config.yml is.
The Rackspace Community (“Community”) is provided “AS IS” without warranty of any kind. The information on the Community sites is created by members of the Community and is intended for reference and general discussions only. Although some of the content may contain information provided by Rackspace employees, it does not represent an assessment of a particular customer environment or an assessment of any specific compliance with laws or regulations or constitute advice. We recommend that you engage additional expertise in order to further evaluate applicable requirements for your specific environment. For customer specific support issues please contact your Rackspace Support Team.READ MORE
RACKSPACE MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND, EXPRESS OR IMPLIED, AS TO THE ACCURACY OR COMPLETENESS OF THE CONTENTS OF THE RACKSPACE OPEN CLOUD COMMUNITY SITE. RACKSPACE RESERVES THE RIGHT TO DISCONTINUE OR MAKE CHANGES TO ITS SERVICES OFFERINGS AND SPECIFICATIONS AT ANY TIME WITHOUT NOTICE. USERS MUST TAKE FULL RESPONSIBILITY FOR APPLICATION OF ANY SERVICES AND/OR PROCESSES MENTIONED IN ANY COMMUNITY DISCUSSIONS. EXCEPT AS SET FORTH IN RACKSPACE GENERAL TERMS AND CONDITIONS, CLOUD TERMS OF SERVICE AND/OR OTHER AGREEMENT YOU SIGN WITH RACKSPACE, RACKSPACE ASSUMES NO LIABILITY WHATSOEVER, AND DISCLAIMS ANY EXPRESS OR IMPLIED WARRANTY, RELATING TO ITS SERVICES INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND NONINFRINGEMENT.
ALTHOUGH PART OF THE COMMUNITY GENERATED CONTENT MAY EXPLAIN HOW RACKSPACE SERVICES MAY WORK WITH THIRD PARTY PRODUCTS, THE INFORMATION CONTAINED IN THE COMMUNITY DISCUSSIONS IS NOT DESIGNED TO WORK WITH ALL SCENARIOS. ANY USE OR CHANGES TO THIRD PARTY PRODUCTS AND/OR CONFIGURATIONS SHOULD BE MADE AT THE DISCRETION OF YOUR ADMINISTRATORS AND SUBJECT TO THE APPLICABLE TERMS AND CONDITIONS OF SUCH THIRD PARTY. EVEN THOUGH RACKSPACE EMPLOYEES MAY PARTICIPATE IN THE COMMUNITY DISCUSSIONS, RACKSPACE DOES NOT PROVIDE TECHNICAL SUPPORT FOR THIRD PARTY PRODUCTS, OTHER THAN SPECIFIED IN YOUR HOSTING SERVICES AGREEMENT YOU HAVE SIGNED WITH RACKSPACE AND RACKSPACE ACCEPTS NO RESPONSIBILITY FOR THIRD-PARTY PRODUCTS.READ LESS