You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We deployed a simple app with a single VanillaSoftwareProcess entity, but gave it an incorrect location (misspelt aws region name). As expected it failed to come up.
However, I only looked at this a couple of days later - by which time the tasks had been deleted (default I believe is to keep for 24 hours). The web-console showed in the summary tab of the application the following message:
The entity appears to have failed externally.
No Brooklyn-managed task failures reported. For more information, investigate sensors and streams on recent activity, as well as external systems and logs where necessary.
However, looking in the log it is clear that start() failed to provision the VM.
Presumably this message is based on whether there are any tasks currently existing for this entity, and what errors those show. If you refresh after those tasks have been deleted then it gets the summary wrong. I'd want this summary to be correct (so us not to throw away the fact there was an error at the point of effector invocation).
The text was updated successfully, but these errors were encountered:
We deployed a simple app with a single VanillaSoftwareProcess entity, but gave it an incorrect location (misspelt aws region name). As expected it failed to come up.
However, I only looked at this a couple of days later - by which time the tasks had been deleted (default I believe is to keep for 24 hours). The web-console showed in the summary tab of the application the following message:
However, looking in the log it is clear that start() failed to provision the VM.
Presumably this message is based on whether there are any tasks currently existing for this entity, and what errors those show. If you refresh after those tasks have been deleted then it gets the summary wrong. I'd want this summary to be correct (so us not to throw away the fact there was an error at the point of effector invocation).
The text was updated successfully, but these errors were encountered: