May 2016 - Devel - oVirt List Archives

Re: [ovirt-devel] [VDSM] Excessive warnings in vdsm log
by Nir Soffer 17 May '16

17 May '16

The best way is to use warnings.warn instead of logging.warning - we already using this for similar stuf, and we have a configuration option ti enabke the warnings in the logs. Nir בתאריך 17 במאי 2016 11:33 לפנה״צ,‏ "Martin Sivak" <msivak(a)redhat.com> כתב: Can't we just configure the logging level for the specific logger? That is why we use them. Keep the logging, but change the default for schemaapi to ERROR for now. Martin On Tue, May 17, 2016 at 8:47 AM, Yaniv Kaul <ykaul(a)redhat.com> wrote: > > > On Tue, May 17, 2016 at 9:44 AM, Piotr Kliczewski <pkliczew(a)redhat.com> > wrote: >> >> Nir, >> >> The warnings were added to annoy people so we could keep the schema align >> with the code. >> I think that we should use this opportunity to push fixes instead of >> disabling it. > > > I agree to the end goal, but I don't think this specific method would work. > I much rather we'll do a concentrated effort to drastically reduce those - > and I don't think right now is the best time for it (a bit late for 4.0) > Y. > >> >> Thanks, >> Piotr >> >> On Mon, May 16, 2016 at 10:09 PM, Nir Soffer <nsoffer(a)redhat.com> wrote: >>> >>> Hi all, >>> >>> Since data verification patches were merged, vdsm logs is spammed with >>> useless warnings (see bellow). >>> >>> This spam make it harder to debug vdsm. >>> >>> Please add configuration variable to enable this warnings, and make >>> them disabled by default. >>> >>> Thanks, >>> Nir >>> >>> ---- >>> jsonrpc.Executor/0::WARNING::2016-05-16 >>> 23:05:21,719::schemaapi::140::SchemaCache::(_report_inconsistency) >>> Following parameters ['ksmMergeAcrossNodes', 'haStats'] were not >>> recognized >>> jsonrpc.Executor/0::WARNING::2016-05-16 >>> 23:05:21,720::schemaapi::140::SchemaCache::(_report_inconsistency) >>> Parameter cpuUserVdsmd is not float type >>> jsonrpc.Executor/0::WARNING::2016-05-16 >>> 23:05:21,720::schemaapi::140::SchemaCache::(_report_inconsistency) >>> Parameter rxRate is not float type >>> jsonrpc.Executor/0::WARNING::2016-05-16 >>> 23:05:21,720::schemaapi::140::SchemaCache::(_report_inconsistency) >>> Parameter cpuLoad is not float type >>> jsonrpc.Executor/0::WARNING::2016-05-16 >>> 23:05:21,720::schemaapi::140::SchemaCache::(_report_inconsistency) >>> Parameter memUsed is not uint type >>> jsonrpc.Executor/0::WARNING::2016-05-16 >>> 23:05:21,720::schemaapi::140::SchemaCache::(_report_inconsistency) >>> Parameter cpuIdle is not float type >>> jsonrpc.Executor/0::WARNING::2016-05-16 >>> 23:05:21,721::schemaapi::140::SchemaCache::(_report_inconsistency) >>> Parameter txRate is not float type >>> jsonrpc.Executor/0::WARNING::2016-05-16 >>> 23:05:21,721::schemaapi::140::SchemaCache::(_report_inconsistency) >>> Parameter txDropped is not uint type >>> jsonrpc.Executor/0::WARNING::2016-05-16 >>> 23:05:21,721::schemaapi::140::SchemaCache::(_report_inconsistency) >>> Parameter elapsedTime is not uint type >>> jsonrpc.Executor/0::WARNING::2016-05-16 >>> 23:05:21,721::schemaapi::140::SchemaCache::(_report_inconsistency) >>> Parameter netConfigDirty is not boolean type >>> jsonrpc.Executor/0::WARNING::2016-05-16 >>> 23:05:21,721::schemaapi::140::SchemaCache::(_report_inconsistency) >>> Parameter rxErrors is not uint type >>> jsonrpc.Executor/0::WARNING::2016-05-16 >>> 23:05:21,721::schemaapi::140::SchemaCache::(_report_inconsistency) >>> Parameter rxRate is not float type >>> jsonrpc.Executor/0::WARNING::2016-05-16 >>> 23:05:21,722::schemaapi::140::SchemaCache::(_report_inconsistency) >>> Parameter rx is not uint type >>> jsonrpc.Executor/0::WARNING::2016-05-16 >>> 23:05:21,722::schemaapi::140::SchemaCache::(_report_inconsistency) >>> Parameter txDropped is not uint type >>> jsonrpc.Executor/0::WARNING::2016-05-16 >>> 23:05:21,722::schemaapi::140::SchemaCache::(_report_inconsistency) >>> Parameter txErrors is not uint type >>> jsonrpc.Executor/0::WARNING::2016-05-16 >>> 23:05:21,722::schemaapi::140::SchemaCache::(_report_inconsistency) >>> Parameter txRate is not float type >>> jsonrpc.Executor/0::WARNING::2016-05-16 >>> 23:05:21,722::schemaapi::140::SchemaCache::(_report_inconsistency) >>> Parameter speed is not uint type >>> jsonrpc.Executor/0::WARNING::2016-05-16 >>> 23:05:21,723::schemaapi::140::SchemaCache::(_report_inconsistency) >>> Parameter tx is not uint type >>> jsonrpc.Executor/0::WARNING::2016-05-16 >>> 23:05:21,723::schemaapi::140::SchemaCache::(_report_inconsistency) >>> Parameter rxDropped is not uint type >>> jsonrpc.Executor/0::WARNING::2016-05-16 >>> 23:05:21,723::schemaapi::140::SchemaCache::(_report_inconsistency) >>> Parameter rxErrors is not uint type >>> jsonrpc.Executor/0::WARNING::2016-05-16 >>> 23:05:21,723::schemaapi::140::SchemaCache::(_report_inconsistency) >>> Parameter rxRate is not float type >>> jsonrpc.Executor/0::WARNING::2016-05-16 >>> 23:05:21,723::schemaapi::140::SchemaCache::(_report_inconsistency) >>> Parameter rx is not uint type >>> jsonrpc.Executor/0::WARNING::2016-05-16 >>> 23:05:21,723::schemaapi::140::SchemaCache::(_report_inconsistency) >>> Parameter txDropped is not uint type >>> jsonrpc.Executor/0::WARNING::2016-05-16 >>> 23:05:21,724::schemaapi::140::SchemaCache::(_report_inconsistency) >>> Parameter txErrors is not uint type >>> jsonrpc.Executor/0::WARNING::2016-05-16 >>> 23:05:21,724::schemaapi::140::SchemaCache::(_report_inconsistency) >>> Parameter txRate is not float type >>> jsonrpc.Executor/0::WARNING::2016-05-16 >>> 23:05:21,724::schemaapi::140::SchemaCache::(_report_inconsistency) >>> Parameter speed is not uint type >>> jsonrpc.Executor/0::WARNING::2016-05-16 >>> 23:05:21,724::schemaapi::140::SchemaCache::(_report_inconsistency) >>> Parameter tx is not uint type >>> jsonrpc.Executor/0::WARNING::2016-05-16 >>> 23:05:21,724::schemaapi::140::SchemaCache::(_report_inconsistency) >>> Parameter rxDropped is not uint type >>> jsonrpc.Executor/0::WARNING::2016-05-16 >>> 23:05:21,725::schemaapi::140::SchemaCache::(_report_inconsistency) >>> Parameter rxErrors is not uint type >>> jsonrpc.Executor/0::WARNING::2016-05-16 >>> 23:05:21,725::schemaapi::140::SchemaCache::(_report_inconsistency) >>> Parameter rxRate is not float type >>> jsonrpc.Executor/0::WARNING::2016-05-16 >>> 23:05:21,725::schemaapi::140::SchemaCache::(_report_inconsistency) >>> Parameter rx is not uint type >>> jsonrpc.Executor/0::WARNING::2016-05-16 >>> 23:05:21,725::schemaapi::140::SchemaCache::(_report_inconsistency) >>> Parameter txDropped is not uint type >>> jsonrpc.Executor/0::WARNING::2016-05-16 >>> 23:05:21,725::schemaapi::140::SchemaCache::(_report_inconsistency) >>> Parameter txErrors is not uint type >>> jsonrpc.Executor/0::WARNING::2016-05-16 >>> 23:05:21,725::schemaapi::140::SchemaCache::(_report_inconsistency) >>> Parameter txRate is not float type >>> jsonrpc.Executor/0::WARNING::2016-05-16 >>> 23:05:21,726::schemaapi::140::SchemaCache::(_report_inconsistency) >>> Parameter speed is not uint type >>> jsonrpc.Executor/0::WARNING::2016-05-16 >>> 23:05:21,726::schemaapi::140::SchemaCache::(_report_inconsistency) >>> Parameter tx is not uint type >>> jsonrpc.Executor/0::WARNING::2016-05-16 >>> 23:05:21,726::schemaapi::140::SchemaCache::(_report_inconsistency) >>> Parameter rxDropped is not uint type >>> jsonrpc.Executor/0::WARNING::2016-05-16 >>> 23:05:21,726::schemaapi::140::SchemaCache::(_report_inconsistency) >>> Parameter rxErrors is not uint type >>> jsonrpc.Executor/0::WARNING::2016-05-16 >>> 23:05:21,726::schemaapi::140::SchemaCache::(_report_inconsistency) >>> Parameter rxRate is not float type >>> jsonrpc.Executor/0::WARNING::2016-05-16 >>> 23:05:21,727::schemaapi::140::SchemaCache::(_report_inconsistency) >>> Parameter rx is not uint type >>> jsonrpc.Executor/0::WARNING::2016-05-16 >>> 23:05:21,727::schemaapi::140::SchemaCache::(_report_inconsistency) >>> Parameter txDropped is not uint type >>> jsonrpc.Executor/0::WARNING::2016-05-16 >>> 23:05:21,727::schemaapi::140::SchemaCache::(_report_inconsistency) >>> Parameter txErrors is not uint type >>> jsonrpc.Executor/0::WARNING::2016-05-16 >>> 23:05:21,727::schemaapi::140::SchemaCache::(_report_inconsistency) >>> Parameter txRate is not float type >>> jsonrpc.Executor/0::WARNING::2016-05-16 >>> 23:05:21,727::schemaapi::140::SchemaCache::(_report_inconsistency) >>> Parameter speed is not uint type >>> jsonrpc.Executor/0::WARNING::2016-05-16 >>> 23:05:21,727::schemaapi::140::SchemaCache::(_report_inconsistency) >>> Parameter tx is not uint type >>> jsonrpc.Executor/0::WARNING::2016-05-16 >>> 23:05:21,728::schemaapi::140::SchemaCache::(_report_inconsistency) >>> Parameter rxDropped is not uint type >>> jsonrpc.Executor/0::WARNING::2016-05-16 >>> 23:05:21,728::schemaapi::140::SchemaCache::(_report_inconsistency) >>> Parameter rxErrors is not uint type >>> jsonrpc.Executor/0::WARNING::2016-05-16 >>> 23:05:21,728::schemaapi::140::SchemaCache::(_report_inconsistency) >>> Parameter rxRate is not float type >>> jsonrpc.Executor/0::WARNING::2016-05-16 >>> 23:05:21,728::schemaapi::140::SchemaCache::(_report_inconsistency) >>> Parameter rx is not uint type >>> jsonrpc.Executor/0::WARNING::2016-05-16 >>> 23:05:21,728::schemaapi::140::SchemaCache::(_report_inconsistency) >>> Parameter txDropped is not uint type >>> jsonrpc.Executor/0::WARNING::2016-05-16 >>> 23:05:21,728::schemaapi::140::SchemaCache::(_report_inconsistency) >>> Parameter txErrors is not uint type >>> jsonrpc.Executor/0::WARNING::2016-05-16 >>> 23:05:21,729::schemaapi::140::SchemaCache::(_report_inconsistency) >>> Parameter txRate is not float type >>> jsonrpc.Executor/0::WARNING::2016-05-16 >>> 23:05:21,729::schemaapi::140::SchemaCache::(_report_inconsistency) >>> Parameter speed is not uint type >>> jsonrpc.Executor/0::WARNING::2016-05-16 >>> 23:05:21,729::schemaapi::140::SchemaCache::(_report_inconsistency) >>> Parameter tx is not uint type >>> jsonrpc.Executor/0::WARNING::2016-05-16 >>> 23:05:21,729::schemaapi::140::SchemaCache::(_report_inconsistency) >>> Parameter rxDropped is not uint type >>> jsonrpc.Executor/0::WARNING::2016-05-16 >>> 23:05:21,729::schemaapi::140::SchemaCache::(_report_inconsistency) >>> Parameter rxErrors is not uint type >>> jsonrpc.Executor/0::WARNING::2016-05-16 >>> 23:05:21,730::schemaapi::140::SchemaCache::(_report_inconsistency) >>> Parameter rxRate is not float type >>> jsonrpc.Executor/0::WARNING::2016-05-16 >>> 23:05:21,730::schemaapi::140::SchemaCache::(_report_inconsistency) >>> Parameter rx is not uint type >>> jsonrpc.Executor/0::WARNING::2016-05-16 >>> 23:05:21,730::schemaapi::140::SchemaCache::(_report_inconsistency) >>> Parameter txDropped is not uint type >>> jsonrpc.Executor/0::WARNING::2016-05-16 >>> 23:05:21,730::schemaapi::140::SchemaCache::(_report_inconsistency) >>> Parameter txErrors is not uint type >>> jsonrpc.Executor/0::WARNING::2016-05-16 >>> 23:05:21,730::schemaapi::140::SchemaCache::(_report_inconsistency) >>> Parameter txRate is not float type >>> jsonrpc.Executor/0::WARNING::2016-05-16 >>> 23:05:21,730::schemaapi::140::SchemaCache::(_report_inconsistency) >>> Parameter speed is not uint type >>> jsonrpc.Executor/0::WARNING::2016-05-16 >>> 23:05:21,731::schemaapi::140::SchemaCache::(_report_inconsistency) >>> Parameter tx is not uint type >>> jsonrpc.Executor/0::WARNING::2016-05-16 >>> 23:05:21,731::schemaapi::140::SchemaCache::(_report_inconsistency) >>> Parameter rxDropped is not uint type >>> jsonrpc.Executor/0::WARNING::2016-05-16 >>> 23:05:21,731::schemaapi::140::SchemaCache::(_report_inconsistency) >>> Parameter rxErrors is not uint type >>> jsonrpc.Executor/0::WARNING::2016-05-16 >>> 23:05:21,731::schemaapi::140::SchemaCache::(_report_inconsistency) >>> Parameter rxRate is not float type >>> jsonrpc.Executor/0::WARNING::2016-05-16 >>> 23:05:21,731::schemaapi::140::SchemaCache::(_report_inconsistency) >>> Parameter rx is not uint type >>> jsonrpc.Executor/0::WARNING::2016-05-16 >>> 23:05:21,732::schemaapi::140::SchemaCache::(_report_inconsistency) >>> Parameter txDropped is not uint type >>> jsonrpc.Executor/0::WARNING::2016-05-16 >>> 23:05:21,732::schemaapi::140::SchemaCache::(_report_inconsistency) >>> Parameter txErrors is not uint type >>> jsonrpc.Executor/0::WARNING::2016-05-16 >>> 23:05:21,732::schemaapi::140::SchemaCache::(_report_inconsistency) >>> Parameter txRate is not float type >>> jsonrpc.Executor/0::WARNING::2016-05-16 >>> 23:05:21,732::schemaapi::140::SchemaCache::(_report_inconsistency) >>> Parameter speed is not uint type >>> jsonrpc.Executor/0::WARNING::2016-05-16 >>> 23:05:21,732::schemaapi::140::SchemaCache::(_report_inconsistency) >>> Parameter tx is not uint type >>> jsonrpc.Executor/0::WARNING::2016-05-16 >>> 23:05:21,733::schemaapi::140::SchemaCache::(_report_inconsistency) >>> Parameter rxDropped is not uint type >>> jsonrpc.Executor/0::WARNING::2016-05-16 >>> 23:05:21,733::schemaapi::140::SchemaCache::(_report_inconsistency) >>> Parameter cpuSys is not float type >>> jsonrpc.Executor/0::WARNING::2016-05-16 >>> 23:05:21,733::schemaapi::140::SchemaCache::(_report_inconsistency) >>> Following parameters ['nodeIndex'] were not recognized >>> jsonrpc.Executor/0::WARNING::2016-05-16 >>> 23:05:21,733::schemaapi::140::SchemaCache::(_report_inconsistency) >>> Parameter cpuSys is not float type >>> jsonrpc.Executor/0::WARNING::2016-05-16 >>> 23:05:21,733::schemaapi::140::SchemaCache::(_report_inconsistency) >>> Parameter cpuUser is not float type >>> jsonrpc.Executor/0::WARNING::2016-05-16 >>> 23:05:21,734::schemaapi::140::SchemaCache::(_report_inconsistency) >>> Required property numaNodeIndex is not provided when calling >>> Host.getStats >>> jsonrpc.Executor/0::WARNING::2016-05-16 >>> 23:05:21,734::schemaapi::140::SchemaCache::(_report_inconsistency) >>> Parameter cpuIdle is not float type >>> jsonrpc.Executor/0::WARNING::2016-05-16 >>> 23:05:21,734::schemaapi::140::SchemaCache::(_report_inconsistency) >>> Following parameters ['nodeIndex'] were not recognized >>> jsonrpc.Executor/0::WARNING::2016-05-16 >>> 23:05:21,734::schemaapi::140::SchemaCache::(_report_inconsistency) >>> Parameter cpuSys is not float type >>> jsonrpc.Executor/0::WARNING::2016-05-16 >>> 23:05:21,734::schemaapi::140::SchemaCache::(_report_inconsistency) >>> Parameter cpuUser is not float type >>> jsonrpc.Executor/0::WARNING::2016-05-16 >>> 23:05:21,735::schemaapi::140::SchemaCache::(_report_inconsistency) >>> Required property numaNodeIndex is not provided when calling >>> Host.getStats >>> jsonrpc.Executor/0::WARNING::2016-05-16 >>> 23:05:21,735::schemaapi::140::SchemaCache::(_report_inconsistency) >>> Parameter cpuIdle is not float type >>> jsonrpc.Executor/0::WARNING::2016-05-16 >>> 23:05:21,735::schemaapi::140::SchemaCache::(_report_inconsistency) >>> Following parameters ['nodeIndex'] were not recognized >>> jsonrpc.Executor/0::WARNING::2016-05-16 >>> 23:05:21,735::schemaapi::140::SchemaCache::(_report_inconsistency) >>> Parameter cpuSys is not float type >>> jsonrpc.Executor/0::WARNING::2016-05-16 >>> 23:05:21,735::schemaapi::140::SchemaCache::(_report_inconsistency) >>> Parameter cpuUser is not float type >>> jsonrpc.Executor/0::WARNING::2016-05-16 >>> 23:05:21,736::schemaapi::140::SchemaCache::(_report_inconsistency) >>> Required property numaNodeIndex is not provided when calling >>> Host.getStats >>> jsonrpc.Executor/0::WARNING::2016-05-16 >>> 23:05:21,736::schemaapi::140::SchemaCache::(_report_inconsistency) >>> Parameter cpuIdle is not float type >>> jsonrpc.Executor/0::WARNING::2016-05-16 >>> 23:05:21,736::schemaapi::140::SchemaCache::(_report_inconsistency) >>> Following parameters ['nodeIndex'] were not recognized >>> jsonrpc.Executor/0::WARNING::2016-05-16 >>> 23:05:21,736::schemaapi::140::SchemaCache::(_report_inconsistency) >>> Parameter cpuSys is not float type >>> jsonrpc.Executor/0::WARNING::2016-05-16 >>> 23:05:21,736::schemaapi::140::SchemaCache::(_report_inconsistency) >>> Parameter cpuUser is not float type >>> jsonrpc.Executor/0::WARNING::2016-05-16 >>> 23:05:21,737::schemaapi::140::SchemaCache::(_report_inconsistency) >>> Required property numaNodeIndex is not provided when calling >>> Host.getStats >>> jsonrpc.Executor/0::WARNING::2016-05-16 >>> 23:05:21,737::schemaapi::140::SchemaCache::(_report_inconsistency) >>> Parameter cpuIdle is not float type >>> jsonrpc.Executor/0::WARNING::2016-05-16 >>> 23:05:21,737::schemaapi::140::SchemaCache::(_report_inconsistency) >>> Following parameters ['nodeIndex'] were not recognized >>> jsonrpc.Executor/0::WARNING::2016-05-16 >>> 23:05:21,737::schemaapi::140::SchemaCache::(_report_inconsistency) >>> Parameter cpuSys is not float type >>> jsonrpc.Executor/0::WARNING::2016-05-16 >>> 23:05:21,737::schemaapi::140::SchemaCache::(_report_inconsistency) >>> Parameter cpuUser is not float type >>> jsonrpc.Executor/0::WARNING::2016-05-16 >>> 23:05:21,738::schemaapi::140::SchemaCache::(_report_inconsistency) >>> Required property numaNodeIndex is not provided when calling >>> Host.getStats >>> jsonrpc.Executor/0::WARNING::2016-05-16 >>> 23:05:21,738::schemaapi::140::SchemaCache::(_report_inconsistency) >>> Parameter cpuIdle is not float type >>> jsonrpc.Executor/0::WARNING::2016-05-16 >>> 23:05:21,738::schemaapi::140::SchemaCache::(_report_inconsistency) >>> Following parameters ['nodeIndex'] were not recognized >>> jsonrpc.Executor/0::WARNING::2016-05-16 >>> 23:05:21,738::schemaapi::140::SchemaCache::(_report_inconsistency) >>> Parameter cpuSys is not float type >>> jsonrpc.Executor/0::WARNING::2016-05-16 >>> 23:05:21,738::schemaapi::140::SchemaCache::(_report_inconsistency) >>> Parameter cpuUser is not float type >>> jsonrpc.Executor/0::WARNING::2016-05-16 >>> 23:05:21,739::schemaapi::140::SchemaCache::(_report_inconsistency) >>> Required property numaNodeIndex is not provided when calling >>> Host.getStats >>> jsonrpc.Executor/0::WARNING::2016-05-16 >>> 23:05:21,739::schemaapi::140::SchemaCache::(_report_inconsistency) >>> Parameter cpuIdle is not float type >>> jsonrpc.Executor/0::WARNING::2016-05-16 >>> 23:05:21,739::schemaapi::140::SchemaCache::(_report_inconsistency) >>> Following parameters ['nodeIndex'] were not recognized >>> jsonrpc.Executor/0::WARNING::2016-05-16 >>> 23:05:21,739::schemaapi::140::SchemaCache::(_report_inconsistency) >>> Parameter cpuSys is not float type >>> jsonrpc.Executor/0::WARNING::2016-05-16 >>> 23:05:21,739::schemaapi::140::SchemaCache::(_report_inconsistency) >>> Parameter cpuUser is not float type >>> jsonrpc.Executor/0::WARNING::2016-05-16 >>> 23:05:21,740::schemaapi::140::SchemaCache::(_report_inconsistency) >>> Required property numaNodeIndex is not provided when calling >>> Host.getStats >>> jsonrpc.Executor/0::WARNING::2016-05-16 >>> 23:05:21,740::schemaapi::140::SchemaCache::(_report_inconsistency) >>> Parameter cpuIdle is not float type >>> jsonrpc.Executor/0::WARNING::2016-05-16 >>> 23:05:21,740::schemaapi::140::SchemaCache::(_report_inconsistency) >>> Following parameters ['nodeIndex'] were not recognized >>> jsonrpc.Executor/0::WARNING::2016-05-16 >>> 23:05:21,740::schemaapi::140::SchemaCache::(_report_inconsistency) >>> Parameter cpuSys is not float type >>> jsonrpc.Executor/0::WARNING::2016-05-16 >>> 23:05:21,740::schemaapi::140::SchemaCache::(_report_inconsistency) >>> Parameter cpuUser is not float type >>> jsonrpc.Executor/0::WARNING::2016-05-16 >>> 23:05:21,741::schemaapi::140::SchemaCache::(_report_inconsistency) >>> Required property numaNodeIndex is not provided when calling >>> Host.getStats >>> jsonrpc.Executor/0::WARNING::2016-05-16 >>> 23:05:21,741::schemaapi::140::SchemaCache::(_report_inconsistency) >>> Parameter cpuIdle is not float type >>> jsonrpc.Executor/0::WARNING::2016-05-16 >>> 23:05:21,741::schemaapi::140::SchemaCache::(_report_inconsistency) >>> Parameter cpuUser is not float type >>> jsonrpc.Executor/0::WARNING::2016-05-16 >>> 23:05:21,741::schemaapi::140::SchemaCache::(_report_inconsistency) >>> Parameter ksmCpu is not float type >>> jsonrpc.Executor/0::WARNING::2016-05-16 >>> 23:05:21,741::schemaapi::140::SchemaCache::(_report_inconsistency) >>> Parameter memFree is not uint type >>> jsonrpc.Executor/0::WARNING::2016-05-16 >>> 23:05:21,742::schemaapi::140::SchemaCache::(_report_inconsistency) >>> Parameter lastCheck is not float type >>> jsonrpc.Executor/0::WARNING::2016-05-16 >>> 23:05:21,742::schemaapi::140::SchemaCache::(_report_inconsistency) >>> Parameter delay is not float type >>> jsonrpc.Executor/0::WARNING::2016-05-16 >>> 23:05:21,742::schemaapi::140::SchemaCache::(_report_inconsistency) >>> Parameter lastCheck is not float type >>> jsonrpc.Executor/0::WARNING::2016-05-16 >>> 23:05:21,742::schemaapi::140::SchemaCache::(_report_inconsistency) >>> Parameter delay is not float type >>> jsonrpc.Executor/0::WARNING::2016-05-16 >>> 23:05:21,742::schemaapi::140::SchemaCache::(_report_inconsistency) >>> Parameter lastCheck is not float type >>> jsonrpc.Executor/0::WARNING::2016-05-16 >>> 23:05:21,743::schemaapi::140::SchemaCache::(_report_inconsistency) >>> Parameter delay is not float type >>> jsonrpc.Executor/0::WARNING::2016-05-16 >>> 23:05:21,743::schemaapi::140::SchemaCache::(_report_inconsistency) >>> Parameter lastCheck is not float type >>> jsonrpc.Executor/0::WARNING::2016-05-16 >>> 23:05:21,743::schemaapi::140::SchemaCache::(_report_inconsistency) >>> Parameter delay is not float type >>> jsonrpc.Executor/0::WARNING::2016-05-16 >>> 23:05:21,743::schemaapi::140::SchemaCache::(_report_inconsistency) >>> Parameter lastCheck is not float type >>> jsonrpc.Executor/0::WARNING::2016-05-16 >>> 23:05:21,743::schemaapi::140::SchemaCache::(_report_inconsistency) >>> Parameter delay is not float type >>> jsonrpc.Executor/0::WARNING::2016-05-16 >>> 23:05:21,744::schemaapi::140::SchemaCache::(_report_inconsistency) >>> Parameter lastCheck is not float type >>> jsonrpc.Executor/0::WARNING::2016-05-16 >>> 23:05:21,744::schemaapi::140::SchemaCache::(_report_inconsistency) >>> Parameter delay is not float type >>> jsonrpc.Executor/0::WARNING::2016-05-16 >>> 23:05:21,744::schemaapi::140::SchemaCache::(_report_inconsistency) >>> Parameter free is not uint type >>> jsonrpc.Executor/0::WARNING::2016-05-16 >>> 23:05:21,744::schemaapi::140::SchemaCache::(_report_inconsistency) >>> Parameter free is not uint type >>> jsonrpc.Executor/0::WARNING::2016-05-16 >>> 23:05:21,744::schemaapi::140::SchemaCache::(_report_inconsistency) >>> Parameter free is not uint type >>> jsonrpc.Executor/0::WARNING::2016-05-16 >>> 23:05:21,744::schemaapi::140::SchemaCache::(_report_inconsistency) >>> Parameter free is not uint type >>> jsonrpc.Executor/0::WARNING::2016-05-16 >>> 23:05:21,745::schemaapi::140::SchemaCache::(_report_inconsistency) >>> Parameter cpuSysVdsmd is not float type >>> jsonrpc.Executor/0::WARNING::2016-05-16 >>> 23:05:21,745::schemaapi::140::SchemaCache::(_report_inconsistency) >>> Required property haStatus is not provided when calling Host.getStats >> >> >> >> _______________________________________________ >> Devel mailing list >> Devel(a)ovirt.org >> http://lists.ovirt.org/mailman/listinfo/devel > > > > _______________________________________________ > Devel mailing list > Devel(a)ovirt.org > http://lists.ovirt.org/mailman/listinfo/devel _______________________________________________ Devel mailing list Devel(a)ovirt.org http://lists.ovirt.org/mailman/listinfo/devel

1 0

FATAL: Operation aborted, found duplicate version: 04000640
by Yedidyah Bar David 17 May '16

17 May '16

Hi, Please handle. Found on jenkins [1]. [1] http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-master_el7_me… Thanks, -- Didi

2 1

Unable to login to gerrit.ovirt.org with Google OAuth2 (gerrit-oauth-provider plugin)
by Ramesh Nachimuthu 17 May '16

17 May '16

Hi, I am not able to login to gerrit.ovirt.org using Google OAuth2 (gerrit-oauth-provider plugin). It says 'Server Error'. Anyone else facing the same issue? Regards, Ramesh

2 2

[VDSM] protocoldetector test - new failure
by Nir Soffer 16 May '16

16 May '16

Hi all, This test was very stable since 3.5 - this failure smells like recent regression. 21:08:14 ====================================================================== 21:08:14 ERROR: test_reject_very_slow_client(True) (protocoldetectorTests.AcceptorTests) 21:08:14 ---------------------------------------------------------------------- 21:08:14 Traceback (most recent call last): 21:08:14 File "/home/jenkins/workspace/vdsm_master_check-patch-fc23-x86_64/vdsm/tests/protocoldetectorTests.py", line 113, in tearDown 21:08:14 self.acceptor.stop() 21:08:14 File "/home/jenkins/workspace/vdsm_master_check-patch-fc23-x86_64/vdsm/lib/vdsm/protocoldetector.py", line 212, in stop 21:08:14 self._acceptor.close() 21:08:14 File "/usr/lib64/python2.7/asyncore.py", line 407, in close 21:08:14 self.del_channel() 21:08:14 File "/home/jenkins/workspace/vdsm_master_check-patch-fc23-x86_64/vdsm/lib/yajsonrpc/betterAsyncore.py", line 137, in del_channel 21:08:14 asyncore.dispatcher.del_channel(self, map) 21:08:14 File "/usr/lib64/python2.7/asyncore.py", line 292, in del_channel 21:08:14 del map[fd] 21:08:14 KeyError: 120 21:08:14 -------------------- >> begin captured logging << -------------------- 21:08:14 vds.MultiProtocolAcceptor: INFO: Listening at 127.0.0.1:38899 21:08:14 vds.MultiProtocolAcceptor: DEBUG: Adding detector <protocoldetectorTests.Echo object at 0x7f7479512dd0> 21:08:14 vds.MultiProtocolAcceptor: DEBUG: Adding detector <protocoldetectorTests.Uppercase object at 0x7f7479512910> 21:08:14 ProtocolDetector.AcceptorImpl: INFO: Accepting connection from 127.0.0.1:33696 21:08:14 ProtocolDetector.Detector: DEBUG: Using required_size=9 21:08:14 ProtocolDetector.Detector: DEBUG: Timed out while waiting for data 21:08:14 vds.MultiProtocolAcceptor: DEBUG: Stopping Acceptor 21:08:14 --------------------- >> end captured logging << --------------------- Nir

1 0

[VDSM] new virt tests failing
by Nir Soffer 16 May '16

16 May '16

Hi all, I'm seeing these tests failing locally: ====================================================================== ERROR: test___str__ (vmMigrationTests.TestProgress) ---------------------------------------------------------------------- Traceback (most recent call last): File "/home/nsoffer/src/vdsm/tests/vmMigrationTests.py", line 166, in setUp libvirt.VIR_DOMAIN_JOB_TIME_ELAPSED: 42, AttributeError: 'module' object has no attribute 'VIR_DOMAIN_JOB_TIME_ELAPSED' ====================================================================== ERROR: test___str___without_optional_fields (vmMigrationTests.TestProgress) ---------------------------------------------------------------------- Traceback (most recent call last): File "/home/nsoffer/src/vdsm/tests/vmMigrationTests.py", line 166, in setUp libvirt.VIR_DOMAIN_JOB_TIME_ELAPSED: 42, AttributeError: 'module' object has no attribute 'VIR_DOMAIN_JOB_TIME_ELAPSED' ---------------------------------------------------------------------- And indeed, there is no such constant: >>> import libvirt >>> libvirt.VIR_DOMAIN_JOB_TIME_ELAPSED Traceback (most recent call last): File "<stdin>", line 1, in <module> AttributeError: 'module' object has no attribute 'VIR_DOMAIN_JOB_TIME_ELAPSED' $ rpm -q libvirt-python libvirt-python-1.2.13-1.fc22.x86_64 Is this old libvirt version, or the tests are broken? Cheers, Nir

2 1

[VDSM] testMethodWithIntParam (bridgeTests.BridgeTests) failing
by Nir Soffer 16 May '16

16 May '16

This tests started failing recently 23:10:06 ====================================================================== 23:10:06 ERROR: testMethodWithIntParam (bridgeTests.BridgeTests) 23:10:06 ---------------------------------------------------------------------- 23:10:06 Traceback (most recent call last): 23:10:06 File "/home/jenkins/workspace/vdsm_master_check-patch-fc23-x86_64/vdsm/tests/monkeypatch.py", line 133, in wrapper 23:10:06 return f(*args, **kw) 23:10:06 File "/home/jenkins/workspace/vdsm_master_check-patch-fc23-x86_64/vdsm/tests/bridgeTests.py", line 168, in testMethodWithIntParam 23:10:06 self.assertEqual(bridge.dispatch('VM.migrationCreate')(**params), 23:10:06 File "/home/jenkins/workspace/vdsm_master_check-patch-fc23-x86_64/vdsm/lib/vdsm/rpc/Bridge.py", line 271, in _dynamicMethod 23:10:06 raise InvalidCall(fn, methodArgs, e) 23:10:06 InvalidCall: Attempt to call function: <bound method VM.migrationCreate of <bridgeTests.VM instance at 0x7fbf3d64bef0>> with arguments: ({'vmID': '773adfc7-10d4-4e60-b700-3272ee1871f9'},) error: migrationCreate() takes exactly 3 arguments (2 given) 23:10:06 -------------------- >> begin captured logging << -------------------- 23:10:06 DynamicBridge: ERROR: TypeError raised by dispatched function 23:10:06 Traceback (most recent call last): 23:10:06 File "/home/jenkins/workspace/vdsm_master_check-patch-fc23-x86_64/vdsm/lib/vdsm/rpc/Bridge.py", line 268, in _dynamicMethod 23:10:06 result = fn(*methodArgs) 23:10:06 TypeError: migrationCreate() takes exactly 3 arguments (2 given) 23:10:06 --------------------- >> end captured logging << --------------------- I sent a patch to mark it as broken: https://gerrit.ovirt.org/57364 The issue should be resolved when https://gerrit.ovirt.org/53305/ will be merged. Dan, please take this patch until the schema change is ready. Nir

3 2

New network testing failing (netinfo move)
by Nir Soffer 15 May '16

15 May '16

Hi all, Pleas this test, need to update after netinfo package was moved: 12:56:36 ====================================================================== 12:56:36 ERROR: Failure: ImportError (No module named netinfo.addresses) 12:56:36 ---------------------------------------------------------------------- 12:56:36 Traceback (most recent call last): 12:56:36 File "/usr/lib/python2.7/site-packages/nose/loader.py", line 413, in loadTestsFromName 12:56:36 addr.filename, addr.module) 12:56:36 File "/usr/lib/python2.7/site-packages/nose/importer.py", line 47, in importFromPath 12:56:36 return self.importFromDir(dir_path, fqname) 12:56:36 File "/usr/lib/python2.7/site-packages/nose/importer.py", line 94, in importFromDir 12:56:36 mod = load_module(part_fqname, fh, filename, desc) 12:56:36 File "/home/jenkins/workspace/vdsm_master_check-patch-el7-x86_64/vdsm/tests/network/ovs_info_test.py", line 31, in <module> 12:56:36 from vdsm.network.ovs import info 12:56:36 File "/home/jenkins/workspace/vdsm_master_check-patch-el7-x86_64/vdsm/lib/vdsm/network/ovs/info.py", line 23, in <module> 12:56:36 from vdsm.netinfo.addresses import getIpAddrs, getIpInfo, is_ipv6_local_auto 12:56:36 ImportError: No module named netinfo.addresses This breaks unrelated builds: http://jenkins.ovirt.org/job/vdsm_master_check-patch-el7-x86_64/1157/console Cheers, Nir

2 1

[UI plugins] RestApiSessionAcquired is out, api.ssoToken() is in
by Vojtech Szocs 12 May '16

12 May '16

Hi everyone, we've merged a patch that aligns UI code with Engine SSO infra: https://gerrit.ovirt.org/#/c/49278/ In particular, UI code that creates & maintains REST webapp's HTTP session was removed in favor of using SSO token. **UI plugin authors take note!** The "RestApiSessionAcquired" callback was removed -- please update your UI plugins to use the new "api.ssoToken" function when making REST API requests: var xhr = new XMLHttpRequest(); xhr.open('GET', 'http://example.com/ovirt-engine/api'); xhr.setRequestHeader('Authorization', 'Bearer ' + api.ssoToken()); xhr.setRequestHeader('Accept', 'application/json'); xhr.addEventListener('load', function () { // response loaded OK, parse JSON data var data = JSON.parse(this.responseText); }); xhr.send(); While being a breaking change, this should simplify UI plugin code because: - the new "api.ssoToken" function can be called anytime, removing the need for an asynchronous callback - no need to use session-specific request headers anymore (like "Prefer: persistent-auth" and "JSESSIONID: xxx"), just use "Authorization: Bearer xxx" and you're good Please see commit msg of above mentioned patch for further details on the changes and their implications. Let me know if you have any questions or comments. Regards, Vojtech

1 0

[VDSM] Strange build requirements added lately
by Nir Soffer 12 May '16

12 May '16

Hi all, Building rpms is failing now on my development machine due to new build requirements: rpmbuild -ta \ vdsm-4.17.999.tar.gz error: Failed build dependencies: PyYAML is needed by vdsm-4.17.999-1091.git4d7d14a.fc22.x86_64 libvirt-python3 is needed by vdsm-4.17.999-1091.git4d7d14a.fc22.x86_64 mom >= 0.5.3 is needed by vdsm-4.17.999-1091.git4d7d14a.fc22.x86_64 openvswitch >= 2.0.0 is needed by vdsm-4.17.999-1091.git4d7d14a.fc22.x86_64 python3-netaddr is needed by vdsm-4.17.999-1091.git4d7d14a.fc22.x86_64 Needing a yaml package and python3-netaddr make sense, but I don't understand why we need these packages for building vdsm: - libvirt-python3 - we should not access libvirt using the tests - mom - we are not running mom on a development machine - openvswitch - we are not running this on a development machine If these are not build requirements, please remove them. Thanks, Nir

4 8

Doing a mock ovirt-engine build for epel7 on fedora 23 hangs
by Roman Mohr 11 May '16

11 May '16

Hi, My mock rpm builds hang on the line Downloading: http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-ear-plugin/2.8… Does anyone else have similar issues when building inside mock for epel7 on a fedora 23 machine?\ Best Regards, Roman

2 2

oVirt Community Newsletter: April 2016
by Brian Proffitt 09 May '16

09 May '16

Spring has sprung in the Northern Hemisphere, and oVirt dev team is preparing for the upcoming 4.0 release, even as the 3.6 tree continues. And while oVirt has taken a respite from the event extravaganzas of January and February, there's still some positive moves happening in the oVirt community. ----------------- Software Releases ----------------- oVirt 3.6.5 Final Release is now available http://lists.ovirt.org/pipermail/announce/2016-April/000247.html oVirt Live 3.6.6 First Release Candidate is now available for testing http://lists.ovirt.org/pipermail/users/2016-April/039430.html oVirt 3.6.6 Second Release Candidate is now available for testing http://lists.ovirt.org/pipermail/announce/2016-May/000251.html oVirt Node Next Beta http://lists.ovirt.org/pipermail/announce/2016-April/000250.html ---------------- In the Community ---------------- Schedule for oVirt 4.0.0 http://lists.ovirt.org/pipermail/announce/2016-April/000246.html Prepare for version 4 of oVirt API http://lists.ovirt.org/pipermail/users/2016-May/039624.html RCC adopts oVirt for Virtualization https://rcc.fsu.edu/news/rcc-adopts-ovirt-virtualization oVirt Makes Impact at ROSS'16 [Russian] http://www.pcweek.ru/foss/article/detail.php?ID=184736 ------------------------------------ Deep Dives and Technical Discussions ------------------------------------ Advanced users authentication, using Kerberos, CAS SSO and Active Directory http://www.ovirt.org/blog/2016/04/sso/ DevNation: oVirt, Uninterrupted and Integrated Virtualization http://bit.ly/1VQxRKv oVirt-Specific Aspect Languages http://ahadas.github.io/oVirt-Specifc-Aspect-Languages/ Downstream News: RHEV To Make Impact at DevNation http://bit.ly/1VQxQ9p Downstream: Scaling Up On Demand with Red Hat Enterprise Virtualization http://red.ht/1VI1HR8 -- Brian Proffitt Principal Community Analyst Open Source and Standards @TheTechScribe 574.383.9BKP

1 0

ioprocess logs
by Piotr Kliczewski 09 May '16

09 May '16

All, Whenever I see build failure on my laptop there is bunch of ioprocess logs. Can we find fix the issues? Exception AttributeError: "'NoneType' object has no attribute 'write'"Exception in thread ioprocess communication (15770) (most likely raised during interpreter shutdown): in <bound method IOProcess.__del__ of <ioprocess.IOProcess object at 0x7fa0bb84a510>> ignored Exception AttributeError: "'NoneType' object has no attribute 'wrTraceback (most recent call last): ite'" File "/usr/lib64/python2.7/threading.py", line 804, in __bootstrap_inner in <bound method IOProcess.__del__ of <ioprocess.IOProcess object at 0x7fa07f7b5b10>> ignored Exception AttributeError File "/usr/lib64/python2.7/threading.py", line 757, in run : File "/usr/lib/python2.7/site-packages/ioprocess/__init__.py", line 180, in _communicate"'NoneType' object has no attribute 'write'" in <bound method IOProcess.__del__ of <ioprocess.IOProcess object at 0x7fa07f831950>><type 'exceptions.AttributeError'>: 'NoneType' object has no attribute 'close' ignored Exception AttributeError: "'NoneType' object has no attribute 'write'" in <bound method IOProcess.__del__ of <ioprocess.IOProcess object at 0x7fa07f84fe90>> ignored Exception AttributeError: "'NoneType' object has no attribute 'write'" in <bound method IOProcess.__del__ of <ioprocess.IOProcess object at 0x7fa07f866850>> ignored Exception AttributeError: "'NoneType' object has no attribute 'write'" in <bound method IOProcess.__del__ of <ioprocess.IOProcess object at 0x7fa07f82fbd0>> ignored Exception AttributeError: "'NoneType' object has no attribute 'write'" in <bound method IOProcess.__del__ of <ioprocess.IOProcess object at 0x7fa07f7b5310>> ignored Exception AttributeError: "'NoneType' object has no attribute 'write'" in <bound method IOProcess.__del__ of <ioprocess.IOProcess object at 0x7fa0bb84a350>> ignored Exception AttributeError: "'NoneType' object has no attribute 'write'" in <bound method IOProcess.__del__ of <ioprocess.IOProcess object at 0x7fa0bb919550>> ignored Exception AttributeError: "'NoneType' object has no attribute 'write'" in <bound method IOProcess.__del__ of <ioprocess.IOProcess object at 0x7fa07f861690>> ignored Exception AttributeError: "'NoneType' object has no attribute 'write'" in <bound method IOProcess.__del__ of <ioprocess.IOProcess object at 0x7fa07f8342d0>> ignored Exception AttributeError: "'NoneType' object has no attribute 'write'" in <bound method IOProcess.__del__ of <ioprocess.IOProcess object at 0x7fa0b8491610>> ignored Exception AttributeError: "'NoneType' object has no attribute 'write'" in <bound method IOProcess.__del__ of <ioprocess.IOProcess object at 0x7fa0b8187ed0>> ignored Exception AttributeError: "'NoneType' object has no attribute 'write'" in <bound method IOProcess.__del__ of <ioprocess.IOProcess object at 0x7fa0bb800ad0>> ignored Exception AttributeError: "'NoneType' object has no attribute 'write'" in <bound method IOProcess.__del__ of <ioprocess.IOProcess object at 0x7fa07f861a10>> ignored Exception AttributeError: "'NoneType' object has no attribute 'write'" in <bound method IOProcess.__del__ of <ioprocess.IOProcess object at 0x7fa0bb791090>> ignored Exception AttributeError: "'NoneType' object has no attribute 'write'" in <bound method IOProcess.__del__ of <ioprocess.IOProcess object at 0x7fa0bb774650>> ignored Exception AttributeError: "'NoneType' object has no attribute 'write'" in <bound method IOProcess.__del__ of <ioprocess.IOProcess object at 0x7fa07f834b10>> ignored Exception AttributeError: "'NoneType' object has no attribute 'write'" in <bound method IOProcess.__del__ of <ioprocess.IOProcess object at 0x7fa07f77fb50>> ignored Exception AttributeError: "'NoneType' object has no attribute 'write'" in <bound method IOProcess.__del__ of <ioprocess.IOProcess object at 0x7fa07f84ad90>> ignored Exception AttributeError: "'NoneType' object has no attribute 'write'" in <bound method IOProcess.__del__ of <ioprocess.IOProcess object at 0x7fa07f84f690>> ignored Exception AttributeError: "'NoneType' object has no attribute 'write'" in <bound method IOProcess.__del__ of <ioprocess.IOProcess object at 0x7fa07f60f510>> ignored Exception AttributeError: "'NoneType' object has no attribute 'write'" in <bound method IOProcess.__del__ of <ioprocess.IOProcess object at 0x7fa07f84a4d0>> ignored Exception AttributeError: "'NoneType' object has no attribute 'write'" in <bound method IOProcess.__del__ of <ioprocess.IOProcess object at 0x7fa07f82f150>> ignored Exception AttributeError: "'NoneType' object has no attribute 'write'" in <bound method IOProcess.__del__ of <ioprocess.IOProcess object at 0x7fa07f831290>> ignored Thanks, Piotr

2 3

Ondra Machacek is now the main maintainer of the Python and Java SDK
by Juan Hernández 09 May '16

09 May '16

Hello, Ondra Machacek has been doing an excellent work in the new versions of the Java and Python SDKs for version 4 of the engine. As a result we have decided to appoint him as the main maintainer of these two components. Starting intermediately he will take full responsibility and ownership of version 4 of these SDKs. Regards, Juan Hernandez -- Dirección Comercial: C/Jose Bardasano Baos, 9, Edif. Gorbea 3, planta 3ºD, 28016 Madrid, Spain Inscrita en el Reg. Mercantil de Madrid – C.I.F. B82657941 - Red Hat S.L.

1 0

[ATTN] VDSM netinfo changes break hosted-engine --deploy
by Roy Golan 09 May '16

09 May '16

VDSM's commit ef992682782853a20d8f537a96ba376286ef10df moved netinfo under network folder and that break hosted-engine --deploy. It will fail with ``` # hosted-engine --deploy ***L:ERROR Internal error: No module named netinfo.cache ``` Please review the fix: https://gerrit.ovirt.org/57228 Adapt to netinfo namespace change under network [DRAFT]

1 0

Re: [ovirt-devel] [Fixed][vdsm] Failing to rename volume on merge (remove snapshot operation)
by Maor Lipchuk 08 May '16

08 May '16

On Sun, May 8, 2016 at 4:11 PM, Maor Lipchuk <mlipchuk(a)redhat.com> wrote: > > > On Sun, May 8, 2016 at 2:22 PM, Nir Soffer <nsoffer(a)redhat.com> wrote: > >> On Sun, May 8, 2016 at 12:56 PM, Maor Lipchuk <mlipchuk(a)redhat.com> >> wrote: >> > Hi, >> > >> > I've been trying to remove a single snapshot and consistently fail with >> the >> > following error (see [1]). >> > >> > Those are my steps: >> > 1. Create a VM + Disk >> > 2. Create a snapshot >> > 3. Remove the snapshot >> > >> > My VDSM is the latest (commit d7796fb8bdd5b424ecad54dc36cb58cd477b3224) >> > >> > Is there a bug open on it? or even better, fixing patches? >> > >> > [1] >> > 5b61867b-6dd4-4224-be4a-859904e3298b::DEBUG::2016-05-08 >> > 12:34:22,296::fileVolume::573::Storage.Volume::(rename) Renaming >> > /rhev/data-center/mnt/10.35.16.43:_export_data9/e562ec63-b734-4554-b8 >> > >> 2c-7fc8314c352f/images/c26b2f00-563f-4965-8bcd-e7ca8ead1625/903f5a13-f7e4-4222-bb02-303019756bb9.lease >> > to >> > /rhev/data-center/mnt/10.35.16.43: >> _export_data9/e562ec63-b734-4554-b82c-7fc8314c352f >> > >> /images/c26b2f00-563f-4965-8bcd-e7ca8ead1625/_remove_me_LGQXBkpd_903f5a13-f7e4-4222-bb02-303019756bb9.lease >> > 5b61867b-6dd4-4224-be4a-859904e3298b::ERROR::2016-05-08 >> > 12:34:22,298::image::1338::Storage.Image::(merge) can't set attribute >> > Traceback (most recent call last): >> > File "/usr/share/vdsm/storage/image.py", line 1321, in merge >> > [vols[vName] for vName in chain]) >> > File "/usr/share/vdsm/storage/image.py", line 1146, in >> _baseRawVolumeMerge >> > srcVol.rename(tmpUUID) >> > File "/usr/share/vdsm/storage/fileVolume.py", line 580, in rename >> > self._manifest.volumePath = volPath >> > AttributeError: can't set attribute >> >> I think this is a bug introduced during the sdm refactorings, and I >> also reproduced it once >> but did not have time to investigate it yet. >> >> If the code expect the replace a volume path during runtime, we should >> have a setter: >> >> @property >> def volumePath(self): >> return self._volumePath >> >> @volumePath.setter >> def volumePath(self, value): >> self._volumePath = value >> >> You can try add this to the manifest class and see if it fixes this issue. >> > > Looks like that fixes the issue. Added a patch at https://gerrit.ovirt.org/#/c/57194/1 Thanks for the help, Maor > > > >> >> Nir >> >> > 5b61867b-6dd4-4224-be4a-859904e3298b::DEBUG::2016-05-08 >> > >> 12:34:22,299::resourceManager::628::Storage.ResourceManager::(releaseResource) >> > Trying to release resource 'e562ec63-b734-4554-b82c-7fc >> > 8314c352f_imageNS.c26b2f00-563f-4965-8bcd-e7ca8ead1625' >> > 5b61867b-6dd4-4224-be4a-859904e3298b::DEBUG::2016-05-08 >> > >> 12:34:22,299::resourceManager::647::Storage.ResourceManager::(releaseResource) >> > Released resource 'e562ec63-b734-4554-b82c-7fc8314c352f >> > _imageNS.c26b2f00-563f-4965-8bcd-e7ca8ead1625' (0 active users) >> > 5b61867b-6dd4-4224-be4a-859904e3298b::DEBUG::2016-05-08 >> > >> 12:34:22,299::resourceManager::653::Storage.ResourceManager::(releaseResource) >> > Resource 'e562ec63-b734-4554-b82c-7fc8314c352f_imageNS. >> > c26b2f00-563f-4965-8bcd-e7ca8ead1625' is free, finding out if anyone is >> > waiting for it. >> > 5b61867b-6dd4-4224-be4a-859904e3298b::DEBUG::2016-05-08 >> > >> 12:34:22,299::resourceManager::628::Storage.ResourceManager::(releaseResource) >> > Trying to release resource 'e562ec63-b734-4554-b82c-7fc >> > 8314c352f_volumeNS.903f5a13-f7e4-4222-bb02-303019756bb9' >> > 5b61867b-6dd4-4224-be4a-859904e3298b::DEBUG::2016-05-08 >> > >> 12:34:22,299::resourceManager::647::Storage.ResourceManager::(releaseResource) >> > Released resource 'e562ec63-b734-4554-b82c-7fc8314c352f >> > _volumeNS.903f5a13-f7e4-4222-bb02-303019756bb9' (0 active users) >> > 5b61867b-6dd4-4224-be4a-859904e3298b::DEBUG::2016-05-08 >> > >> 12:34:22,299::resourceManager::653::Storage.ResourceManager::(releaseResource) >> > Resource 'e562ec63-b734-4554-b82c-7fc8314c352f_volumeNS >> > .903f5a13-f7e4-4222-bb02-303019756bb9' is free, finding out if anyone is >> > waiting for it. >> > 5b61867b-6dd4-4224-be4a-859904e3298b::DEBUG::2016-05-08 >> > >> 12:34:22,299::resourceManager::661::Storage.ResourceManager::(releaseResource) >> > No one is waiting for resource 'e562ec63-b734-4554-b82c >> > -7fc8314c352f_volumeNS.903f5a13-f7e4-4222-bb02-303019756bb9', Clearing >> > records. >> > 5b61867b-6dd4-4224-be4a-859904e3298b::DEBUG::2016-05-08 >> > >> 12:34:22,299::resourceManager::628::Storage.ResourceManager::(releaseResource) >> > Trying to release resource 'e562ec63-b734-4554-b82c-7fc >> > 8314c352f_volumeNS.e6d9874a-8225-44e1-9440-0a3cfd4ea7fc' >> > 5b61867b-6dd4-4224-be4a-859904e3298b::DEBUG::2016-05-08 >> > >> 12:34:22,299::resourceManager::647::Storage.ResourceManager::(releaseResource) >> > Released resource 'e562ec63-b734-4554-b82c-7fc8314c352f >> > _volumeNS.e6d9874a-8225-44e1-9440-0a3cfd4ea7fc' (0 active users) >> > 5b61867b-6dd4-4224-be4a-859904e3298b::DEBUG::2016-05-08 >> > >> 12:34:22,300::resourceManager::653::Storage.ResourceManager::(releaseResource) >> > Resource 'e562ec63-b734-4554-b82c-7fc8314c352f_volumeNS >> > .e6d9874a-8225-44e1-9440-0a3cfd4ea7fc' is free, finding out if anyone is >> > waiting for it. >> > 5b61867b-6dd4-4224-be4a-859904e3298b::DEBUG::2016-05-08 >> > >> 12:34:22,300::resourceManager::661::Storage.ResourceManager::(releaseResource) >> > No one is waiting for resource 'e562ec63-b734-4554-b82c >> > -7fc8314c352f_volumeNS.e6d9874a-8225-44e1-9440-0a3cfd4ea7fc', Clearing >> > records. >> > 5b61867b-6dd4-4224-be4a-859904e3298b::DEBUG::2016-05-08 >> > >> 12:34:22,300::resourceManager::661::Storage.ResourceManager::(releaseResource) >> > No one is waiting for resource 'e562ec63-b734-4554-b82c >> > -7fc8314c352f_imageNS.c26b2f00-563f-4965-8bcd-e7ca8ead1625', Clearing >> > records. >> > 5b61867b-6dd4-4224-be4a-859904e3298b::ERROR::2016-05-08 >> > 12:34:22,300::task::868::Storage.TaskManager.Task::(_setError) >> > Task=`5b61867b-6dd4-4224-be4a-859904e3298b`::Unexpected error >> > Traceback (most recent call last): >> > File "/usr/share/vdsm/storage/task.py", line 875, in _run >> > return fn(*args, **kargs) >> > File "/usr/share/vdsm/storage/task.py", line 334, in run >> > return self.cmd(*self.argslist, **self.argsdict) >> > File "/usr/lib/python2.7/site-packages/vdsm/storage/securable.py", >> line >> > 78, in wrapper >> > return method(self, *args, **kwargs) >> > File "/usr/share/vdsm/storage/sp.py", line 1862, in mergeSnapshots >> > sdUUID, vmUUID, imgUUID, ancestor, successor, postZero) >> > File "/usr/share/vdsm/storage/image.py", line 1339, in merge >> > : raise se.SourceImageActionError(imgUUID, sdUUID, str(e)) >> > SourceImageActionError: Error during source image manipulation: >> > "image=c26b2f00-563f-4965-8bcd-e7ca8ead1625, source >> > domain=e562ec63-b734-4554-b82c-7fc8314c352f: can't set attribute" >> > 5b61867b-6dd4-4224-be4a-859904e3298b::DEBUG::2016-05-08 >> > 12:34:22,300::task::887::Storage.TaskManager.Task::(_run) >> > Task=`5b61867b-6dd4-4224-be4a-859904e3298b`::Task._run: >> > 5b61867b-6dd4-4224-be4a-859904e3298b () {} failed - stopping task >> > 5b61867b-6dd4-4224-be4a-859904e3298b::DEBUG::2016-05-08 >> > 12:34:22,300::task::1248::Storage.TaskManager.Task::(stop) >> > Task=`5b61867b-6dd4-4224-be4a-859904e3298b`::stopping in state running >> > (force False) >> > >> > >> > >> > Regards, >> > Maor >> > >> > >> > _______________________________________________ >> > vdsm-devel mailing list >> > vdsm-devel(a)lists.fedorahosted.org >> > >> https://lists.fedorahosted.org/admin/lists/vdsm-devel@lists.fedorahosted.org >> > >> > >

1 0

Re: [ovirt-devel] [vdsm] Failing to rename volume on merge (remove snapshot operation)
by Maor Lipchuk 08 May '16

08 May '16

On Sun, May 8, 2016 at 2:22 PM, Nir Soffer <nsoffer(a)redhat.com> wrote: > On Sun, May 8, 2016 at 12:56 PM, Maor Lipchuk <mlipchuk(a)redhat.com> wrote: > > Hi, > > > > I've been trying to remove a single snapshot and consistently fail with > the > > following error (see [1]). > > > > Those are my steps: > > 1. Create a VM + Disk > > 2. Create a snapshot > > 3. Remove the snapshot > > > > My VDSM is the latest (commit d7796fb8bdd5b424ecad54dc36cb58cd477b3224) > > > > Is there a bug open on it? or even better, fixing patches? > > > > [1] > > 5b61867b-6dd4-4224-be4a-859904e3298b::DEBUG::2016-05-08 > > 12:34:22,296::fileVolume::573::Storage.Volume::(rename) Renaming > > /rhev/data-center/mnt/10.35.16.43:_export_data9/e562ec63-b734-4554-b8 > > > 2c-7fc8314c352f/images/c26b2f00-563f-4965-8bcd-e7ca8ead1625/903f5a13-f7e4-4222-bb02-303019756bb9.lease > > to > > /rhev/data-center/mnt/10.35.16.43: > _export_data9/e562ec63-b734-4554-b82c-7fc8314c352f > > > /images/c26b2f00-563f-4965-8bcd-e7ca8ead1625/_remove_me_LGQXBkpd_903f5a13-f7e4-4222-bb02-303019756bb9.lease > > 5b61867b-6dd4-4224-be4a-859904e3298b::ERROR::2016-05-08 > > 12:34:22,298::image::1338::Storage.Image::(merge) can't set attribute > > Traceback (most recent call last): > > File "/usr/share/vdsm/storage/image.py", line 1321, in merge > > [vols[vName] for vName in chain]) > > File "/usr/share/vdsm/storage/image.py", line 1146, in > _baseRawVolumeMerge > > srcVol.rename(tmpUUID) > > File "/usr/share/vdsm/storage/fileVolume.py", line 580, in rename > > self._manifest.volumePath = volPath > > AttributeError: can't set attribute > > I think this is a bug introduced during the sdm refactorings, and I > also reproduced it once > but did not have time to investigate it yet. > > If the code expect the replace a volume path during runtime, we should > have a setter: > > @property > def volumePath(self): > return self._volumePath > > @volumePath.setter > def volumePath(self, value): > self._volumePath = value > > You can try add this to the manifest class and see if it fixes this issue. > Which class is it? Where is it located? > > Nir > > > 5b61867b-6dd4-4224-be4a-859904e3298b::DEBUG::2016-05-08 > > > 12:34:22,299::resourceManager::628::Storage.ResourceManager::(releaseResource) > > Trying to release resource 'e562ec63-b734-4554-b82c-7fc > > 8314c352f_imageNS.c26b2f00-563f-4965-8bcd-e7ca8ead1625' > > 5b61867b-6dd4-4224-be4a-859904e3298b::DEBUG::2016-05-08 > > > 12:34:22,299::resourceManager::647::Storage.ResourceManager::(releaseResource) > > Released resource 'e562ec63-b734-4554-b82c-7fc8314c352f > > _imageNS.c26b2f00-563f-4965-8bcd-e7ca8ead1625' (0 active users) > > 5b61867b-6dd4-4224-be4a-859904e3298b::DEBUG::2016-05-08 > > > 12:34:22,299::resourceManager::653::Storage.ResourceManager::(releaseResource) > > Resource 'e562ec63-b734-4554-b82c-7fc8314c352f_imageNS. > > c26b2f00-563f-4965-8bcd-e7ca8ead1625' is free, finding out if anyone is > > waiting for it. > > 5b61867b-6dd4-4224-be4a-859904e3298b::DEBUG::2016-05-08 > > > 12:34:22,299::resourceManager::628::Storage.ResourceManager::(releaseResource) > > Trying to release resource 'e562ec63-b734-4554-b82c-7fc > > 8314c352f_volumeNS.903f5a13-f7e4-4222-bb02-303019756bb9' > > 5b61867b-6dd4-4224-be4a-859904e3298b::DEBUG::2016-05-08 > > > 12:34:22,299::resourceManager::647::Storage.ResourceManager::(releaseResource) > > Released resource 'e562ec63-b734-4554-b82c-7fc8314c352f > > _volumeNS.903f5a13-f7e4-4222-bb02-303019756bb9' (0 active users) > > 5b61867b-6dd4-4224-be4a-859904e3298b::DEBUG::2016-05-08 > > > 12:34:22,299::resourceManager::653::Storage.ResourceManager::(releaseResource) > > Resource 'e562ec63-b734-4554-b82c-7fc8314c352f_volumeNS > > .903f5a13-f7e4-4222-bb02-303019756bb9' is free, finding out if anyone is > > waiting for it. > > 5b61867b-6dd4-4224-be4a-859904e3298b::DEBUG::2016-05-08 > > > 12:34:22,299::resourceManager::661::Storage.ResourceManager::(releaseResource) > > No one is waiting for resource 'e562ec63-b734-4554-b82c > > -7fc8314c352f_volumeNS.903f5a13-f7e4-4222-bb02-303019756bb9', Clearing > > records. > > 5b61867b-6dd4-4224-be4a-859904e3298b::DEBUG::2016-05-08 > > > 12:34:22,299::resourceManager::628::Storage.ResourceManager::(releaseResource) > > Trying to release resource 'e562ec63-b734-4554-b82c-7fc > > 8314c352f_volumeNS.e6d9874a-8225-44e1-9440-0a3cfd4ea7fc' > > 5b61867b-6dd4-4224-be4a-859904e3298b::DEBUG::2016-05-08 > > > 12:34:22,299::resourceManager::647::Storage.ResourceManager::(releaseResource) > > Released resource 'e562ec63-b734-4554-b82c-7fc8314c352f > > _volumeNS.e6d9874a-8225-44e1-9440-0a3cfd4ea7fc' (0 active users) > > 5b61867b-6dd4-4224-be4a-859904e3298b::DEBUG::2016-05-08 > > > 12:34:22,300::resourceManager::653::Storage.ResourceManager::(releaseResource) > > Resource 'e562ec63-b734-4554-b82c-7fc8314c352f_volumeNS > > .e6d9874a-8225-44e1-9440-0a3cfd4ea7fc' is free, finding out if anyone is > > waiting for it. > > 5b61867b-6dd4-4224-be4a-859904e3298b::DEBUG::2016-05-08 > > > 12:34:22,300::resourceManager::661::Storage.ResourceManager::(releaseResource) > > No one is waiting for resource 'e562ec63-b734-4554-b82c > > -7fc8314c352f_volumeNS.e6d9874a-8225-44e1-9440-0a3cfd4ea7fc', Clearing > > records. > > 5b61867b-6dd4-4224-be4a-859904e3298b::DEBUG::2016-05-08 > > > 12:34:22,300::resourceManager::661::Storage.ResourceManager::(releaseResource) > > No one is waiting for resource 'e562ec63-b734-4554-b82c > > -7fc8314c352f_imageNS.c26b2f00-563f-4965-8bcd-e7ca8ead1625', Clearing > > records. > > 5b61867b-6dd4-4224-be4a-859904e3298b::ERROR::2016-05-08 > > 12:34:22,300::task::868::Storage.TaskManager.Task::(_setError) > > Task=`5b61867b-6dd4-4224-be4a-859904e3298b`::Unexpected error > > Traceback (most recent call last): > > File "/usr/share/vdsm/storage/task.py", line 875, in _run > > return fn(*args, **kargs) > > File "/usr/share/vdsm/storage/task.py", line 334, in run > > return self.cmd(*self.argslist, **self.argsdict) > > File "/usr/lib/python2.7/site-packages/vdsm/storage/securable.py", line > > 78, in wrapper > > return method(self, *args, **kwargs) > > File "/usr/share/vdsm/storage/sp.py", line 1862, in mergeSnapshots > > sdUUID, vmUUID, imgUUID, ancestor, successor, postZero) > > File "/usr/share/vdsm/storage/image.py", line 1339, in merge > > : raise se.SourceImageActionError(imgUUID, sdUUID, str(e)) > > SourceImageActionError: Error during source image manipulation: > > "image=c26b2f00-563f-4965-8bcd-e7ca8ead1625, source > > domain=e562ec63-b734-4554-b82c-7fc8314c352f: can't set attribute" > > 5b61867b-6dd4-4224-be4a-859904e3298b::DEBUG::2016-05-08 > > 12:34:22,300::task::887::Storage.TaskManager.Task::(_run) > > Task=`5b61867b-6dd4-4224-be4a-859904e3298b`::Task._run: > > 5b61867b-6dd4-4224-be4a-859904e3298b () {} failed - stopping task > > 5b61867b-6dd4-4224-be4a-859904e3298b::DEBUG::2016-05-08 > > 12:34:22,300::task::1248::Storage.TaskManager.Task::(stop) > > Task=`5b61867b-6dd4-4224-be4a-859904e3298b`::stopping in state running > > (force False) > > > > > > > > Regards, > > Maor > > > > > > _______________________________________________ > > vdsm-devel mailing list > > vdsm-devel(a)lists.fedorahosted.org > > > https://lists.fedorahosted.org/admin/lists/vdsm-devel@lists.fedorahosted.org > > >

1 0

Fwd: [vdsm] Failing to rename volume on merge (remove snapshot operation)
by Maor Lipchuk 08 May '16

08 May '16

Forwarding to devel@ovirt list. cc'ing Adam as well ---------- Forwarded message ---------- From: Dan Kenigsberg <danken(a)redhat.com> Date: Sun, May 8, 2016 at 2:52 PM Subject: Re: [vdsm] Failing to rename volume on merge (remove snapshot operation) To: Maor Lipchuk <mlipchuk(a)redhat.com> vdsm-devel is long deprecated. Plesae repost to devel@ovirt, and include alitke, the owner of _manifest on your CC. On Sun, May 08, 2016 at 12:56:58PM +0300, Maor Lipchuk wrote: > Hi, > > I've been trying to remove a single snapshot and consistently fail with the > following error (see [1]). > > Those are my steps: > 1. Create a VM + Disk > 2. Create a snapshot > 3. Remove the snapshot > > My VDSM is the latest (commit d7796fb8bdd5b424ecad54dc36cb58cd477b3224) > > Is there a bug open on it? or even better, fixing patches? > > [1] > 5b61867b-6dd4-4224-be4a-859904e3298b::DEBUG::2016-05-08 > 12:34:22,296::fileVolume::573::Storage.Volume::(rename) Renaming > /rhev/data-center/mnt/10.35.16.43:_export_data9/e562ec63-b734-4554-b8 > 2c-7fc8314c352f/images/c26b2f00-563f-4965-8bcd-e7ca8ead1625/903f5a13-f7e4-4222-bb02-303019756bb9.lease > to /rhev/data-center/mnt/10.35.16.43: > _export_data9/e562ec63-b734-4554-b82c-7fc8314c352f > /images/c26b2f00-563f-4965-8bcd-e7ca8ead1625/_remove_me_LGQXBkpd_903f5a13-f7e4-4222-bb02-303019756bb9.lease > 5b61867b-6dd4-4224-be4a-859904e3298b::ERROR::2016-05-08 > 12:34:22,298::image::1338::Storage.Image::(merge) can't set attribute > Traceback (most recent call last): > File "/usr/share/vdsm/storage/image.py", line 1321, in merge > [vols[vName] for vName in chain]) > File "/usr/share/vdsm/storage/image.py", line 1146, in _baseRawVolumeMerge > srcVol.rename(tmpUUID) > File "/usr/share/vdsm/storage/fileVolume.py", line 580, in rename > self._manifest.volumePath = volPath > AttributeError: can't set attribute > 5b61867b-6dd4-4224-be4a-859904e3298b::DEBUG::2016-05-08 > 12:34:22,299::resourceManager::628::Storage.ResourceManager::(releaseResource) > Trying to release resource 'e562ec63-b734-4554-b82c-7fc > 8314c352f_imageNS.c26b2f00-563f-4965-8bcd-e7ca8ead1625' > 5b61867b-6dd4-4224-be4a-859904e3298b::DEBUG::2016-05-08 > 12:34:22,299::resourceManager::647::Storage.ResourceManager::(releaseResource) > Released resource 'e562ec63-b734-4554-b82c-7fc8314c352f > _imageNS.c26b2f00-563f-4965-8bcd-e7ca8ead1625' (0 active users) > 5b61867b-6dd4-4224-be4a-859904e3298b::DEBUG::2016-05-08 > 12:34:22,299::resourceManager::653::Storage.ResourceManager::(releaseResource) > Resource 'e562ec63-b734-4554-b82c-7fc8314c352f_imageNS. > c26b2f00-563f-4965-8bcd-e7ca8ead1625' is free, finding out if anyone is > waiting for it. > 5b61867b-6dd4-4224-be4a-859904e3298b::DEBUG::2016-05-08 > 12:34:22,299::resourceManager::628::Storage.ResourceManager::(releaseResource) > Trying to release resource 'e562ec63-b734-4554-b82c-7fc > 8314c352f_volumeNS.903f5a13-f7e4-4222-bb02-303019756bb9' > 5b61867b-6dd4-4224-be4a-859904e3298b::DEBUG::2016-05-08 > 12:34:22,299::resourceManager::647::Storage.ResourceManager::(releaseResource) > Released resource 'e562ec63-b734-4554-b82c-7fc8314c352f > _volumeNS.903f5a13-f7e4-4222-bb02-303019756bb9' (0 active users) > 5b61867b-6dd4-4224-be4a-859904e3298b::DEBUG::2016-05-08 > 12:34:22,299::resourceManager::653::Storage.ResourceManager::(releaseResource) > Resource 'e562ec63-b734-4554-b82c-7fc8314c352f_volumeNS > .903f5a13-f7e4-4222-bb02-303019756bb9' is free, finding out if anyone is > waiting for it. > 5b61867b-6dd4-4224-be4a-859904e3298b::DEBUG::2016-05-08 > 12:34:22,299::resourceManager::661::Storage.ResourceManager::(releaseResource) > No one is waiting for resource 'e562ec63-b734-4554-b82c > -7fc8314c352f_volumeNS.903f5a13-f7e4-4222-bb02-303019756bb9', Clearing > records. > 5b61867b-6dd4-4224-be4a-859904e3298b::DEBUG::2016-05-08 > 12:34:22,299::resourceManager::628::Storage.ResourceManager::(releaseResource) > Trying to release resource 'e562ec63-b734-4554-b82c-7fc > 8314c352f_volumeNS.e6d9874a-8225-44e1-9440-0a3cfd4ea7fc' > 5b61867b-6dd4-4224-be4a-859904e3298b::DEBUG::2016-05-08 > 12:34:22,299::resourceManager::647::Storage.ResourceManager::(releaseResource) > Released resource 'e562ec63-b734-4554-b82c-7fc8314c352f > _volumeNS.e6d9874a-8225-44e1-9440-0a3cfd4ea7fc' (0 active users) > 5b61867b-6dd4-4224-be4a-859904e3298b::DEBUG::2016-05-08 > 12:34:22,300::resourceManager::653::Storage.ResourceManager::(releaseResource) > Resource 'e562ec63-b734-4554-b82c-7fc8314c352f_volumeNS > .e6d9874a-8225-44e1-9440-0a3cfd4ea7fc' is free, finding out if anyone is > waiting for it. > 5b61867b-6dd4-4224-be4a-859904e3298b::DEBUG::2016-05-08 > 12:34:22,300::resourceManager::661::Storage.ResourceManager::(releaseResource) > No one is waiting for resource 'e562ec63-b734-4554-b82c > -7fc8314c352f_volumeNS.e6d9874a-8225-44e1-9440-0a3cfd4ea7fc', Clearing > records. > 5b61867b-6dd4-4224-be4a-859904e3298b::DEBUG::2016-05-08 > 12:34:22,300::resourceManager::661::Storage.ResourceManager::(releaseResource) > No one is waiting for resource 'e562ec63-b734-4554-b82c > -7fc8314c352f_imageNS.c26b2f00-563f-4965-8bcd-e7ca8ead1625', Clearing > records. > 5b61867b-6dd4-4224-be4a-859904e3298b::ERROR::2016-05-08 > 12:34:22,300::task::868::Storage.TaskManager.Task::(_setError) > Task=`5b61867b-6dd4-4224-be4a-859904e3298b`::Unexpected error > Traceback (most recent call last): > File "/usr/share/vdsm/storage/task.py", line 875, in _run > return fn(*args, **kargs) > File "/usr/share/vdsm/storage/task.py", line 334, in run > return self.cmd(*self.argslist, **self.argsdict) > File "/usr/lib/python2.7/site-packages/vdsm/storage/securable.py", line > 78, in wrapper > return method(self, *args, **kwargs) > File "/usr/share/vdsm/storage/sp.py", line 1862, in mergeSnapshots > sdUUID, vmUUID, imgUUID, ancestor, successor, postZero) > File "/usr/share/vdsm/storage/image.py", line 1339, in merge > : raise se.SourceImageActionError(imgUUID, sdUUID, str(e)) > SourceImageActionError: Error during source image manipulation: > "image=c26b2f00-563f-4965-8bcd-e7ca8ead1625, source > domain=e562ec63-b734-4554-b82c-7fc8314c352f: can't set attribute" > 5b61867b-6dd4-4224-be4a-859904e3298b::DEBUG::2016-05-08 > 12:34:22,300::task::887::Storage.TaskManager.Task::(_run) > Task=`5b61867b-6dd4-4224-be4a-859904e3298b`::Task._run: > 5b61867b-6dd4-4224-be4a-859904e3298b () {} failed - stopping task > 5b61867b-6dd4-4224-be4a-859904e3298b::DEBUG::2016-05-08 > 12:34:22,300::task::1248::Storage.TaskManager.Task::(stop) > Task=`5b61867b-6dd4-4224-be4a-859904e3298b`::stopping in state running > (force False) > > > > Regards, > Maor > _______________________________________________ > vdsm-devel mailing list > vdsm-devel(a)lists.fedorahosted.org > https://lists.fedorahosted.org/admin/lists/vdsm-devel@lists.fedorahosted.org

1 0

[IOPROCESS] New builds for testing
by Nir Soffer 06 May '16

06 May '16

Hi all, Fresh ioprocess builds are available for testing. The packages should be available in updates-testing repository on fedora. Please test these builds and provide feedback here: https://bodhi.fedoraproject.org/updates/?packages=ioprocess Thanks, Nir

1 0

[ANN] oVirt 3.6.6 Second Release Candidate is now available for testing
by Sandro Bonazzola 06 May '16

06 May '16

The oVirt Project is pleased to announce the availability of the Second Release Candidate of oVirt 3.6.6 for testing, as of May 7th, 2016 This release is available now for: * Fedora 22 * Red Hat Enterprise Linux 6.7 * CentOS Linux 6.7 (or similar) * Red Hat Enterprise Linux 7.2 or later * CentOS Linux (or similar) 7.2 or later This release supports Hypervisor Hosts running: * Red Hat Enterprise Linux 7.2 or later * CentOS Linux (or similar) 7.2 or later * Fedora 22 This release candidate includes the following updated packages: * ovirt-engine * ovirt-hosted-engine-setup * ovirt-hosted-engine-ha * vdsm * vdsm-jsonrpc-java See the release notes [1] for installation / upgrade instructions and a list of new features and bugs fixed. Notes: * A new oVirt Live ISO is already available [2]. * A new oVirt Node Next Install ISO will be available soon[3] * Mirrors[4] might need up to one day to synchronize. Additional Resources: * Read more about the oVirt 3.6.6 release highlights: http://www.ovirt.org/release/3.6.6/ * Get more oVirt Project updates on Twitter: https://twitter.com/ovirt * Check out the latest project news on the oVirt blog: http://www.ovirt.org/blog/ [1] http://www.ovirt.org/release/3.6.6/ [2] http://resources.ovirt.org/pub/ovirt-3.6-pre/iso/ovirt-live/ [3] http://resources.ovirt.org/pub/ovirt-3.6-pre/iso/ovirt-node-ng-installer/ [4] http://www.ovirt.org/Repository_mirrors#Current_mirrors -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

1 0

[URGENT][ACTION REQUIRED] fc23 master broken on vdsm-jsonrpc-java-1.2.3 missing
by Sandro Bonazzola 06 May '16

06 May '16

*21:57:45* package: ovirt-engine-backend-4.0.0-0.0.master.20160506110433.gitb791fed.fc23.noarch from check-custom-fc23*21:57:45* unresolved deps: *21:57:45* vdsm-jsonrpc-java >= 0:1.2.3 Please fix ASAP. Just to clarify, when a new build is needed: 1) get all the needed code merged in gerrit 2) tag the commit with the version bump 3) be sure that jenkins build job has been triggered and the package is built successfully 4) push to sonatype / maven central 5) once everything is in place, only then, change the code in ovirt-engine. pushing to sonatype before having code merged, tagged and built and require it will lead to breakage at all levels. This is the 4th time today I hit breakage like this, please avoid that in future. Thanks. -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

1 0

[ACTION REQUIRED] ovirt-node-plugin-hosted-engine broken on 3.6
by Sandro Bonazzola 06 May '16

06 May '16

*00:07:19.979* ======================================================================*00:07:19.979* ERROR: Failure: ImportError (No module named ovirt.node.utils.expose)*00:07:19.979* ----------------------------------------------------------------------*00:07:19.979* Traceback (most recent call last):*00:07:19.979* File "/usr/lib/python2.7/site-packages/nose/loader.py", line 413, in loadTestsFromName*00:07:19.979* addr.filename, addr.module)*00:07:19.979* File "/usr/lib/python2.7/site-packages/nose/importer.py", line 47, in importFromPath*00:07:19.979* return self.importFromDir(dir_path, fqname)*00:07:19.980* File "/usr/lib/python2.7/site-packages/nose/importer.py", line 94, in importFromDir*00:07:19.980* mod = load_module(part_fqname, fh, filename, desc)*00:07:19.980* File "/home/jenkins/workspace/ovirt-node-plugin-hosted-engine_ovirt-3.6_check-merged-el7-x86_64/ovirt-node-plugin-hosted-engine/src/__init__.py", line 21, in <module>*00:07:19.980* from ovirt.node.utils.expose import Feature, Owner*00:07:19.980* ImportError: No module named ovirt.node.utils.expose See http://jenkins.ovirt.org/view/00%20Unstable%20Jobs%20(Production)/job/ovirt… -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

2 1

[ACTION REQUIRED] master broken on unreleased vdsm-jsonrpc-java >= 1.2.3
by Sandro Bonazzola 06 May '16

06 May '16

[ ERROR ] Failed to execute stage 'Environment customization': [u'ovirt-engine-backend-4.0.0-0.0.master.20160505213341.gite5e9463.el7.centos.noarch requires vdsm-jsonrpc-java >= 1.2.3'] See http://jenkins.ovirt.org/view/00%20Unstable%20Jobs%20(Production)/job/ovirt… Please be sure that a dependency is publicly available before requiring it. Thanks! -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

1 0

Sonarqube reports for ovirt-engine
by Roman Mohr 05 May '16

05 May '16

HI all, I have asked sonarqube if they would add ovirt-engine to their hosted sonar instance https://nemo.sonarqube.org/. They would be happy to do that. It is free and for open source projects only. For those which are not familiar with sonarqube, it is a code quality testing tool which gives a lot of architectural insights into applications (coverity like features, code coverage, coupling, bunch of other OOP code metrics, trends, ...). To integrate with nemo I would add a travis.yml file which would do the build and analysis of ovirt-engine on travis and upload it to nemo. There are no risks four our CI if travis or nemo have issues. Best Regards, Roman

2 1

Master ovirt-engine build broken
by Roman Mohr 04 May '16

04 May '16

Hi, I see failing tests regarding to missing translations (e.g. [1]). [...] Failed tests: doTest(org.ovirt.engine.ui.uicompat.UIMessagesTest): cpuInfoLabel does not match the number of parameters in UIMessages_zh_CN.properties(..) [...] Best Regards, Roman [1] http://jenkins.ovirt.org/job/ovirt-engine_master_check-patch-fc23-x86_64/40…

8 21

[oVirt 4.0 Localization Question #3] "NUMA node pinned index error."
by Yuko Katabami 04 May '16

04 May '16

Hi oVirt developers, Here is our question #3. Thank you! File: AppErrors Resource ID: VM_NUMA_NODE_PINNED_INDEX_ERROR String: NUMA node pinned index error. Question: We cannot understand this message clearly as there are several different ways to interpret it. Could anyone please paraphrase this string? Does it mean, something like "An error ocurred with index of a pinned NUMA node."? Yuko

2 1

oVirt 3.6.6 RC2 build starting
by Lev Veyde 04 May '16

04 May '16

Fyi oVirt products maintainers, An oVirt build for an official release is going to start right now. If you're a maintainer for any of the projects included in oVirt distribution and you have changes in your package ready to be released please: - bump version and release to be GA ready - tag your release within git (implies a GitHub Release to be automatically created) - build your packages within jenkins / koji / copr / whatever - verify all bugs on MODIFIED have target release and target milestone set. Thanks in advance, Lev Veyde.

1 0

[oVirt 4.0 Localization Question #2] NETWORK_ATTACHMENT_MISSING_IP_CONFIGURATION
by Yuko Katabami 04 May '16

04 May '16

Hello all, Here is our second question: *File*: AppErrors *Resource ID*: NETWORK_ATTACHMENT_MISSING_IP_CONFIGURATION *String*: Network attachment of Network ${networkName}, Interface ${interfaceName} is missing ip configuration details. *Question*: There is a gramattical error in this message. Should it changed to either of following? 1) For the network attachment of network ${networkName}, interface ${interfaceName} is missing IP configuration details. 2) Network attachment of network ${networkName} and interface ${interfaceName} are missing ip configuration details. Thanks in advance! Yuko **

1 1

[oVirt 4.0 Localization Question #1] "Storage Domain's number of LVs exceeded threshold"
by Yuko Katabami 03 May '16

03 May '16

Hi oVirt developers, We have started translating oVirt 4.0 UI strings from this week. The following is our first question. It would be great if you could provide us the answer. *File: *LocalizedEnums *Resource ID: *AuditLogType___NUNBER_OF_LVS_ON_STORAGE_DOMAIN _EXCEEDED_THRESHOLD> *String: *Storage Domain's number of LVs exceeded threshold *Question:* Could you please tell us where this string is shown on UI? I would like to check whether this string is used as a message to report taht it exceeded the threshold or it is a label where the number is shown. Kind regards, Yuko

2 2

oVirt 3.6.6 RC2 merge / tag / bugzilla reminder
by Rafael Martins 03 May '16

03 May '16

All stable branch maintainers, please make sure to merge all relevant open bugs until Wednesday morning 11:00 AM TLV time. https://bugzilla.redhat.com/buglist.cgi?quicksearch=target_milestone%3A3.6.… Every package build (i.e oVirt product) - please make sure every bug in MODIFIED has the right Target Release and Target Milestone. A Target release should state the version of the package you're building and should include the same version you used for the tag you just used for this build. (e.g. for ovirt-engine, tag: ovirt-engine-3.6.6, tr: 3.6.6) Thanks, Rafael Martins

1 0

oVirt 3.6.6 RC2 build planned
by Rafael Martins 03 May '16

03 May '16

Fyi oVirt developers, An oVirt build is planned for this Wednesday 11:00 AM TLV time (10:00 AM CEST). Taking into consideration the time it takes for Jenkins to run a full CI everything need to be backported by Tuesday 11PM. Please make sure to mark as verified and CR +2 so it will be ready for merging Wednesday morning. https://bugzilla.redhat.com/buglist.cgi?quicksearch=target_milestone%3A3.6.… Thanks Rafael Martins

1 0

[ACTION REQUIRED] oVirt Engine 3.6.6 branched
by Sandro Bonazzola 02 May '16

02 May '16

Hi, ovirt-engine-3.6.6 has been created and is currently an exact copy of ovirt-engine-3.6. >From now on, all patches targeted to 3.6.6 will need to be cherry-picked to that branch too. A patch for bumping the ovirt-engine-3.6 branch to 3.6.7 will follow. Thanks, -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

1 0

Reminder: oVirt 4 Feature freeze and beta release in 2 weeks
by Sandro Bonazzola 02 May '16

02 May '16

Hi, just a friendly reminder that we're entering feature freeze in 2 weeks and release oVirt 4.0 beta on May 18th[1]. If your project is not yet built in jenkins and / or not yet published in master repository please let me know. [1] http://www.ovirt.org/develop/release-management/releases/4.0/release-manage… -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

1 0

Weekly bug status for ovirt-system-tests (using Lago) [ 01/05/16 ]
by Eyal Edri 01 May '16

01 May '16

FYI, Some updates from recent activity on ovirt-system-tests running on Lago. *Open bugs:* https://goo.gl/eUaPUY *Open issues:* Improvements on the host install issue, some env are not reproducing anymore but not sure we're 100% clear yet. *Open patches:* (reviews are welcome) https://gerrit.ovirt.org/#/q/project:ovirt-system-tests+status:open * There are quite a few open, some are just temp for helping with the debug of 'stuck in installing state' *Jenkins jobs: (failing on known issues)* http://jenkins.ovirt.org/view/oVirt%20system%20tests/ *Recently merged patches:* commit 211e475c004a2635896e528cd3aed6cd7d0dc5fd Author: Sandro Bonazzola <sbonazzo(a)redhat.com> Date: Thu Apr 28 16:44:50 2016 +0200 common: yum-repos: update glusterfs repos - dropped Gluster community repo for Fedora23: the repo is empty and Gluster community is maintaining Fedora packages within Fedora repositories. For reference: http://download.gluster.org/pub/gluster/glusterfs/LATEST/Fedora/What_About_… - on EL7 moved from Gluster community repo to CentOS Storage SIG repositories: we've been advised by Gluster community that their packaging effort is focused on CentOS Storage SIG and CentOS infrastructure is more reliable. Change-Id: I4d2c752be825fbbb9035222845728d10c5dd288c Signed-off-by: Sandro Bonazzola <sbonazzo(a)redhat.com> ---------------------------------------------------------------------------------------------------------- commit 19c102110279975d274c32477cc28c7c29e75fbc Author: David Caro <dcaroest(a)redhat.com> Date: Wed Apr 20 21:10:37 2016 +0200 Fixed answerfile for master A new question was added to the setup Change-Id: I6be958a70d67126d8067ff1855018125623b10c1 ---------------------------------------------------------------------------------------------------------- commit 5829862d17e92f91cfd04e7b9d5549cd775c800c Author: Yaniv Kaul <ykaul(a)redhat.com> Date: Mon Apr 25 14:06:27 2016 +0300 Add 'device=eth0' to EL7 deploy scripts. Apparently, /etc/sysconfig/network-scripts/ifcfg-eth0 lacks it on EL7 images. This works with NetworkManager, but not without it. When something goes bad, VDSM fails to rollback properly as its missing. For now, add it. Change-Id: I1c4ca07499a3947022e6f943cf05842ee1def408 Signed-off-by: Yaniv Kaul <ykaul(a)redhat.com> ---------------------------------------------------------------------------------------------------------- commit ddb42782968e5c6d411cdc747503fd90bed249d7 Author: David Caro <dcaroest(a)redhat.com> Date: Tue Mar 29 18:53:42 2016 +0200 Fix the master suite runs This is just copying over and adapting a bit (just so it works) the 3.6 suite into the master suite. Only for the 3.6 api, the newapi tests will be added later Still affected by the storage deactivation issues Change-Id: I55781a5d5a746aaf81e403eeeee40880beacb8a0 Signed-off-by: David Caro <dcaroest(a)redhat.com> ---------------------------------------------------------------------------------------------------------- commit c7d50cf8aebd6b566ae5c6ee8d6e3b8ec24ffc2b Author: Yaniv Kaul <ykaul(a)redhat.com> Date: Tue Apr 26 13:57:43 2016 +0300 Remove snapshot and reverting as part of the ovirt-system-tests I currently did not find a use case for it. It slows down the tests and causes (real? false?) issues with SDs. Mainly their activation and deactivation. It dramatically reduced the time to run the whole suite for me. 3-4 minutes on my desktop, and >10 minutes on my laptop. Change-Id: I9f7e509220c83805df78abb94b0ddc390c4a7f54 Signed-off-by: Yaniv Kaul <ykaul(a)redhat.com> ---------------------------------------------------------------------------------------------------------- -- Eyal Edri Associate Manager RHEV DevOps EMEA ENG Virtualization R&D Red Hat Israel phone: +972-9-7692018 irc: eedri (on #tlv #rhev-dev #rhev-integ)

1 0

[VDSM] flaky networking test
by Nir Soffer 01 May '16

01 May '16

Hi all, I think we have a pending patch for this, perhaps we should merge it? 19:32:54 ====================================================================== 19:32:54 ERROR: test_local_auto_with_dynamic_address_from_ra (network.netinfo_test.TestIPv6Addresses) 19:32:54 ---------------------------------------------------------------------- 19:32:54 Traceback (most recent call last): 19:32:54 File "/home/jenkins/workspace/vdsm_master_check-patch-fc23-x86_64/vdsm/tests/testValidation.py", line 97, in wrapper 19:32:54 return f(*args, **kwargs) 19:32:54 File "/home/jenkins/workspace/vdsm_master_check-patch-fc23-x86_64/vdsm/tests/network/netinfo_test.py", line 446, in test_local_auto_with_dynamic_address_from_ra 19:32:54 self.assertEqual('link', ip_addrs[1]['scope']) 19:32:54 File "/usr/lib64/python2.7/contextlib.py", line 24, in __exit__ 19:32:54 self.gen.next() 19:32:54 File "/home/jenkins/workspace/vdsm_master_check-patch-fc23-x86_64/vdsm/tests/network/nettestlib.py", line 405, in dnsmasq_run 19:32:54 server.stop() 19:32:54 File "/usr/lib64/python2.7/contextlib.py", line 24, in __exit__ 19:32:54 self.gen.next() 19:32:54 File "/home/jenkins/workspace/vdsm_master_check-patch-fc23-x86_64/vdsm/tests/network/firewall.py", line 45, in allow_dhcp 19:32:54 _forbid_dhcp(iface) 19:32:54 File "/home/jenkins/workspace/vdsm_master_check-patch-fc23-x86_64/vdsm/tests/network/firewall.py", line 89, in _forbid_dhcp 19:32:54 '67', '-j', 'ACCEPT']) # DHCPv4 19:32:54 File "/home/jenkins/workspace/vdsm_master_check-patch-fc23-x86_64/vdsm/tests/network/firewall.py", line 110, in _execCmdChecker 19:32:54 command, out, err)) 19:32:54 FirewallError: Command ['/sbin/iptables', '-D', 'INPUT', '-i', 'veth_qjA94YJwY8', '-p', 'udp', '--sport', '68', '--dport', '67', '-j', 'ACCEPT'] failed with []; ['Another app is currently holding the xtables lock. Perhaps you want to use the -w option?'] 19:32:54 -------------------- >> begin captured logging << -------------------- 19:32:54 root: DEBUG: /usr/bin/taskset --cpu-list 0-1 /sbin/ip link add name veth_qjA94YJwY8 type veth peer name veth_NLC6ccMcUU (cwd None) 19:32:54 root: DEBUG: SUCCESS: <err> = ''; <rc> = 0 19:32:54 root: DEBUG: /usr/bin/taskset --cpu-list 0-1 /usr/sbin/dnsmasq --dhcp-authoritative -p 0 --dhcp-option=3 --dhcp-option=6 -i veth_qjA94YJwY8 -I lo -d --bind-dynamic --enable-ra --dhcp-range=2001:1:1:1::,slaac,2m (cwd None) 19:32:54 root: DEBUG: /usr/bin/taskset --cpu-list 0-1 /sbin/service iptables status (cwd None) 19:32:54 root: DEBUG: SUCCESS: <err> = 'Redirecting to /bin/systemctl status iptables.service\nRunning in chroot, ignoring request.\n'; <rc> = 0 19:32:54 root: DEBUG: /usr/bin/taskset --cpu-list 0-1 /sbin/iptables --wait -I INPUT -i veth_qjA94YJwY8 -p udp --sport 68 --dport 67 -j ACCEPT (cwd None) 19:32:54 root: DEBUG: SUCCESS: <err> = ''; <rc> = 0 19:32:54 root: DEBUG: /usr/bin/taskset --cpu-list 0-1 /sbin/iptables --wait -I INPUT -i veth_qjA94YJwY8 -p udp --sport 546 --dport 547 -j ACCEPT (cwd None) 19:32:54 root: DEBUG: SUCCESS: <err> = ''; <rc> = 0 19:32:54 root: DEBUG: /usr/bin/taskset --cpu-list 0-1 /sbin/ip link set dev veth_NLC6ccMcUU up (cwd None) 19:32:54 root: DEBUG: SUCCESS: <err> = ''; <rc> = 0 19:32:54 root: DEBUG: /usr/bin/taskset --cpu-list 0-1 /sbin/ip link set dev veth_qjA94YJwY8 up (cwd None) 19:32:54 root: DEBUG: SUCCESS: <err> = ''; <rc> = 0 19:32:54 root: DEBUG: /usr/bin/taskset --cpu-list 0-1 /sbin/ip -6 addr add dev veth_qjA94YJwY8 2001:1:1:1::1/64 (cwd None) 19:32:54 root: DEBUG: SUCCESS: <err> = ''; <rc> = 0 19:32:54 root: DEBUG: dnsmasq: started, version 2.75 DNS disabled 19:32:54 dnsmasq: compile time options: IPv6 GNU-getopt DBus no-i18n IDN DHCP DHCPv6 no-Lua TFTP no-conntrack ipset auth DNSSEC loop-detect inotify 19:32:54 dnsmasq: warning: interface veth_qjA94YJwY8 does not currently exist 19:32:54 dnsmasq-dhcp: router advertisement on 2001:1:1:1:: 19:32:54 dnsmasq-dhcp: IPv6 router advertisement enabled 19:32:54 dnsmasq-dhcp: RTR-SOLICIT(veth_qjA94YJwY8) ce:82:16:6e:a5:7d 19:32:54 dnsmasq-dhcp: RTR-ADVERT(veth_qjA94YJwY8) 2001:1:1:1:: 19:32:54 19:32:54 root: DEBUG: /usr/bin/taskset --cpu-list 0-1 /sbin/service iptables status (cwd None) 19:32:54 root: DEBUG: SUCCESS: <err> = 'Redirecting to /bin/systemctl status iptables.service\nRunning in chroot, ignoring request.\n'; <rc> = 0 19:32:54 root: DEBUG: /usr/bin/taskset --cpu-list 0-1 /sbin/iptables -D INPUT -i veth_qjA94YJwY8 -p udp --sport 68 --dport 67 -j ACCEPT (cwd None) 19:32:55 root: DEBUG: FAILED: <err> = 'Another app is currently holding the xtables lock. Perhaps you want to use the -w option?\n'; <rc> = 4 19:32:55 root: DEBUG: /usr/bin/taskset --cpu-list 0-1 /sbin/ip link del dev veth_qjA94YJwY8 (cwd None) 19:32:55 root: DEBUG: SUCCESS: <err> = ''; <rc> = 0 19:32:55 --------------------- >> end captured logging << ---------------------

2 3

cannot create local ISO domain in RHEVM
by knarra 01 May '16

01 May '16

Hi, I am trying to set up Hosted Engine. I wanted to deploy windows virtual machines in this environment and as part of that i am creating ISO Domain to upload my windows image. But for some reason, while i create ISO domain it always fails with error "Failed to add Storage Domain <storagedomain_name"> and always remains in unattached state. Can some one please help me to reslove this issue? Attaching the vdsm logs. Thanks kasturi.

2 2