Verify operation in masakari

[elnaz sa]

can not create segment in ubuntu 20 with this error :Request requires an ID but none was found

This bug tracker is for errors with the documentation, use the following as a template and remove or add fields as you see fit. Convert [ ] into [x] to check boxes:

- [ ] This doc is inaccurate in this way: ______
- [ ] This is a doc addition request.
- [ ] I have a fix to the document that I can paste below including example: input and output.

If you have a troubleshooting or support issue, use the following resources:

 - The mailing list: https://lists.openstack.org
 - IRC: 'openstack' channel on Freenode

-----------------------------------
Release: 11.0.1.dev5 on 2019-08-28 20:19:06
SHA: 6f01a0661a084d4267ea6d3982fc8ec8482b9cdc
Source: https://opendev.org/openstack/masakari/src/doc/source/install/verify.rst
URL: https://docs.openstack.org/masakari/wallaby/install/verify.html

[Radosław Piliszek (yoctozepto)]

Please share the installation method you used, the exact steps you took to get this error and logs of the API service.

[elnaz sa (elnaz23)]

 sure
 first i create mysql database for masakari and create user, service and endpoints according by openstack site: https://docs.openstack.org/masakari/wallaby/install/install_and_configure_ubuntu.html

also configure my compute nodes in pacemaker cluster and insall masakari-monitor on compute nodes

the masakari-api has started with no errors and get notification when an instance or compute node failed.
and for testing the masakari-engine we have to config failover segment but when create segment with this command (openstack segment create s1 auto COMPUTE
we have this error :"quest requires an ID but none was found"

thanks for your Attention

[Radosław Piliszek (yoctozepto)]

Interesting, it does not seem reproducible. May I interest you in deploying Masakari with automatic tooling like Kolla-Ansible or OpenStack-Ansible?

Also, try to run this command with --debug and also attach logs from masakari api.

[elnaz sa (elnaz23)]

 thanks for answer
I run this command with --debug option and the output is

Attribute [] not found in [<openstack.resource._ComponentManager object at 0x7fb5d722b0d0>]: ''.
Attribute [] not found in [<openstack.resource._ComponentManager object at 0x7fb5d722b910>]: ''.
Attribute [] not found in [<openstack.resource._ComponentManager object at 0x7fb5d722b910>]: ''.
Request requires an ID but none was found
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/cliff/app.py", line 401, in run_subcommand
    result = cmd.run(parsed_args)
  File "/usr/lib/python3/dist-packages/osc_lib/command/command.py", line 39, in run
    return super(Command, self).run(parsed_args)
  File "/usr/lib/python3/dist-packages/cliff/display.py", line 115, in run
    column_names, data = self.take_action(parsed_args)
  File "/usr/local/lib/python3.8/dist-packages/masakariclient/osc/v1/segment.py", line 168, in take_action
    return _show_segment(masakari_client,
  File "/usr/local/lib/python3.8/dist-packages/masakariclient/osc/v1/segment.py", line 277, in _show_segment
    segment = masakari_client.get_segment(segment_uuid)
  File "/usr/lib/python3/dist-packages/openstack/instance_ha/v1/_proxy.py", line 86, in get_segment
    return self._get(_segment.Segment, segment)
  File "/usr/lib/python3/dist-packages/openstack/proxy.py", line 47, in check
    return method(self, expected, actual, *args, **kwargs)
  File "/usr/lib/python3/dist-packages/openstack/proxy.py", line 506, in _get
    return res.fetch(
  File "/usr/lib/python3/dist-packages/openstack/resource.py", line 1450, in fetch
    request = self._prepare_request(requires_id=requires_id,
  File "/usr/lib/python3/dist-packages/openstack/resource.py", line 1136, in _prepare_request
    raise exceptions.InvalidRequest(
openstack.exceptions.InvalidRequest: Request requires an ID but none was found
clean_up CreateSegment: Request requires an ID but none was found
====================================
could you tell me more about deploying masakari with
 ansible ?

[Radosław Piliszek (yoctozepto)]

Ah, so it failed at request preparation stage. Interesting.
Your server-side installation might be fine but there seems to be some incompatibility between SDK and client components that cause an issue. What versions of clients do you have installed? Please share the output of `pip list`.

Those Ansible-based solutions are opinionated and they deploy the whole OpenStack installation for you. Deploying a single service might need more effort on your side. Anyhow, here are the docs for the two solutions I mentioned:
https://docs.openstack.org/kolla-ansible/latest/
https://docs.openstack.org/openstack-ansible/latest/
There are also others and it is usually recommended to use one of the deployment projects rather than to try everything from scratch.

[elnaz sa (elnaz23)]

thank you very much

the output from pip list:
============================

alembic 1.4.3.dev0
amqp 5.0.3
aniso8601 8.0.0
anyjson 0.3.3
appdirs 1.4.3
arrow 0.15.5
attrs 19.3.0
Automat 0.8.0
automaton 2.3.0
Babel 2.8.0
backports.entry-points-selectable 1.1.0
bcrypt 3.1.7
beautifulsoup4 4.8.2
blinker 1.4
cachetools 4.0.0
castellan 3.7.1
certifi 2019.11.28
cffi 1.14.0
chardet 3.0.4
cinder 18.0.0
Click 7.0
cliff 3.6.0
cloud-init 21.2
cmd2 0.8.5
colorama 0.4.3
command-not-found 0.3
configobj 5.0.6
constantly 15.1.0
crmsh 4.0.0
cryptography 3.3.2
csscompressor 0.9.4
cursive 0.2.2
dbus-python 1.2.16
ddt 1.4.1
debtcollector 2.2.0
decorator 4.4.2
defusedxml 0.6.0
deprecation 2.0.7
distlib 0.3.2
distro 1.4.0
distro-info 0.23ubuntu1
Django 2.2.12
django-appconf 1.0.3
django-compressor 2.2
django-debreach 2.0.1
django-pyscss 2.0.2
dnspython 1.16.0
docutils 0.16
dogpile.cache 1.1.2
entrypoints 0.3
eventlet 0.30.0
extras 1.0.0
fasteners 0.14.1
filelock 3.0.12
fixtures 3.0.0
Flask 1.1.1
Flask-RESTful 0.3.8
futurist 2.1.0
glance 22.0.0
glance-store 2.5.0
greenlet 0.4.17
horizon 19.2.0
html5lib 1.0.1
httplib2 0.18.1
hyperlink 19.0.0
idna 2.8
importlib-metadata 1.6.0
incremental 16.10.1
iso8601 0.1.12
itsdangerous 1.1.0
Jinja2 2.10.1
jmespath 0.9.4
jsonpatch 1.22
jsonpointer 2.0
jsonschema 3.2.0
keyring 18.0.1
keystone 19.0.0
keystoneauth1 ...

[Radosław Piliszek (yoctozepto)]

Well, you can fix python-masakariclient by installing version 7.0.0 (for Wallaby). But the installed version should not differ enough to justify this error. Perhaps there is some other version discrepancy in there. I see you are using Ubuntu but I got it that you installed Masakari manually despite the fact that Ubuntu provides Masakari in packages. I am afraid you might have introduced a very particular packaging issue into your environment that might be hard for me to debug. If reinstalling version 7.0.0 does not fix the issue, then I will be out of ideas. :-(

[elnaz sa (elnaz23)]

thank you very much

[Launchpad Janitor (janitor)]

[Expired for masakari because there has been no activity for 60 days.]