OpenStack Heat

Bug #1346755
Comment #6

Comment 6 for bug 1346755

Revision history for this message

Venu Murthy (venu-murthy) wrote on 2014-07-25: Re: [Bug 1346755] Re: Wrong Logging level for "WARNING heat.engine.service [-] Stack create failed, status FAILED"

OK, in that case I think what Clint proposed is good to go with, i.e. to
reduce the log level of some informative logs to Info level.
The bottom line is, the current logging level is a little mixed up and it
will need to be relooked into and set appropriately.

Best regards,
Venu

[image: ThoughtWorks] <http://www.thoughtworks.com/>
---
*“Excellence is never an accident. It is always the result of high
intention, sincere effort, and intelligent execution.... ― Aristotle*

On Thu, Jul 24, 2014 at 6:56 PM, Steven Hardy <email address hidden> wrote:

> > deserves the level of being a Fatal or at least an Error level
>
> Again, users can't see logs, so as both Clint and I have now said, even
> a warning level log is too severe, it should probably be reduced to info
> level.
>
> The user-visible status is that available via heat event-list <stack>,
> and heat stack-show <stack>, so if that is not providing sufficient
> information as to the reason for the failure we should fix that - users
> can't see logs, so increasing the log level of the engine log message
> doesn't help (non developer) users at all.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1346755
>
> Title:
> Wrong Logging level for "WARNING heat.engine.service [-] Stack create
> failed, status FAILED"
>
> Status in Orchestration API (Heat):
> Incomplete
>
> Bug description:
> Hello!
>
> The log level for a critical error such as "heat.engine.service [-]
> Stack create failed, status FAILED" is set to Warning State currently.
>
> But looking at the severity of the issue, i.e. the entire stack fails
> creation, no matter how many other resources have spun up well, one
> such failure is as good as the stack not being created and not being
> available.
>
> Taking the definitions of log level from here,
> http://stackoverflow.com/questions/2031163/when-to-use-log-level-warn-
> vs-error
>
> this error should fall in the Error or Fatal category!
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/heat/+bug/1346755/+subscriptions
>

Best regards,
Venu

[image: ThoughtWorks] <http://www.thoughtworks.com/>
---
*“Excellence is never an accident. It is always the result of high
intention, sincere effort, and intelligent execution.... ― Aristotle*

On Thu, Jul 24, 2014 at 6:56 PM, Steven Hardy <shardy@redhat.com> wrote:

> > deserves the level of being a Fatal or at least an Error level
>
> Again, users can't see logs, so as both Clint and I have now said, even
> a warning level log is too severe, it should probably be reduced to info
> level.
>
> The user-visible status is that available via heat event-list <stack>,
> and heat stack-show <stack>, so if that is not providing sufficient
> information as to the reason for the failure we should fix that - users
> can't see logs, so increasing the log level of the engine log message
> doesn't help (non developer) users at all.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1346755
>
> Title:
>   Wrong Logging level for "WARNING heat.engine.service [-] Stack create
>   failed, status FAILED"
>
> Status in Orchestration API (Heat):
>   Incomplete
>
> Bug description:
>   Hello!
>
>   The log level for a critical error such as "heat.engine.service [-]
>   Stack create failed, status FAILED" is set to Warning State currently.
>
>   But looking at the severity of the issue, i.e. the entire stack fails
>   creation, no matter how many other resources have spun up well, one
>   such failure is as good as the stack not being created and not being
>   available.
>
>   Taking the definitions of log level from here,
>   http://stackoverflow.com/questions/2031163/when-to-use-log-level-warn-
>   vs-error
>
>   this error should fall in the Error or Fatal category!
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/heat/+bug/1346755/+subscriptions
>