Skip to content

Commit eefaaf3

Browse files
committed
PR feedback
1 parent 614dc3f commit eefaaf3

2 files changed

Lines changed: 5 additions & 7 deletions

File tree

  • dev-tools/reconfigurator-cli/src
  • nexus/reconfigurator/planning/src/blueprint_builder

dev-tools/reconfigurator-cli/src/main.rs

Lines changed: 5 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -783,13 +783,14 @@ fn cmd_blueprint_edit(
783783

784784
let mut new_blueprint = builder.build();
785785

786-
// We want to preserve the CockroachDB cluster settings from the parent
787-
// blueprint.
786+
// Normally `builder.build()` would construct the cockroach fingerprint
787+
// based on what we read from CRDB and put into the planning input, but
788+
// since we don't have a CRDB we had to make something up for our planning
789+
// input's CRDB fingerprint. In the absense of a better alternative, we'll
790+
// just copy our parent's CRDB fingerprint and carry it forward.
788791
new_blueprint
789792
.cockroachdb_fingerprint
790793
.clone_from(&blueprint.cockroachdb_fingerprint);
791-
new_blueprint.cockroachdb_setting_preserve_downgrade =
792-
blueprint.cockroachdb_setting_preserve_downgrade;
793794

794795
let rv = format!(
795796
"blueprint {} created from blueprint {}: {}",

nexus/reconfigurator/planning/src/blueprint_builder/builder.rs

Lines changed: 0 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -969,9 +969,6 @@ impl<'a> BlueprintBuilder<'a> {
969969
let sled_zones = self.zones.change_sled_zones(sled_id);
970970

971971
// Find the internal NTP zone and expunge it.
972-
//
973-
// TODO-cleanup Is there ever a case where we might want to do some kind
974-
// of graceful shutdown of an internal NTP zone? Seems unlikely...
975972
let mut internal_ntp_zone_id_iter = sled_zones
976973
.iter_zones(BlueprintZoneFilter::ShouldBeRunning)
977974
.filter_map(|config| {

0 commit comments

Comments
 (0)