When a zero service version is returned, it means that we have no
services running for the requested binary. In that case, we should
assume the latest version available until told otherwise. This usually
happens in first-start cases, where everything is likely to be up to
date anyway.
This change addresses an issue where the version returned had been
hard-coded to 4.11 (mitaka).
Reviewed: https:/ /review. openstack. org/549737 /git.openstack. org/cgit/ openstack/ nova/commit/ ?id=b81a66b3b0b 1ce9f56280dda40 ac871132cb29f2
Committed: https:/
Submitter: Zuul
Branch: master
commit b81a66b3b0b1ce9 f56280dda40ac87 1132cb29f2
Author: git-harry <email address hidden>
Date: Mon Mar 5 10:48:28 2018 +0000
Fix version cap when no nova-compute started
When a zero service version is returned, it means that we have no
services running for the requested binary. In that case, we should
assume the latest version available until told otherwise. This usually
happens in first-start cases, where everything is likely to be up to
date anyway.
This change addresses an issue where the version returned had been
hard-coded to 4.11 (mitaka).
Change-Id: I696a8ea8adbe94 81e11407ecafd5e 47b2bd29804
Closes-bug: 1753443