Red Hat Bugzilla – Bug 1289508
HostMaxSupportedClusterVersion shouldn't be read from vds.
Last modified: 2016-02-10 14:44:36 EST
Description of problem:
UI uses org.ovirt.engine.ui.uicommonweb.models.hosts.network.NetworkOperationFactory#getHostMaxSupportedClusterVersion() to figure out max supported cluster version. This version number is taken from host setting. However if such version does not exist (yet?) in org.ovirt.engine.core.compat.Version, vdc_option values will not be obtained from GetConfigurationValuesQuery and not stored in org.ovirt.engine.ui.uicommonweb.dataprovider.AsyncDataProvider#cachedConfigValuesPreConvert and UI code will fail on NPE.
Version-Release number of selected component (if applicable):
100% if host and engine is out of sync with max supported version, otherwise 0%
Steps to Reproduce:
This resulted from VDSM adding support for 4.0 and just after few hours the engine side patch that adds support for 4.0 merged
Maybe we should always take the max version from the engine side since we always merge first the VDSM side supporting a new version and only then add the engine side support
If the issue is only relevant in this use-case, then it isn't interesting.
Will it happen in other use-cases?
this can happens anywhere, where versions aren't in sync — I don't know if there can be (theoretically) customer running not just equal versions of engine/vdsm. If not, this can probably happen only during merging patches which sets vdsm/engine to higher versions.
(In reply to Oved Ourfali from comment #2)
> If the issue is only relevant in this use-case, then it isn't interesting.
> Will it happen in other use-cases?
AFAIK this can happen only in development when the VDSM patch supporting version x+1 is merged and the engine is still in version x
(In reply to Eli Mesika from comment #4)
> (In reply to Oved Ourfali from comment #2)
> > If the issue is only relevant in this use-case, then it isn't interesting.
> > Will it happen in other use-cases?
> AFAIK this can happen only in development when the VDSM patch supporting
> version x+1 is merged and the engine is still in version x
If that's the only case then I'm closing as NOTABUG.