Comment 30 for bug 1525800

Revision history for this message
Igor Meneguitte Ávila (igoravila) wrote :

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