- Devel - oVirt List Archives

BUG - Cannot install Host with empty password.
by Shawn Weeks 04 Oct '18

04 Oct '18

Is there a current open bug for https://bugzilla.redhat.com/show_bug.cgi?id=1057575. It's still happening in the current release but it should have been fixed back in 2016. Guide me fails with this error but add host works fine. Thanks Shawn

1 0

Adding Fedora 28 host fail with "NotImplementedError: Packager install not implemented"
by Nir Soffer 04 Oct '18

04 Oct '18

Trying to add Fedora 28 host to engine master, host installation fails immediately with: 2018-10-02 20:34:45,440+0300 DEBUG otopi.plugins.otopi.dialog.machine dialog.__logString:204 DIALOG:SEND **%EventStart STAGE internal_packages METHOD otopi.plugins.ovirt_host_deploy.vd sm.vdsmid.Plugin._packages (None) 2018-10-02 20:34:45,443+0300 DEBUG otopi.context context._executeMethod:143 method exception Traceback (most recent call last): File "/tmp/ovirt-qh2D5sbRmG/pythonlib/otopi/context.py", line 133, in _executeMethod method['method']() File "/tmp/ovirt-qh2D5sbRmG/otopi-plugins/ovirt-host-deploy/vdsm/vdsmid.py", line 84, in _packages self.packager.install(('dmidecode',)) File "/tmp/ovirt-qh2D5sbRmG/pythonlib/otopi/packager.py", line 102, in install raise NotImplementedError(_('Packager install not implemented')) NotImplementedError: Packager install not implemented 2018-10-02 20:34:45,444+0300 ERROR otopi.context context._executeMethod:152 Failed to execute stage 'Environment packages setup': Packager install not implemented engine version: 4.3.0_master (efabde5a36cbf85b43a60ead37e42943c35c2741) Is this a known issue? any workaround? Nir

5 8

random failures on test 004_basic_sanity.check_snapshot_with_memory
by Dafna Ron 04 Oct '18

04 Oct '18

Hi, I have been noticing random failures for test 004_basic_sanity.check_snapshot_with_memory The failure is not connected directly to any of the failed changes and its either a problem with the test or a problem in vdsm which is causing the failure of this test randomly. the error we are getting is: Fault reason is "Operation Failed". Fault detail is "[Cannot run VM. Low disk space on Storage Domain iscsi.]". HTTP response code is 409. I think that its related the sparsify failure we have seen in the past [1] but it has been happening more often now. Tal, can someone in your team review this again? I think that if this is not resolved soon I will skip the test so that it does not fail changes for no reason. You can see failed build here: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/3277/ You can see the logs for the failed test here: https://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/3277/artifact/b… [1] https://ovirt-jira.atlassian.net/browse/OVIRT-2024 Thanks, Dafna

1 0

vdsm has been tagged (v4.20.42)
by Milan Zamazal 03 Oct '18

03 Oct '18

Vdsm 4.20.42 for oVirt 4.2.7 rc2

1 0

Re: Issue with vdsm-hook-vmfex-dev = 4.20.40-11.git6d99cc8.el7 shipping on u/s 4.2
by Eyal Edri 03 Oct '18

03 Oct '18

Adding devel and infra as well. On Wed, Oct 3, 2018 at 3:10 PM Michael Burman <mburman(a)redhat.com> wrote: > Hi > > I think we have an issue with vdsm-hook-vmfex-dev on 4.2 u/s > > When i try to update i get this Dependency Resolution > > Error: Package: vdsm-4.20.40-11.git6d99cc8.el7.x86_64 (ovirt-4.2-snapshot) > Requires: vdsm-hook-vmfex-dev = 4.20.40-11.git6d99cc8.el7 > Installed: vdsm-hook-vmfex-dev-4.20.40-10.giteffb1ef.el7.noarch > (@ovirt-4.2-snapshot) > vdsm-hook-vmfex-dev = 4.20.40-10.giteffb1ef.el7 > Available: vdsm-hook-vmfex-dev-4.20.23-1.el7.noarch > (ovirt-4.2-centos-ovirt42) > vdsm-hook-vmfex-dev = 4.20.23-1.el7 > Available: vdsm-hook-vmfex-dev-4.20.39.1-1.el7.noarch > (ovirt-4.2-centos-ovirt42) > vdsm-hook-vmfex-dev = 4.20.39.1-1.el7 > Error: Package: vdsm-hook-vmfex-dev-4.20.40-10.giteffb1ef.el7.noarch > (@ovirt-4.2-snapshot) > Requires: vdsm = 4.20.40-10.giteffb1ef.el7 > Removing: vdsm-4.20.40-10.giteffb1ef.el7.x86_64 > (@ovirt-4.2-snapshot) > vdsm = 4.20.40-10.giteffb1ef.el7 > Updated By: vdsm-4.20.40-11.git6d99cc8.el7.x86_64 > (ovirt-4.2-snapshot) > vdsm = 4.20.40-11.git6d99cc8.el7 > Available: vdsm-4.20.23-1.el7.x86_64 (ovirt-4.2-centos-ovirt42) > vdsm = 4.20.23-1.el7 > Available: vdsm-4.20.39.1-1.el7.x86_64 > (ovirt-4.2-centos-ovirt42) > vdsm = 4.20.39.1-1.el7 > > > https://resources.ovirt.org/pub/ovirt-4.2-snapshot/rpm/el7Server/noarch/ > > Is missing the correct version and this is the problem > > Thanks, > -- > > Michael Burman > > Senior Quality engineer - rhv network - redhat israel > > Red Hat > > <https://www.redhat.com> > > mburman(a)redhat.com M: 0545355725 IM: mburman > <https://red.ht/sig> > -- Eyal edri MANAGER RHV/CNV DevOps EMEA VIRTUALIZATION R&D Red Hat EMEA <https://www.redhat.com/> <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> phone: +972-9-7692018 irc: eedri (on #tlv #rhev-dev #rhev-integ)

3 3

[ENGINE] make install-dev fails, trying to install outside of ENGINE_PREFIX
by Nir Soffer 02 Oct '18

02 Oct '18

Trying to make install-dev with engine master: $ git clean -dxf $ git log | head -1 commit efabde5a36cbf85b43a60ead37e42943c35c2741 The build failes, trying to install stuff out of ENGINE_PREFIX: $ make install-dev ENGINE_PREFIX=/home/nsoffer/ovirt-engine ... make copy-recursive SOURCEDIR=packaging/sys-etc TARGETDIR="/usr/local/etc"... make[2]: Entering directory `/home/nsoffer/src/ovirt-engine' ( cd "packaging/sys-etc" && find . -type d -printf '%P\n' ) | while read d; do \ install -d -m 755 "/usr/local/etc/${d}"; \ done install: cannot change permissions of ‘/usr/local/etc/logrotate.d’: No such file or directory Is this know issue? any workaround? Thanks, Nir

1 1

increasingly common OST failure: Cannot setup Networks. Another Setup Networks or Host Refresh process in progress on the host. Please try later.
by Dan Kenigsberg 02 Oct '18

02 Oct '18

FYI, Ales is working on retrying setupNetwork in case there is an async getCapabilities going on the host. https://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt-4.2_change-q… However, the real bug is partially hidden by Lago complaining about ExtractPathNoPathError: scp: /root/fluentd: No such file or directory What is it? Is it already tracked by someone?

4 4

ovirt-engine has been tagged (ovirt-engine-4.2.7.2)
by Piotr Kliczewski 02 Oct '18

02 Oct '18

1 0

vdsm has been tagged (v4.20.41)
by Milan Zamazal 02 Oct '18

02 Oct '18

Vdsm 4.20.41 for oVirt 4.2.7 rc2

1 0

Help understanding vdsHeartbeatInSeconds relation to Heartbeat exceeded
by Germano Veit Michel 02 Oct '18

02 Oct '18

Hi, I've been trying to understand why we see some heartbeat exceeded messages with a last response a very short time ago, while the vdsHeartbeatInSeconds option would allow for much more before triggering the disconnect. The vdc_option vdsHeartbeatInSeconds is set to 30 by default. It is used here in the engine, the propagates to vdsm-jsonrpc-java int heartbeat = Config.<Integer> getValue(ConfigValues.vdsHeartbeatInSeconds) * 1000; TransportFactory.createVdsServer() -> JsonRpcUtils.createStompClient() -> StompClientPolicy ClientPolicy -> createClient() -> getJsonClient() -> setClientPolicy() -> setRetryPolicy() So I understand ClientPolicy.incomingHearbeat = vdsHeartbeatInSeconds*1000 = 30000ms If this is the case, why do we see messages such as this, if isIncomingHeartbeatExceeded() shouldn't return True in case the last heartbeat was less than 30000ms ago? 2018-09-17 10:46:49,891+03 ERROR [org.ovirt.vdsm.jsonrpc.client.reactors.ReactorClient] (SSL Stomp Reactor) [] Heartbeat exceeded for host '192.168.7.235', last response arrived 1702 ms ago. if (!this.isInInit() && this.policy.isIncomingHeartbeat() && this.isIncomingHeartbeatExceeded()) { String msg = String.format("Heartbeat exceeded for host '%s', last response arrived %s ms ago.", getHostname(), getHeartbeatTime()); log.error(msg); this.disconnect(msg); } private long getHeartbeatTime() { return System.currentTimeMillis() - this.lastIncomingHeartbeat; } private boolean isIncomingHeartbeatExceeded() { return this.lastIncomingHeartbeat + this.policy.getIncomingHeartbeat() < System.currentTimeMillis(); } public ClientPolicy(int retryTimeOut, int retryNumber, int incomingHeartbeat, int outgoingHeartbeat, List<Class<? extends Exception>> retryableExceptions) { this.retryNumber = retryNumber; this.retryTimeOut = retryTimeOut; setIncomingHeartbeat(incomingHeartbeat); setOutgoingHeartbeat(outgoingHeartbeat); this.exceptions = Collections.unmodifiableList(retryableExceptions); } I used byteman to print the value stored in policy.incomingHeartbeat and it is: If vdsHeartbeatInSeconds = 45 2018-09-27 15:17:13,673+10 INFO [stdout] (SSL Stomp Reactor) policy.incomingHeartbeat: 33750 If vdsHeartbeatInSeconds = 30 (default) 2018-09-27 15:21:51,099+10 INFO [stdout] (SSL Stomp Reactor) policy.incomingHeartbeat: 22500 I was expecting 45000 and 30000. But even with 33750 and 22500, I dont understand why we see "Heartbeat exceeded" and disconnection if the last heartbeat arrived just 1700ms ago. I'm clearly missing something. Could someone please put some light on what is the missing piece? Thanks, Germano

1 1