Commit fd0673a
authored
openvmm_entry: shut down mesh cleanly on worker launch failure (microsoft#3299)
When the worker fails to launch, the VmmMesh was dropped without calling
shutdown(), causing the child mesh host process to spew connection-reset
errors and span-close logs to stderr after the actual error message.
Ensure mesh.shutdown() is always called on the error path so the user
sees a clean error and nothing else.1 parent f9d66a7 commit fd0673a
1 file changed
Lines changed: 20 additions & 7 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
2064 | 2064 | | |
2065 | 2065 | | |
2066 | 2066 | | |
2067 | | - | |
2068 | | - | |
2069 | | - | |
2070 | | - | |
| 2067 | + | |
2071 | 2068 | | |
2072 | 2069 | | |
2073 | 2070 | | |
| |||
2079 | 2076 | | |
2080 | 2077 | | |
2081 | 2078 | | |
2082 | | - | |
2083 | | - | |
| 2079 | + | |
| 2080 | + | |
| 2081 | + | |
| 2082 | + | |
| 2083 | + | |
| 2084 | + | |
| 2085 | + | |
| 2086 | + | |
| 2087 | + | |
| 2088 | + | |
| 2089 | + | |
| 2090 | + | |
| 2091 | + | |
| 2092 | + | |
| 2093 | + | |
| 2094 | + | |
| 2095 | + | |
| 2096 | + | |
2084 | 2097 | | |
2085 | 2098 | | |
2086 | 2099 | | |
| |||
2215 | 2228 | | |
2216 | 2229 | | |
2217 | 2230 | | |
2218 | | - | |
| 2231 | + | |
2219 | 2232 | | |
2220 | 2233 | | |
2221 | 2234 | | |
| |||
0 commit comments