Open Stack

Public bug reported:

When using Ansible with recent updates including openstacksdk 0.99.0
failures can be reproduced with Ansible, using the
openstack.compute.v2.server.Server module in Playbooks.

Issue appears when trying to launch new instances in an OpenStack
environment.

Detail message:
n exception occurred during task execution. To see the full traceback, use -vvv. The error was: KeyError: 'volumes is not found. openstack.compute.v2.server.Server objects do not support setting arbitrary keys through the dict interface.'

A role back to openstacksdk version 0.61 works as workaround.

Some details:
ansible [core 2.13.0]
  config file = /.../ansible.cfg
  configured module search path = ['/.../.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
  ansible python module location = /.../.local/lib/python3.9/site-packages/ansible
  ansible collection location = /.../.ansible/collections:/usr/share/ansible/collections
  executable location = /usr/local/bin/ansible
  python version = 3.9.2 (default, Feb 28 2021, 17:03:44) [GCC 10.2.1 20210110]
  jinja version = 3.1.2
  libyaml = True

** Affects: openstack-i18n
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of OpenStack
I18n Core Team, which is subscribed to openstack i18n.
https://bugs.launchpad.net/bugs/1975497

Title:
  openstacksdk 0.99.0 failure in compute.v2.server in Ansible

Status in openstack i18n:
  New

Bug description:
  When using Ansible with recent updates including openstacksdk 0.99.0
  failures can be reproduced with Ansible, using the
  openstack.compute.v2.server.Server module in Playbooks.

  Issue appears when trying to launch new instances in an OpenStack
  environment.

  Detail message:
  n exception occurred during task execution. To see the full traceback, use -vvv. The error was: KeyError: 'volumes is not found. openstack.compute.v2.server.Server objects do not support setting arbitrary keys through the dict interface.'

  A role back to openstacksdk version 0.61 works as workaround.

  Some details:
  ansible [core 2.13.0]
    config file = /.../ansible.cfg
    configured module search path = ['/.../.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
    ansible python module location = /.../.local/lib/python3.9/site-packages/ansible
    ansible collection location = /.../.ansible/collections:/usr/share/ansible/collections
    executable location = /usr/local/bin/ansible
    python version = 3.9.2 (default, Feb 28 2021, 17:03:44) [GCC 10.2.1 20210110]
    jinja version = 3.1.2
    libyaml = True

To manage notifications about this bug go to:
https://bugs.launchpad.net/openstack-i18n/+bug/1975497/+subscriptions