Can we please reconsider the severity of this bug? This makes trove integration into existing clouds with non-integer flavor IDs impossible, and this happens to be the case in some cases when deploying Trove + Ironic via Devstack causing Tempest breakage.
Can we please reconsider the severity of this bug? This makes trove integration into existing clouds with non-integer flavor IDs impossible, and this happens to be the case in some cases when deploying Trove + Ironic via Devstack causing Tempest breakage.