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

Mon May 9 13:26:32 UTC 2016

Hi,

Problem solved, but the ceilometer is not working as expected.

Scale up is not running. Does anyone know how to solve this problem?

---> alarm-notifier

2016-05-05 01:01:02.979 23618 INFO ceilometer.alarm.notifier.rest [req-1ee03d14-d011-4698-9396-c8237caf7c7b - - - - -] Notifying alarm teste-cpu_alarm_high-vut4wjst2npm ce5fa165-f216-4b41-bafa-ca80fee7018a with severity low from insufficient data to alarm with action SplitResult(scheme=u'http', netloc=u'controller:8000', path=u'/v1/signal/arn%3Aopenstack%3Aheat%3A%3A60d7922e29e44dc1ac62df3fe7ba3841%3Astacks%2Fteste%2F951d7e10-b296-4d7f-978a-270d56a7f7bc%2Fresources%2Fweb_server_scaleup_policy', query=u'Timestamp=2016-05-04T03%3A33%3A02Z&SignatureMethod=HmacSHA256&AWSAccessKeyId=69c5f5fc884f4e3a860d138fa0f854ce&SignatureVersion=2&Signature=o%2BSugdhZhPBnUrBlFo3Kx2bZuHmCP2l1J9%2BIVZ55vIU%3D', fragment='') because Transition to alarm due to 1 samples outside threshold, most recent: 89.1756234322. request-id: req-380e303d-1568-40e7-a721-888485f85209 
2016-05-05 01:02:02.825 23618 INFO ceilometer.alarm.notifier.rest [req-9603d3cf-de79-41d6-bebd-2fdbad688557 - - - - -] Notifying alarm teste-cpu_alarm_high-vut4wjst2npm ce5fa165-f216-4b41-bafa-ca80fee7018a with severity low from alarm to alarm with action SplitResult(scheme=u'http', netloc=u'controller:8000', path=u'/v1/signal/arn%3Aopenstack%3Aheat%3A%3A60d7922e29e44dc1ac62df3fe7ba3841%3Astacks%2Fteste%2F951d7e10-b296-4d7f-978a-270d56a7f7bc%2Fresources%2Fweb_server_scaleup_policy', query=u'Timestamp=2016-05-04T03%3A33%3A02Z&SignatureMethod=HmacSHA256&AWSAccessKeyId=69c5f5fc884f4e3a860d138fa0f854ce&SignatureVersion=2&Signature=o%2BSugdhZhPBnUrBlFo3Kx2bZuHmCP2l1J9%2BIVZ55vIU%3D', fragment='') because Remaining as alarm due to 1 samples outside threshold, most recent: 89.1756234322. request-id: req-2b6757d3-222f-4d04-a6af-74641aa1a4eb 

----> heat-api-cfn.log

2016-05-05 01:01:02.988 25610 INFO heat.api.aws.ec2token [-] Checking AWS credentials..
2016-05-05 01:01:02.989 25610 INFO heat.api.aws.ec2token [-] AWS credentials found, checking against keystone.
2016-05-05 01:01:02.991 25610 INFO heat.api.aws.ec2token [-] Authenticating with http://controller:5000/ec2tokens
2016-05-05 01:01:03.002 25610 INFO heat.api.aws.ec2token [-] AWS authentication failure.
2016-05-05 01:02:02.833 25610 INFO heat.api.aws.ec2token [-] Checking AWS credentials..
2016-05-05 01:02:02.835 25610 INFO heat.api.aws.ec2token [-] AWS credentials found, checking against keystone.
2016-05-05 01:02:02.837 25610 INFO heat.api.aws.ec2token [-] Authenticating with http://controller:5000/ec2tokens
2016-05-05 01:02:02.847 25610 INFO heat.api.aws.ec2token [-] AWS authentication failure.

Regards,

Igor

-- 
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:
  Fix Committed
Status in heat:
  Fix Released
Status in heat package in Ubuntu:
  Invalid
Status in heat source package in Wily:
  Fix Released

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