This is non-related to the working process issue - that's because during the OS the installation alarm evaluator starts before keystone begins actually working - that leads to the no auth passed in the https://github.com/openstack/ceilometer/blob/master/ceilometer/alarm/service.py#L130 that's called from the start method as a periodic task. That seems to be fixed with the alarm evaluator started *after* the keystone.
This is non-related to the working process issue - that's because during the OS the installation alarm evaluator starts before keystone begins actually working - that leads to the no auth passed in the https:/ /github. com/openstack/ ceilometer/ blob/master/ ceilometer/ alarm/service. py#L130 that's called from the start method as a periodic task. That seems to be fixed with the alarm evaluator started *after* the keystone.