Re: [openstack-dev] [Ceilometer][wsme][pecan] Need help for ceilometer havana alarm issue
thank you very much seems I should search the launchpad more carefully On Thu, Mar 6, 2014 at 3:37 PM, Mehdi Abaakouk wrote: > Hi, > > On Thu, Mar 06, 2014 at 10:44:25AM +0800, ZhiQiang Fan wrote: > > I already check the stable/havana and master branch via devstack, the > > problem is still in havana, but master branch is not affected > > > > I think it is important to fix it for havana too, since some high level > > application may depends on the returned faultstring. Currently, I'm not > > sure mater branch fix it in pecan or wsme module, or in ceilometer itself > > > > Is there anyone can help with this problem? > > This is a duplicate bug of > https://bugs.launchpad.net/ceilometer/+bug/1260398 > > This one have already been fixed, I have marked havana as affected, to > think about it if we cut a new havana version. > > Feel free to prepare the backport. > > Regards, > > -- > Mehdi Abaakouk > mail: sil...@sileht.net > irc: sileht > > ___ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > -- blog: zqfan.github.com git: github.com/zqfan ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Ceilometer][wsme][pecan] Need help for ceilometer havana alarm issue
Hi, On Thu, Mar 06, 2014 at 10:44:25AM +0800, ZhiQiang Fan wrote: > I already check the stable/havana and master branch via devstack, the > problem is still in havana, but master branch is not affected > > I think it is important to fix it for havana too, since some high level > application may depends on the returned faultstring. Currently, I'm not > sure mater branch fix it in pecan or wsme module, or in ceilometer itself > > Is there anyone can help with this problem? This is a duplicate bug of https://bugs.launchpad.net/ceilometer/+bug/1260398 This one have already been fixed, I have marked havana as affected, to think about it if we cut a new havana version. Feel free to prepare the backport. Regards, -- Mehdi Abaakouk mail: sil...@sileht.net irc: sileht signature.asc Description: Digital signature ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Ceilometer][wsme][pecan] Need help for ceilometer havana alarm issue
I already check the stable/havana and master branch via devstack, the problem is still in havana, but master branch is not affected I think it is important to fix it for havana too, since some high level application may depends on the returned faultstring. Currently, I'm not sure mater branch fix it in pecan or wsme module, or in ceilometer itself Is there anyone can help with this problem? thanks On Tue, Feb 18, 2014 at 9:09 AM, ZhiQiang Fan wrote: > Hi, > > When I try to figure out the root cause of bug[1], I found that once > wsme.exc.ClientSideError is triggerd when create an alarm, assume the > faultstring is x, then if next http trigger a EntityNotFound(Exception) > will get http response with faultstring equal to x. > > I trace the calling stack with a lot log, and the last log I got is in > wsmeext.pecan.wsexpose, which showes that the dict which contains the > faultstring is correct, it seems the problem occurs in formatting http > response. > > env info: > os: sles 11 sp3, ubuntu 12.04.3 > ceilometer: 2013.2.2, 2013.2.1 > wsme: cannot know, checked the egginfo and __init__ but got nothing > pecan: forget... > > Please help, any information will be appreciated. > > Thanks! > > [1]: https://bugs.launchpad.net/ceilometer/+bug/1280036 > -- blog: zqfan.github.com git: github.com/zqfan ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [Ceilometer][wsme][pecan] Need help for ceilometer havana alarm issue
Hi, When I try to figure out the root cause of bug[1], I found that once wsme.exc.ClientSideError is triggerd when create an alarm, assume the faultstring is x, then if next http trigger a EntityNotFound(Exception) will get http response with faultstring equal to x. I trace the calling stack with a lot log, and the last log I got is in wsmeext.pecan.wsexpose, which showes that the dict which contains the faultstring is correct, it seems the problem occurs in formatting http response. env info: os: sles 11 sp3, ubuntu 12.04.3 ceilometer: 2013.2.2, 2013.2.1 wsme: cannot know, checked the egginfo and __init__ but got nothing pecan: forget... Please help, any information will be appreciated. Thanks! [1]: https://bugs.launchpad.net/ceilometer/+bug/1280036 ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev