Downgrade WARNING-level log

It's expected that when a resource completes and the traversal it was
processing is no longer active, we won't update the stack state in the
database. Therefore don't log at WARNING level for this routine event.

Change-Id: Ic901e46c251400c4eeb90a4d9ad4a97d61fb1af8
This commit is contained in:
Zane Bitter 2017-11-02 19:03:46 -04:00
parent 1d24d47e7e
commit ced6e44b85
1 changed files with 5 additions and 7 deletions

View File

@ -964,13 +964,11 @@ class Stack(collections.Mapping):
# delete, stack lock is not used, hence persist state
updated = self._persist_state()
if not updated:
# Possibly failed concurrent update
LOG.warning("Failed to set state of stack %(name)s with"
" traversal ID %(trvsl_id)s, to"
" %(action)s_%(status)s",
{'name': self.name,
'trvsl_id': self.current_traversal,
'action': action, 'status': status})
LOG.info("Stack %(name)s traversal %(trvsl_id)s no longer "
"active; not setting state to %(action)s_%(status)s",
{'name': self.name,
'trvsl_id': self.current_traversal,
'action': action, 'status': status})
return updated
# Persist state to db only if status == IN_PROGRESS