This BZ is created to track yaml schema alignment with runtime.
Piotr, which version is it supposed to be included in?
The included patch is the first step, cleaning the warnings from vdsm log.
We will schedule the work on fixing the storage schema to match the code.
Tal, we need 4.0 bug for the patch, can you tweak it to make gerrit hooks happy?
Tal please see Nir's comment.
What am I testing here?
(In reply to Aharon Canan from comment #5)
> What am I testing here?
Before this patch the log was full with warnings like this:
jsonrpc.Executor/2::WARNING::2016-06-21 00:47:52,536::vdsmapi::143::SchemaCache::(_report_inconsistency) Provided value "0" not defined in AutoNumaBalancingStatus enum for Host.getCapabilities
These warnings are for vdsm developers or developers writing applications using
vdsm apis, so now they are logged only if you enable the python_warnings_enable
in [devel] section of vdsm configuration.
verivied on version:vdsm-184.108.40.206-1.el7ev.x86_64
after enabled different warnings are shown like
or deprecation warnings.
without the python_warnings_enable the only warnings that I see on logs are:
storageRefresh::DEBUG::2016-07-07 18:37:24,892::lvm::288::Storage.Misc.excCmd::(cmd) SUCCESS: <err> = ' WARNING: lvmetad is running but disabled. Restart lvmetad before enabling it!\n'; <rc> = 0
Since the problem described in this bug report should be
resolved in oVirt 4.0.1 released on July 19th 2016, it has been closed with a
resolution of CURRENT RELEASE.
For information on the release, and how to update to this release, follow the link below.
If the solution does not work for you, open a new bug report.
The patch related to this BZ only changes how we log inconsistency issues. We need to fix the schema which is not done. Reopening this BZ.
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.
Moving to low since this does not affect users. These warnings are for developers.
Also this should be scheduled to 4.1.
(In reply to Nir Soffer from comment #11)
> Moving to low since this does not affect users. These warnings are for
> Also this should be scheduled to 4.1.
Moving to 4.2 - I don't see this happening right now. Marking with High Priority so it'll be on our radar for 4.2.
Piotr, isn't this fixed in master now, after merging your latest patches?
There was few fixes but we do not know whether it was complete list of inconsistencies.
Closing in the meanwhile, unless we see some concrete item to fix.
We know that storage code is the least correct with the schema. It is enough to enable 'strict_mode' and see how many calls would fail. Please do not close it before all of the inconsistencies are fixed.