Ask Your Question

Magnum Swarm - master_lb_enabled

asked 2016-08-01 09:57:50 -0500

Maik gravatar image

updated 2016-08-02 02:12:37 -0500

magnum bay-create --name swarmbay --baymodel swarmbaymodel --node-count 1 fails with

InvalidParameterValue: ERROR: Unknown resource Type : Magnum::Optional::Neutron::Pool::HealthMonitor

How can i avoid this error?

API Log stack trace

45817: DEBUG wsme.api [req-58500adb-b62b-4f2a-8e73-f1351d5561cd test2 test2 - - -] Client-side error: ERROR: Unknown resource Type : Magnum::Optional::Neutron::Pool::HealthMonitor
Traceback (most recent call last):

  File "/var/lib/magnum/env/local/lib/python2.7/site-packages/oslo_messaging/rpc/", line 133, in _process_incoming
    res = self.dispatcher.dispatch(message)

  File "/var/lib/magnum/env/local/lib/python2.7/site-packages/oslo_messaging/rpc/", line 150, in dispatch
    return self._do_dispatch(endpoint, method, ctxt, args)

  File "/var/lib/magnum/env/local/lib/python2.7/site-packages/oslo_messaging/rpc/", line 121, in _do_dispatch
    result = func(ctxt, **new_args)

  File "/var/lib/magnum/env/local/lib/python2.7/site-packages/magnum/conductor/handlers/", line 167, in bay_create
    raise e

InvalidParameterValue: ERROR: Unknown resource Type : Magnum::Optional::Neutron::Pool::HealthMonitor
 format_exception /var/lib/magnum/env/local/lib/python2.7/site-packages/wsme/

Conductor shows the same Lines

edit retag flag offensive close merge delete


Add some logs

Maik gravatar imageMaik ( 2016-08-02 02:12:46 -0500 )edit

2 answers

Sort by ยป oldest newest most voted

answered 2016-08-01 14:49:05 -0500

JustcallmeDrago gravatar image

It would be helpful if you posted the API and/or conductor logs if there are any error messages or stack traces in them. Please feel free to drop by the #openstack-containers IRC channel on freenode to get help! My IRC handle is Drago.

Having only the error to go on, here's what I can say:

This is the patch that changed the OS::Neutron::HealthMonitor resource to Magnum::Optional::Neutron::Pool::HealthMonitor: It includes Heat environment files [1] to map Magnum::Optional::Neutron::Pool::HealthMonitor to either OS::Neutron::HealthMonitor or OS::Heat::None (effectively enabling/disabling it). The environment files were moved in

The only reasons I can think of for this occurring are:

  1. Your magnum service code is not up-to-date. When you update the code, make sure the magnum API and conductor get restarted, or else the new versions of python files will not be picked up. The currently-running Magnum processes may still be looking in the location the environment files were before they were moved and not be able to apply the environment files to do the resource remapping.
  2. with_master_lb.yaml and/or no_master_lb.yaml are completely missing from magnum/drivers/common/templates/environments.

[1] (

edit flag offensive delete link more


I used the newest master branch Revision: d92c76f6d1790771ee5da4c9d1c0a3f718acde2d, 2016.07.31 20:54:58

Patchs included in my installation:

Maik gravatar imageMaik ( 2016-08-02 02:34:42 -0500 )edit

ENV Files are on the right place

root@magnum1:/opt/magnum-master/magnum/drivers/common/templates/environments# ll
Maik gravatar imageMaik ( 2016-08-02 02:38:07 -0500 )edit

If have checked the code by moving the environments files - i see that if i moved the files the errors changed to something like "Can not access files", so python schould used the right code

Maik gravatar imageMaik ( 2016-08-02 02:45:57 -0500 )edit

answered 2016-08-01 21:04:41 -0500

Praveen N gravatar image

Hi, The below links may help you about Openstack Magnum,

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower


Asked: 2016-08-01 09:57:50 -0500

Seen: 188 times

Last updated: Aug 02 '16