Problem

Lazystack hard-codes Nova microversion 2.100. Features like original_name on flavors require 2.47+. On older OpenStack deployments (pre-Zed), this will cause failures with no graceful fallback.

If targeting "OpenStack operators broadly," some percentage will run older clouds.

Proposed Solution

• Detect the maximum supported microversion from the Nova API
• Use the highest available microversion up to 2.100
• Gracefully degrade features that require newer microversions (e.g., fall back to flavor ID if original_name is unavailable)
• Log a warning if running on a significantly older cloud so users know some features may be limited

Priority

Medium — not urgent for early adopters on modern clouds, but will become a blocker as the user base grows.

Context

Identified during features & usability review.