Commit b7100a4
committed
fix(compute): reuse an existing node encryption key instead of conflicting
A machine can be both a registered compute Node and a local hypervisor
pool - both provision a NodeEncryptionKey keyed by the same node uuid.
MachinePool.insert() always tried to create a fresh one unconditionally,
so registering a hypervisor on an already-provisioned node hit a
duplicate-key conflict. The key is an identity for the node, not a
specific agent process, so reuse whatever already exists instead.1 parent ba04844 commit b7100a4
1 file changed
Lines changed: 16 additions & 6 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
118 | 118 | | |
119 | 119 | | |
120 | 120 | | |
| 121 | + | |
| 122 | + | |
| 123 | + | |
| 124 | + | |
| 125 | + | |
121 | 126 | | |
122 | | - | |
123 | | - | |
124 | | - | |
125 | | - | |
126 | | - | |
| 127 | + | |
| 128 | + | |
| 129 | + | |
127 | 130 | | |
128 | | - | |
| 131 | + | |
| 132 | + | |
| 133 | + | |
| 134 | + | |
| 135 | + | |
| 136 | + | |
| 137 | + | |
| 138 | + | |
129 | 139 | | |
130 | 140 | | |
131 | 141 | | |
| |||
0 commit comments