Complete node3 NVMe migration

- Update NVME-MIGRATION.md: all nodes now fully migrated
- Add v1.1.7 to CHANGELOG with fixes applied:
  - K3s server crash fix (empty node-passwd file)
  - Longhorn manager fix (install open-iscsi on node3)

Author: jfreed-dev

CHANGELOG.md

@@ -5,6 +5,21 @@ All notable changes to this project will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [1.1.7] - 2025-12-26
+
+### Changed
+
+- Completed node3 NVMe boot migration
+  - Reflashed with fresh Armbian image via BMC
+  - Migrated to NVMe boot (50G root + 415G Longhorn)
+  - Re-registered with K3s cluster
+  - All 4 nodes now fully operational on NVMe
+
+### Fixed
+
+- K3s server crash on node1 caused by empty node-passwd file
+- Longhorn manager crash on node3 (missing open-iscsi package)
+
 ## [1.1.6] - 2025-12-26
 
 ### Added
@@ -121,6 +136,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 - Comprehensive installation guide (INSTALL.md)
 - Implementation documentation (docs/IMPLEMENTATION.md)
 
+[1.1.7]: https://github.com/jfreed-dev/turing-ansible-cluster/compare/v1.1.6...v1.1.7
 [1.1.6]: https://github.com/jfreed-dev/turing-ansible-cluster/compare/v1.1.5...v1.1.6
 [1.1.5]: https://github.com/jfreed-dev/turing-ansible-cluster/compare/v1.1.4...v1.1.5
 [1.1.4]: https://github.com/jfreed-dev/turing-ansible-cluster/compare/v1.1.3...v1.1.4

docs/NVME-MIGRATION.md

@@ -296,10 +296,10 @@ node1:
 |------|-------------|------------------|----------------|
 | node1 | NVMe (50G) | NVMe (415G) | 2025-12-26 |
 | node2 | NVMe (50G) | NVMe (415G) | 2025-12-26 |
-| node3 | NVMe (50G) | NVMe (415G) | 2025-12-26* |
+| node3 | NVMe (50G) | NVMe (415G) | 2025-12-26 |
 | node4 | NVMe (50G) | NVMe (415G) | 2025-12-26 |
 
-\* Node3 requires BMC power cycle to complete migration
+All nodes successfully migrated to NVMe boot with dual-partition layout.
 
 ## Worker Node Considerations