[Bug 1525800] Re: [SRU] ceilometer client error when create Alarm

[Brian Murray]

Hello Sergey, or anyone else affected,

Accepted heat into wily-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/heat/1:5.0.1-0ubuntu2
in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Tags added: verification-needed

-- 
You received this bug notification because you are a member of Ubuntu
OpenStack, which is subscribed to Ubuntu Cloud Archive.
https://bugs.launchpad.net/bugs/1525800

Title:
  [SRU] ceilometer client error when create Alarm

Status in Ubuntu Cloud Archive:
  Invalid
Status in Ubuntu Cloud Archive liberty series:
  New
Status in heat:
  Fix Released
Status in heat package in Ubuntu:
  Invalid
Status in heat source package in Wily:
  Fix Committed

Bug description:
  [Impact]

   * Creating a stack with e.g. OS::Ceilometer::Alarm is failing because
  Ceilometer client is being passed incorrect parameters. This patch
  fixes heat ceilometer client.

  [Test Case]

   * deploy Openstack Liberty
   * create a stack using a HOT template containing e.g. http://paste.ubuntu.com/15928508/
   * check that stack goes to CREATE_COMPLETE status

  [Regression Potential]

   * None

  I use OpenStack Liberty deployed by instruction for CentOS7 from docs.openstack.org
  I'm trying to create OS::Ceilometer::Alarm resource

  In heat-engine.log i have error

  2015-12-14 12:59:00.696 6672 ERROR heat.engine.resource BadRequest:
  Expecting to find domain in project - the server could not comply with
  the request since it is either malformed or otherwise incorrect. The
  client is assumed to be in error. (HTTP 400) (Request-ID: req-
  3d4ab42b-213b-4141-bd28-f8dbb2b79e96)

  environment
  [root at controller ~]# yum list installed | grep heat
  openstack-heat-api.noarch       1:5.0.0-1.el7          @centos-openstack-liberty
  openstack-heat-api-cfn.noarch   1:5.0.0-1.el7          @centos-openstack-liberty
  openstack-heat-common.noarch    1:5.0.0-1.el7          @centos-openstack-liberty
  openstack-heat-engine.noarch    1:5.0.0-1.el7          @centos-openstack-liberty
  python-heatclient.noarch        0.8.0-1.el7            @centos-openstack-liberty
  [root at controller ~]# yum list installed | grep ceilometer
  openstack-ceilometer-alarm.noarch
  openstack-ceilometer-api.noarch 1:5.0.0-1.el7          @centos-openstack-liberty
  python-ceilometer.noarch        1:5.0.0-1.el7          @centos-openstack-liberty
  python-ceilometerclient.noarch  1.5.0-1.el7            @centos-openstack-liberty

  my suggestion, bug in
  heat/engine/clients/os/ceilometer.py

  class CeilometerClientPlugin(client_plugin.ClientPlugin):

      ...

      def _create(self):
      ...
     args = {
              'auth_url': con.auth_url,
              'service_type': self.METERING,
              'project_name': con.tenant,          <--- HERE!!!
              'token': lambda: self.auth_token,
              'endpoint_type': endpoint_type,
              'os_endpoint': endpoint,
              'cacert': self._get_client_option('ceilometer', 'ca_file'),
              'cert_file': self._get_client_option('ceilometer', 'cert_file'),
              'key_file': self._get_client_option('ceilometer', 'key_file'),
              'insecure': self._get_client_option('ceilometer', 'insecure')
          }

  if use
         'project_id': con.tenant_id,
  instead
        'project_name': con.tenant,
  it works fine

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1525800/+subscriptions