January 2023 - openstack-discuss - lists.openstack.org

[outreachy] Call for Outreachy mentors and mentoring organizations for May 2023 internships
by Sofia Enriquez 23 Jan '23

23 Jan '23

Outreachy is seeking open source and open science communities to mentor interns! Outreachy is hosting a live streamed chat with past Outreachy mentors. If you know someone interested in mentoring, please encourage them to attend! See the "Mentor Chats" section below for details. Important dates: - Jan. 17 at 3pm UTC - Mentor chat on YouTube and PeerTube - Feb. 6 at 3pm UTC - Mentor chat on YouTube and PeerTube - Feb. 10 at 4pm UTC - Deadline for open source and open science communities to sign up to be an Outreachy mentoring organization - Feb. 24 at 4pm UTC - Deadline for mentors to submit project descriptions for May 2023 interns to work on What is Outreachy? --- Outreachy is a paid, remote internship program. Outreachy promotes diversity in open source and open science. Our internships are for people who face under-representation, and discrimination or systemic bias in the technology industry of their country. Open source and open science communities can apply to be an Outreachy mentoring organization here: https://www.outreachy.org/communities/cfp/ Please see our blog post for additional details: https://www.outreachy.org/blog/2023-01-05/may-2023-call-for-mentoring-organ… Schedule -------- Jan. 17, 2023 at 3pm UTC - Mentor chat on YouTube and PeerTube Feb. 6, 2023 at 3pm UTC - Mentor chat on YouTube and PeerTube Feb. 10, 2023 - last day for mentoring organizations to sign up Feb. 24, 2023 - last day for mentors to submit projects Mar. 6, 2023 at 4pm UTC - contribution period opens Apr. 3, 2023 at 4pm UTC - contribution period closes May 4, 2023 - interns announced May 29, 2023 to Aug. 25, 2023 - internship -- Sofía Enriquez she/her Software Engineer Red Hat PnT <https://www.redhat.com> IRC: @enriquetaso @RedHat <https://twitter.com/redhat> Red Hat <https://www.linkedin.com/company/red-hat> Red Hat <https://www.facebook.com/RedHatInc> <https://www.redhat.com>

1 0

[Neutron] Bug Deputy Report January 16 - 23
by Jakub Libosvar 23 Jan '23

23 Jan '23

Hi, I was bug deputy last week. There is one critical bug but Slawek is on top of it. Here is the rest of the report: Critical - tempest slow jobs fails https://bugs.launchpad.net/neutron/+bug/2003063 Proposed patch: https://review.opendev.org/c/openstack/neutron/+/871272 Assigned to Slawek High - [FT] Error in “test_arp_spoof_doesnt_block_ipv6” https://bugs.launchpad.net/neutron/+bug/2003196 Patch to gather more information: https://review.opendev.org/c/openstack/neutron/+/871101 Assigned to Rodolfo - [ovn] MTU issues due to centralized vlan provider networks https://bugs.launchpad.net/neutron/+bug/2003455 Assigned to Luis Medium - DVR HA router gets stuck in backup state https://bugs.launchpad.net/neutron/+bug/2003359 Needs an assignee - Floating IP stuck in snat-ns after binding host to associated fixed IP https://bugs.launchpad.net/neutron/+bug/2003532 Needs an assignee but Rodolfo attempts to reproduce - Some port attributes are ignored in bulk port create: allowed_address_pairs, extra_dhcp_opts https://bugs.launchpad.net/neutron/+bug/2003553 Proposed patch: https://review.opendev.org/c/openstack/neutron/+/871294 Assigned to Bence - [OVN] Security group logging only logs half of the connection https://bugs.launchpad.net/neutron/+bug/2003706 Assigned to Elvira Low - neutron-keepalived-state-change unconditional debug mode https://bugs.launchpad.net/neutron/+bug/2003534 Proposed fix: https://review.opendev.org/c/openstack/neutron/+/871274 Assigned to Rodolfo RFEs: - [RFE] Provide Port Binding Information for Manila Share Server Live Migration https://bugs.launchpad.net/neutron/+bug/2003095

1 0

[kolla-ansible] [cinder] Setting up multiple LVM cinder backends located on different servers
by A Monster 23 Jan '23

23 Jan '23

I have an openstack configuration, with 3 controller nodes and multiple compute nodes , one of the controllers has an LVM storage based on HDD drives, while another one has an SDD one, and when I tried to configure the two different types of storage as cinder backends I faced a dilemma since according to the documentation I have to specify the two different backends in the cinder configuration as it is explained here <https://docs.openstack.org/cinder/latest/admin/multi-backend.html> however and since I want to separate disks type when creating volumes, I had to specify different backend names, but I don't know if this configuration should be written in both the storage nodes, or should I specify for each one of these storage nodes the configuration related to its own type of disks. Now, I tried writing the same configuration for both nodes, but I found out that the volume service related to server1 concerning disks in server2 is down, and the volume service in server2 concerning disks in server1 is also down. $ openstack volume service list+------------------+---------------------+------+---------+-------+----------------------------+| Binary | Host | Zone | Status | State | Updated At |+------------------+---------------------+------+---------+-------+----------------------------+| cinder-scheduler | controller-01 | nova | enabled | up | 2023-01-18T14:27:51.000000 || cinder-scheduler | controller-02 | nova | enabled | up | 2023-01-18T14:27:41.000000 || cinder-scheduler | controller-03 | nova | enabled | up | 2023-01-18T14:27:50.000000 || cinder-volume | controller-03@lvm-1 | nova | enabled | up | 2023-01-18T14:27:42.000000 || cinder-volume | controller-01@lvm-1 | nova | enabled | down | 2023-01-18T14:10:00.000000 || cinder-volume | controller-01@lvm-3 | nova | enabled | down | 2023-01-18T14:09:42.000000 || cinder-volume | controller-03@lvm-3 | nova | enabled | down | 2023-01-18T12:12:19.000000|+------------------+---------------------+------+---------+-------+----------------------------+ This is the configuration I have written on the configuration files for cinder_api _cinder_scheduler and cinder_volume for both servers. enabled_backends= lvm-1,lvm-3 [lvm-1] volume_group = cinder-volumes volume_driver = cinder.volume.drivers.lvm.LVMVolumeDriver volume_backend_name = lvm-1 target_helper = lioadm target_protocol = iscsi report_discard_supported = true [lvm-3] volume_group=cinder-volumes-ssd volume_driver=cinder.volume.drivers.lvm.LVMVolumeDriver volume_backend_name=lvm-3 target_helper = lioadm target_protocol = iscsi report_discard_supported = true

2 3

Snapshot error
by Kaiser Wassilij 23 Jan '23

23 Jan '23

Hello, I upgraded from Victoria to Yoga. DISTRIB_ID="OSA" DISTRIB_RELEASE="25.2.0" DISTRIB_CODENAME="Yoga" DISTRIB_DESCRIPTION="OpenStack-Ansible" I have error infra1-glance-container-dc13a04b glance-wsgi-api[282311]: 2023-01-23 13:25:06.745 282311 INFO glance.api.v2.image_data [req-10359154-0be4-4da1-9e85-2d94079c17b4 b2dca74976034d5b9925bdcb03470603 021ce436ab004cde851055bac66370bc - default default] Unable to create trust: no such option collect_timing in group [keystone_authtoken] Use the existing user token. 2023-01-23 14:09:28.890 282298 DEBUG glance.api.v2.images [req-bf237e2c-9aca-4089-a56f-dfa245afdcc6 b2dca74976034d5b9925bdcb03470603 021ce436ab004cde851055bac66370bc - default default] The 'locations' list of image 2995602a-b5da-4758-a1f9-f6b083815f9b is empty _format_image /openstack/venvs/glance-25.2.0/lib/python3.8/site-packages/glance/api/v2/images.py https://bugs.launchpad.net/glance/+bug/1916052 Do any have the same error and how did you solve it Kind regards

2 1

[osprofiler] Regarding contribution process
by Sahid Orentino Ferdjaoui 23 Jan '23

23 Jan '23

Hello, We would like to make some contributions on OSprofiler but not sure of the path that we are taking. For the first one we would like to make a contribution that is adding an option for Jaeger drivers. The point is to add a prefix for the service name. A bug report has been opened for it [0]. Another contribution would be to introduce a set of tags to jaeger spans, still from an option. And finally we would like to add support of Open Telemetry driver. Any suggestions regarding the process that we should use? Spec, blueprint, bug report. Also any blockers that the community may think about? Thanks, s.

1 0

Pulling plugins from my repository
by vincent lee 23 Jan '23

23 Jan '23

Hi everyone, I would like to know where exactly I can replace the path for the GitHub repository. For example, I want to pull some plugins, such as zun_ui, blazar_dashboard, etc., from my own GitHub repository instead of the default GitHub repository. I am currently using Kolla-ansible for deploying OpenStack in the yoga version. Best, Vincent

1 0

Pulling plugins from my repository
by vincent lee 21 Jan '23

21 Jan '23

Hi all, I would like to ask where exactly I can change the default path in which plugins such as zun_ui, blazar_dashboard, etc... can be pulled from my GitHub instead of the default repository. Best, Vincent

2 1

[all][tc] What's happening in Technical Committee: summary 2023 Jan 20: Reading: 5 min
by Ghanshyam Mann 21 Jan '23

21 Jan '23

Hello Everyone, Here is this week's summary of the Technical Committee activities. 1. TC Meetings: ============ * We had this week's meeting on Jan 18. Most of the meeting discussions are summarized in this email. Meeting logs are available @ https://meetings.opendev.org/meetings/tc/2023/tc.2023-01-18-16.00.log.html * The next TC weekly meeting will be on Jan 25 Wed at 16:00 UTC, Feel free to add the topic to the agenda[1] by Jan 24. 2. What we completed this week: ========================= * Removed Adjutant from inactive project list[2] 3. Activities In progress: ================== TC Tracker for the 2023.1 cycle ------------------------------------- * Current cycle working items and their progress are present in the 2023.1 tracker etherpad[3]. Open Reviews ----------------- * Four open reviews for ongoing activities[4]. Cleanup of PyPI maintainer list for OpenStack Projects ---------------------------------------------------------------- The horizon team discussed the 'xstatic-font-awesome' repo PyPi maintainer topic[5] in their weekly meetings and decided to hand over the maintenance to additional external maintainers. The horizon team will retire the repo from OpenStack. To clean up other OpenStack packages, I have sent a separate email[6] to audit first and then we can cleanup based on the audit results. Requesting every PTL to look and do the required step. Project updates ------------------- * Add Cinder Huawei charm[7] * Add the woodpecker charm to Openstack charms[8] Less Active/Inactive projects: ~~~~~~~~~~~~~~~~~~~~~~ * Zaqar status TC discussed and set a deadline of Jan 25th (next week's TC meeting) to check the status and take a final call on Zaqar to be included in this cycle release or not. Zaqar PTL is trying to fix the gate[9]. * Mistral status: python-mistralclient gate is also green now and their beta releases are in progress[10][11]. 4. How to contact the TC: ==================== If you would like to discuss or give feedback to TC, you can reach out to us in multiple ways: 1. Email: you can send the email with tag [tc] on openstack-discuss ML[12]. 2. Weekly meeting: The Technical Committee conduct a weekly meeting every Thursday 15:00 UTC [13] 3. Ping us using 'tc-members' nickname on #openstack-tc IRC channel. [1] https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Agenda_Suggesti… [2] https://review.opendev.org/c/openstack/governance/+/869665 [3] https://etherpad.opendev.org/p/tc-2023.1-tracker [4] https://review.opendev.org/q/projects:openstack/governance+status:open [5] https://github.com/openstack/xstatic-font-awesome/pull/2 [6] https://lists.openstack.org/pipermail/openstack-discuss/2023-January/031848… [7] https://review.opendev.org/c/openstack/governance/+/867588 [8] https://review.opendev.org/c/openstack/governance/+/869752 [9] https://review.opendev.org/c/openstack/zaqar/+/857924/ [10] https://review.opendev.org/c/openstack/releases/+/869470 [11] https://review.opendev.org/c/openstack/releases/+/869448 [12] hhttp://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss [13] http://eavesdrop.openstack.org/#Technical_Committee_Meeting -gmann

1 0

upgrade from Yoda to Zed according to the documentation
by Kaiser Wassilij 20 Jan '23

20 Jan '23

Hallo, I'm trying the openstack system upgrade from Yoda to Zed according to the documentation https://docs.openstack.org/openstack-ansible/zed/admin/upgrades/major-upgra… But I get the following errors: TASK [Clone git repos (parallel)] *********************************************************************************************************************************************************************** An exception occurred during task execution. To see the full traceback, use -vvv. The error was: TypeError: Value of unknown type: <class 'multiprocessing.managers.ListProxy'>, [["Failed to fetch /etc/ansible/roles/etcd\nCmd('git') failed due to: exit code(128)\n cmdline: git fetch --force --shallow-since=2022-05-27\n stderr: 'fatal: error in object: unshallow 29996b0d15ebfaacb7626ce889e26b209ed53434\nfatal: the remote end hung up unexpectedly'"], ["Failed to fetch /etc/ansible/roles/etcd\nCmd('git') failed due to: exit code(128)\n cmdline: git fetch --force --shallow-since=2022-05-27\n stderr: 'fatal: error in object: unshallow 29996b0d15ebfaacb7626ce889e26b209ed53434\nfatal: the remote end hung up unexpectedly'"], ["Role {'name': 'etcd', 'scm': 'git', 'src': 'https://github.com/noonedeadpunk/ansible-etcd' https://github.com/noonedeadpunk/ansible-etcd' , 'version': 'master', 'trackbranch': 'master', 'shallow_since': '2022-05-27', 'path': '/etc/ansible/roles', 'refspec': None, 'depth': 20, 'dest': '/etc/ansible/roles/etcd'} failed after 2 retries\n"]] fatal: [localhost]: FAILED! => {"changed": false, "module_stderr": "Traceback (most recent call last):\n File \"<stdin>\", line 107, in <module>\n File \"<stdin>\", line 99, in _ansiballz_main\n File \"<stdin>\", line 47, in invoke_module\n File \"/usr/lib/python3.8/runpy.py\", line 207, in run_module\n return _run_module_code(code, init_globals, run_name, mod_spec)\n File \"/usr/lib/python3.8/runpy.py\", line 97, in _run_module_code\n _run_code(code, mod_globals, init_globals,\n File \"/usr/lib/python3.8/runpy.py\", line 87, in _run_code\n exec(code, run_globals)\n File \"/tmp/ansible_openstack.osa.git_requirements_payload_m0tl1pcb/ansible_openstack.osa.git_requirements_payload.zip/ansible/modules/openstack/osa/git_requirements.py\", line 333, in <module>\n File \"/tmp/ansible_openstack.osa.git_requirements_payload_m0tl1pcb/ansible_openstack.osa.git_requirements_payload.zip/ansible/modules/openstack/osa/git_requirements.py\", line 329, in main\n File \"/tmp/ansible_openstack.osa.git_requirements_payload_m0tl1pcb/ansible_openstack.osa.git_requirements_payload.zip/ansible/module_utils/basic.py\", line 1533, in fail_json\n File \"/tmp/ansible_openstack.osa.git_requirements_payload_m0tl1pcb/ansible_openstack.osa.git_requirements_payload.zip/ansible/module_utils/basic.py\", line 1506, in _return_formatted\n File \"/tmp/ansible_openstack.osa.git_requirements_payload_m0tl1pcb/ansible_openstack.osa.git_requirements_payload.zip/ansible/module_utils/common/parameters.py\", line 887, in remove_values\n File \"/tmp/ansible_openstack.osa.git_requirements_payload_m0tl1pcb/ansible_openstack.osa.git_requirements_payload.zip/ansible/module_utils/common/parameters.py\", line 461, in _remove_values_conditions\nTypeError: Value of unknown type: <class 'multiprocessing.managers.ListProxy'>, [[\"Failed to fetch /etc/ansible/roles/etcd\\nCmd('git') failed due to: exit code(128)\\n cmdline: git fetch --force --shallow-since=2022-05-27\\n stderr: 'fatal: error in object: unshallow 29996b0d15ebfaacb7626ce889e26b209ed53434\\nfatal: the remote end hung up unexpectedly'\"], [\"Failed to fetch /etc/ansible/roles/etcd\\nCmd('git') failed due to: exit code(128)\\n cmdline: git fetch --force --shallow-since=2022-05-27\\n stderr: 'fatal: error in object: unshallow 29996b0d15ebfaacb7626ce889e26b209ed53434\\nfatal: the remote end hung up unexpectedly'\"], [\"Role {'name': 'etcd', 'scm': 'git', 'src': 'https://github.com/noonedeadpunk/ansible-etcd' https://github.com/noonedeadpunk/ansible-etcd' , 'version': 'master', 'trackbranch': 'master', 'shallow_since': '2022-05-27', 'path': '/etc/ansible/roles', 'refspec': None, 'depth': 20, 'dest': '/etc/ansible/roles/etcd'} failed after 2 retries\\n\"]]\n", "module_stdout": "", "msg": "MODULE FAILURE\nSee stdout/stderr for the exact error", "rc": 1} TASK [Clone git repos (with git)]******** failed: [localhost] (item={'name': 'etcd', 'scm': 'git', 'src': 'https://github.com/noonedeadpunk/ansible-etcd' https://github.com/noonedeadpunk/ansible-etcd' , 'version': 'master', 'trackbranch': 'master', 'shallow_since': '2022-05-27'}) => {"ansible_loop_var": "item", "attempts": 2, "changed": false, "cmd": ["/usr/bin/git", "fetch", "--depth", "20", "--force", "origin", "+refs/heads/master:refs/remotes/origin/master"], "item": {"name": "etcd", "scm": "git", "shallow_since": "2022-05-27", "src": "https://github.com/noonedeadpunk/ansible-etcd", "trackbranch": "master", "version": "master"}, "msg": "Failed to download remote objects and refs: fatal: error in object: unshallow 29996b0d15ebfaacb7626ce889e26b209ed53434\nfatal: the remote end hung up unexpectedly\n"} Does anyone of you have the idea? What should I do? For this reason, no further playbooks will be released. Kind regards

3 2

[openstack-ansible] Installing OpenStack with Ansible fails during Keystone playbook on TASK openstack.osa.db_setup
by jmarcelo.alencar＠gmail.com 20 Jan '23

20 Jan '23

Hello Community, I am trying to create a two machine deployment following Openstack Ansible Deployment Guide (https://docs.openstack.org/project-deploy-guide/openstack-ansible/latest/) The two machines are named targethost01 and targethost02, and I am running Ansible from deploymenthost. Every machine has 4-Core CPUs, 8 GB of RAM, and 240 GB SSD. I am using Ubuntu 22.04.1 LTS. The machine targethost01 has the following network configuration: network: version: 2 ethernets: enp5s0: dhcp4: true enp6s0: {} enp7s0: {} enp8s0: {} enp9s0: {} vlans: vlan.10: id: 10 link: enp6s0 addresses: [ ] vlan.20: id: 20 link: enp7s0 addresses: [ ] vlan.30: id: 30 link: enp8s0 addresses: [ ] vlan.40: id: 40 link: enp9s0 addresses: [ ] bridges: br-mgmt: addresses: [ 172.29.236.101/22 ] mtu: 1500 interfaces: - vlan.10 br-storage: addresses: [ 172.29.244.101/22 ] mtu: 1500 interfaces: - vlan.20 br-vlan: addresses: [] mtu: 1500 interfaces: - vlan.30 br-vxlan: addresses: [ 172.29.240.101/22 ] mtu: 1500 interfaces: - vlan.40 And targethost02 has the following network configuration: network: version: 2 ethernets: enp5s0: dhcp4: true enp6s0: {} enp7s0: {} enp8s0: {} enp9s0: {} vlans: vlan.10: id: 10 link: enp6s0 addresses: [ ] vlan.20: id: 20 link: enp7s0 addresses: [ ] vlan.30: id: 30 link: enp8s0 addresses: [ ] vlan.40: id: 40 link: enp9s0 addresses: [ ] bridges: br-mgmt: addresses: [ 172.29.236.102/22 ] mtu: 1500 interfaces: - vlan.10 br-storage: addresses: [ 172.29.244.102/22 ] mtu: 1500 interfaces: - vlan.20 br-vlan: addresses: [] mtu: 1500 interfaces: - vlan.30 br-vxlan: addresses: [ 172.29.240.102/22 ] mtu: 1500 interfaces: - vlan.40 On the deploymenthost, /etc/openstack_deploy/openstack_user_config.yml has the following: --- cidr_networks: container: 172.29.236.0/22 tunnel: 172.29.240.0/22 storage: 172.29.244.0/22 used_ips: - 172.29.236.1 - "172.29.236.100,172.29.236.200" - "172.29.240.100,172.29.240.200" - "172.29.244.100,172.29.244.200" global_overrides: internal_lb_vip_address: 172.29.236.101 external_lb_vip_address: "{{ bootstrap_host_public_address | default(ansible_facts['default_ipv4']['address']) }}" management_bridge: "br-mgmt" provider_networks: - network: group_binds: - all_containers - hosts type: "raw" container_bridge: "br-mgmt" container_interface: "eth1" container_type: "veth" ip_from_q: "container" is_container_address: true - network: group_binds: - glance_api - cinder_api - cinder_volume - nova_compute type: "raw" container_bridge: "br-storage" container_type: "veth" container_interface: "eth2" container_mtu: "9000" ip_from_q: "storage" - network: group_binds: - neutron_linuxbridge_agent container_bridge: "br-vxlan" container_type: "veth" container_interface: "eth10" container_mtu: "9000" ip_from_q: "tunnel" type: "vxlan" range: "1:1000" net_name: "vxlan" - network: group_binds: - neutron_linuxbridge_agent container_bridge: "br-vlan" container_type: "veth" container_interface: "eth11" type: "vlan" range: "101:200,301:400" net_name: "vlan" - network: group_binds: - neutron_linuxbridge_agent container_bridge: "br-vlan" container_type: "veth" container_interface: "eth12" host_bind_override: "eth12" type: "flat" net_name: "flat" shared-infra_hosts: targethost01: ip: 172.29.236.101 repo-infra_hosts: targethost01: ip: 172.29.236.101 coordination_hosts: targethost01: ip: 172.29.236.101 os-infra_hosts: targethost01: ip: 172.29.236.101 identity_hosts: targethost01: ip: 172.29.236.101 network_hosts: targethost01: ip: 172.29.236.101 compute_hosts: targethost01: ip: 172.29.236.101 targethost02: ip: 172.29.236.102 storage-infra_hosts: targethost01: ip: 172.29.236.101 storage_hosts: targethost01: ip: 172.29.236.101 Also on the deploymenthost, /etc/openstack_deploy/conf.d/haproxy.yml has the following: haproxy_hosts: targethost01: ip: 172.29.236.101 At the Run Playbooks step of the guide, the following two Ansible commands return with unreachable=0 failed=0: # openstack-ansible setup-hosts.yml # openstack-ansible setup-infrastructure.yml And verifying the database also returns no error: root@deploymenthost:/opt/openstack-ansible/playbooks# ansible galera_container -m shell \ -a "mysql -h localhost -e 'show status like \"%wsrep_cluster_%\";'" Variable files: "-e @/etc/openstack_deploy/user_secrets.yml -e @/etc/openstack_deploy/user_variables.yml " [WARNING]: Unable to parse /etc/openstack_deploy/inventory.ini as an inventory source targethost01_galera_container-5aa8474a | CHANGED | rc=0 >> Variable_name Value wsrep_cluster_weight 1 wsrep_cluster_capabilities wsrep_cluster_conf_id 1 wsrep_cluster_size 1 wsrep_cluster_state_uuid e7a0c332-97fe-11ed-b0d4-26b30049826d wsrep_cluster_status Primary But when I execute openstack-ansible setup-openstack.yml, I get this: TASK [os_keystone : Fact for apache module mod_auth_openidc to be installed] *** ok: [targethost01_keystone_container-76e9b31b] TASK [include_role : openstack.osa.db_setup] *********************************** TASK [openstack.osa.db_setup : Create database for service] ******************** failed: [targethost01_keystone_container-76e9b31b -> targethost01_utility_container-dc05dc90(172.29.238.59)] (item=None) => {"censored": "the output has been hidden due to the fact that 'no_log: true' was specified for this result", "changed": false} fatal: [targethost01_keystone_container-76e9b31b -> {{ _oslodb_setup_host }}]: FAILED! => {"censored": "the output has been hidden due to the fact that 'no_log: true' was specified for this result", "changed": false} PLAY RECAP ********************************************************************* targethost01_keystone_container-76e9b31b : ok=33 changed=0 unreachable=0 failed=1 skipped=8 rescued=0 ignored=0 targethost01_utility_container-dc05dc90 : ok=3 changed=0 unreachable=0 failed=0 skipped=0 rescued=0 ignored=0 EXIT NOTICE [Playbook execution failure] ************************************** =============================================================================== First, how can I disable the "censored" warning? I wonder if the uncensored running could give me more clues. Second, it appears to be a problem creating the database (keystone db sync?) How can I test the database execution inside the LXC containers? I tried to log into one of the containers and ping the hosts IP and it works, so they have connectivity. I set up the passwords with: # cd /opt/openstack-ansible # ./scripts/pw-token-gen.py --file /etc/openstack_deploy/user_secrets.yml Any help? Best Regards. -- __________________________________ João Marcelo Uchôa de Alencar jmarcelo.alencar(at)gmail.com __________________________________

2 3