-
Notifications
You must be signed in to change notification settings - Fork 85
instance create saga should produce useful log messages #3877
Copy link
Copy link
Closed
Labels
DebuggingFor when you want better data in debugging an issue (log messages, post mortem debugging, and more)For when you want better data in debugging an issue (log messages, post mortem debugging, and more)good first issueIssues that are good for learning the codebaseIssues that are good for learning the codebasenexusRelated to nexusRelated to nexusvirtualizationPropolis Integration & VM ManagementPropolis Integration & VM Management
Milestone
Description
Metadata
Metadata
Assignees
Labels
DebuggingFor when you want better data in debugging an issue (log messages, post mortem debugging, and more)For when you want better data in debugging an issue (log messages, post mortem debugging, and more)good first issueIssues that are good for learning the codebaseIssues that are good for learning the codebasenexusRelated to nexusRelated to nexusvirtualizationPropolis Integration & VM ManagementPropolis Integration & VM Management
Type
Fields
Give feedbackNo fields configured for issues without a type.
In recent investigations of instance creation times for large instances, I found that there were nearly nothing in the nexus logs around instance creation, and was reliant only on propolis-server logs for details there. This was problematic in cases where the instance failed to be created (similar failure mode to #3417), because there was no propolis zone for me to inspect.
We should beef up the instance creation saga logging with an eye toward debuggability here.