cloud/bmaas/bmdb: correctly handle installation report
Previously we ignored the result of an installation report.
The bmdb does now store the result and correctly triggers
a recovery flow of the installation fails.
Change-Id: Ie8445cf9178ba84c6362b61ef8fa47208ab690be
Reviewed-on: https://review.monogon.dev/c/monogon/+/1865
Reviewed-by: Serge Bazanski <serge@monogon.tech>
Tested-by: Jenkins CI
diff --git a/cloud/bmaas/scruffy/hw_stats_test.go b/cloud/bmaas/scruffy/hw_stats_test.go
index ffb572c..dbcab2d 100644
--- a/cloud/bmaas/scruffy/hw_stats_test.go
+++ b/cloud/bmaas/scruffy/hw_stats_test.go
@@ -10,9 +10,10 @@
"google.golang.org/protobuf/proto"
aapi "source.monogon.dev/cloud/agent/api"
+ "source.monogon.dev/cloud/bmaas/server/api"
+
"source.monogon.dev/cloud/bmaas/bmdb"
"source.monogon.dev/cloud/bmaas/bmdb/model"
- "source.monogon.dev/cloud/bmaas/server/api"
"source.monogon.dev/cloud/lib/component"
)
@@ -197,8 +198,9 @@
}
if m.installationReportGeneration != nil {
err = q.MachineSetOSInstallationReport(ctx, model.MachineSetOSInstallationReportParams{
- MachineID: mach.MachineID,
- Generation: *m.installationReportGeneration,
+ MachineID: mach.MachineID,
+ Generation: *m.installationReportGeneration,
+ OsInstallationResult: model.MachineOsInstallationResultSuccess,
})
if err != nil {
return err