Re: [Engine-devel] Problem creating hosts.
Oi Sérgio, On 02/04/2014 07:16 PM, Sérgio Ribeiro wrote: I’m newbie in ovirt and after installing ovirt, with comand engine-setup, i go to localhost/ovirt-engine and i log on the webpage. On data center only appears a default data-center with no hosts. i trie to create a host and appears na error because the name and address of the host. its a local machine for tests with no domain. the config that i use is name:host1.localdomain, address: 192.168.2.1, and i created this config on etc/hosts file. can you help me? Did you add these address/host into /etc/hosts on ovirt-engine and ovirt-node? You could use the ip address directly too on admin portal. Additionally, do you have any error on event log window? (below on the Admin Portal) -- Cheers Douglas ___ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
Re: [Engine-devel] oVirt 3.4.0 beta is now available
Hi Eli, On 01/22/2014 01:10 PM, Eli Mesika wrote: - Original Message - From: Sandro Bonazzola sbona...@redhat.com To: Martin Perina mper...@redhat.com Cc: engine-devel engine-devel@ovirt.org, us...@ovirt.org Sent: Wednesday, January 22, 2014 5:01:55 PM Subject: Re: [Engine-devel] oVirt 3.4.0 beta is now available Il 22/01/2014 15:49, Martin Perina ha scritto: Hi, I tried to install on F19, but openstack* packages = 3.0.2 are missing: thanks, updated release page, it needs updates-testing I had enabled ovirt-updates-testing and still got this : Here it worked, without looking your 'yum repolist' output I do guess you need to enable the repo from: /etc/yum.repos.d/fedora-updates-testing.repo # yum install ovirt-engine snip Installing: ovirt-enginenoarch 3.4.0-0.5.beta1.fc19 ovirt-3.4.0-prerelease 1.3 /snip snip Installing for dependencies: openstack-java-glance-clientnoarch 3.0.2-1.fc19updates-testing 21 k openstack-java-glance-model noarch 3.0.2-1.fc19updates-testing 18 k openstack-java-keystone-client noarch 3.0.2-1.fc19updates-testing 33 k openstack-java-keystone-model noarch 3.0.2-1.fc19updates-testing 30 k openstack-java-quantum-client noarch 3.0.2-1.fc19updates-testing 20 k openstack-java-quantum-modelnoarch 3.0.2-1.fc19updates-testing 24 k /snip -- Finished Dependency Resolution Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch (ovirt-3.4.0-prerelease) Requires: openstack-java-quantum-model = 3.0.2 Available: openstack-java-quantum-model-3.0.1-1.fc19.noarch (updates) openstack-java-quantum-model = 3.0.1-1.fc19 Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch (ovirt-3.4.0-prerelease) Requires: openstack-java-glance-client = 3.0.2 Available: openstack-java-glance-client-3.0.1-1.fc19.noarch (updates) openstack-java-glance-client = 3.0.1-1.fc19 Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch (ovirt-3.4.0-prerelease) Requires: openstack-java-glance-model = 3.0.2 Available: openstack-java-glance-model-3.0.1-1.fc19.noarch (updates) openstack-java-glance-model = 3.0.1-1.fc19 Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch (ovirt-3.4.0-prerelease) Requires: openstack-java-client = 3.0.2 Available: openstack-java-client-3.0.1-1.fc19.noarch (updates) openstack-java-client = 3.0.1-1.fc19 Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch (ovirt-3.4.0-prerelease) Requires: openstack-java-keystone-model = 3.0.2 Available: openstack-java-keystone-model-3.0.1-1.fc19.noarch (updates) openstack-java-keystone-model = 3.0.1-1.fc19 Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch (ovirt-3.4.0-prerelease) Requires: openstack-java-resteasy-connector = 3.0.2 Available: openstack-java-resteasy-connector-3.0.1-1.fc19.noarch (updates) openstack-java-resteasy-connector = 3.0.1-1.fc19 Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch (ovirt-3.4.0-prerelease) Requires: openstack-java-quantum-client = 3.0.2 Available: openstack-java-quantum-client-3.0.1-1.fc19.noarch (updates) openstack-java-quantum-client = 3.0.1-1.fc19 Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch (ovirt-3.4.0-prerelease) Requires: openstack-java-keystone-client = 3.0.2 Available: openstack-java-keystone-client-3.0.1-1.fc19.noarch (updates) openstack-java-keystone-client = 3.0.1-1.fc19 You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch (ovirt-3.4.0-prerelease) Requires: openstack-java-quantum-model = 3.0.2 Available: openstack-java-quantum-model-3.0.1-1.fc19.noarch (updates) openstack-java-quantum-model = 3.0.1-1.fc19 Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch (ovirt-3.4.0-prerelease) Requires: openstack-java-glance-client = 3.0.2 Available: openstack-java-glance-client-3.0.1-1.fc19.noarch (updates) openstack-java-glance-client = 3.0.1-1.fc19 Error: Package: ovirt-engine-3.4.0-0.5.beta1.fc19.noarch
Re: [Engine-devel] [Users] oVirt 3.4.0 beta is now available
On 01/22/2014 03:00 PM, Eli Mesika wrote:
- Original Message -
From: Eli Mesika emes...@redhat.com
To: dougsl...@redhat.com
Cc: engine-devel engine-devel@ovirt.org, us...@ovirt.org
Sent: Wednesday, January 22, 2014 9:48:54 PM
Subject: Re: [Users] [Engine-devel] oVirt 3.4.0 beta is now available
- Original Message -
From: Douglas Schilling Landgraf dougsl...@redhat.com
To: Eli Mesika emes...@redhat.com, Sandro Bonazzola
sbona...@redhat.com
Cc: engine-devel engine-devel@ovirt.org, us...@ovirt.org
Sent: Wednesday, January 22, 2014 9:31:59 PM
Subject: Re: [Engine-devel] oVirt 3.4.0 beta is now available
Hi Eli,
On 01/22/2014 01:10 PM, Eli Mesika wrote:
- Original Message -
From: Sandro Bonazzola sbona...@redhat.com
To: Martin Perina mper...@redhat.com
Cc: engine-devel engine-devel@ovirt.org, us...@ovirt.org
Sent: Wednesday, January 22, 2014 5:01:55 PM
Subject: Re: [Engine-devel] oVirt 3.4.0 beta is now available
Il 22/01/2014 15:49, Martin Perina ha scritto:
Hi,
I tried to install on F19, but openstack* packages = 3.0.2 are
missing:
thanks, updated release page, it needs updates-testing
I had enabled ovirt-updates-testing and still got this :
Here it worked, without looking your 'yum repolist' output I do guess
you need to enable the repo from:
/etc/yum.repos.d/fedora-updates-testing.repo
Thanks, I enabled ovirt-updates-testing in ovirt repo . :-(
engine-setup fails with the following error
Failed to execute stage 'Misc configuration': Command '/bin/systemctl' failed
to execute
any ideas ?
Hi Eli,
Would be nice too see your engine-setup log file to determine which
error happened. Should be available here: /var/log/ovirt-engine/setup/
Anyway, I could reproduce a similar output during a setup (below the
log) and in my case was postgresql with error: FATAL: could not create
shared memory segment: Invalid argument
Resolved with wiki:
http://www.ovirt.org/Troubleshooting#Installation
In session:
I am having trouble connecting to the database. In the system log, I
get the following message from Postgres
@Sandro, should or maybe installer detect this kind of situation?
=
2014-01-22 17:37:52 DEBUG otopi.plugins.otopi.services.systemd
plugin.execute:446 execute-output: ('/bin/systemctl', 'start',
'postgresql.service') stderr:
Job for postgresql.service failed. See 'systemctl status
postgresql.service' and 'journalctl -xn' for details.
2014-01-22 17:37:52 DEBUG otopi.context context._executeMethod:152
method exception
Traceback (most recent call last):
File /usr/lib/python2.7/site-packages/otopi/context.py, line 142,
in _executeMethod
method['method']()
File
/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-setup/ovirt-engine/provisioning/postgres.py,
line 182, in _misc
self._provisioning.provision()
File /usr/share/ovirt-engine/setup/ovirt_engine_setup/postgres.py,
line 552, in provision
self._restart()
File /usr/share/ovirt-engine/setup/ovirt_engine_setup/postgres.py,
line 407, in _restart
state=state,
File /usr/share/otopi/plugins/otopi/services/systemd.py, line 138,
in state
'start' if state else 'stop'
File /usr/share/otopi/plugins/otopi/services/systemd.py, line 77,
in _executeServiceCommand
raiseOnError=raiseOnError
File /usr/lib/python2.7/site-packages/otopi/plugin.py, line 451, in
execute
command=args[0],
RuntimeError: Command '/bin/systemctl' failed to execute
2014-01-22 17:37:52 ERROR otopi.context context._executeMethod:161
Failed to execute stage 'Misc configuration': Command '/bin/systemctl'
failed to execute
2014-01-22 17:37:52 DEBUG otopi.transaction transaction.abort:131
aborting 'Yum Transaction'
2014-01-22 17:37:52 INFO otopi.plugins.otopi.packagers.yumpackager
yumpackager.info:92 Yum Performing yum transaction rollback
Loaded plugins: versionlock
--
Cheers
Douglas
___
Engine-devel mailing list
Engine-devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/engine-devel
Re: [Engine-devel] oVirt 3.4.0 alpha repository closure failure
On 01/10/2014 05:01 AM, Dan Kenigsberg wrote: On Fri, Jan 10, 2014 at 08:48:52AM +0100, Sandro Bonazzola wrote: Hi, oVirt 3.4.0 alpha repository has been composed but alpha has not been announced due to repository closure failures: on CentOS 6.5: # repoclosure -r ovirt-3.4.0-alpha -l ovirt-3.3.2 -l base -l epel -l glusterfs-epel -l updates -l extra -l glusterfs-noarch-epel -l ovirt-stable -n Reading in repository metadata - please wait Checking Dependencies Repos looked at: 8 base epel glusterfs-epel glusterfs-noarch-epel ovirt-3.3.2 ovirt-3.4.0-alpha ovirt-stable updates Num Packages in Repos: 16581 package: mom-0.3.2-20140101.git2691f25.el6.noarch from ovirt-3.4.0-alpha unresolved deps: procps-ng Adam, this seems like a real bug in http://gerrit.ovirt.org/#/c/22087/ : el6 still carries the older procps (which is, btw, provided by procps-ng). package: vdsm-hook-vhostmd-4.14.0-1.git6fdd55f.el6.noarch from ovirt-3.4.0-alpha unresolved deps: vhostmd Douglas, could you add a with_vhostmd option to the spec, and have it default to 0 on el*, and to 1 on fedoras? Done http://gerrit.ovirt.org/#/c/23126/ -- Cheers Douglas ___ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
[Engine-devel] UseSecureConnectionWithServers
Hi, This email is just a heads up about UseSecureConnectionWithServers option in database that got renamed [1] to EncryptHostCommunication to be more descriptive. Additionally, the EncryptHostCommunication was added to engine-config tool [2]. Fore more info: [1] http://gerrit.ovirt.org/#/c/19305/ [2] http://gerrit.ovirt.org/#/c/19202/ Thanks! -- Cheers Douglas ___ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
Re: [Engine-devel] [Users] [Feedback required][host-deploy] Fedora-19 misses tar at minimal setup
On 07/30/2013 09:25 AM, Michal Skrivanek wrote: On Jul 30, 2013, at 15:12 , Alon Bar-Lev alo...@redhat.com wrote: Hello All, Starting the discussion again... I would like to receive feedback regarding how we should cope with a state presented to use by Fedora. Fedora-19 minimal setup does not install tar utility which is required to deploy files during the host-deploy process (Hosts-Add Host). I guess because of 2.8M in size (including translations) -- a standard commonly used utility was removed. How about filing bug on that? This is such a basic utility I can't imagine anyone removing it. +1 I do agree with Michael. I have opened a thread in fedora devel mailing list anyway. There are three alternatives : 1. Instruct users who are using minimal installations to manually install tar utility just like they configure repository, dns, etc.. Benefit: simplicity. Benefit: use standard tools. Benefit: lower payload to transmit. Drawback: require tar at destination machine. 2. Do not use tar but self extracting python script, a patch is ready[1]. Benefit: ability to deploy environment in which tar is missing. Drawback: non standard tool at destination machine. Drawback: complexity within our code. 3. Do not use tar but cpio, a patch is ready[2]. Benefit: simplicity. Benefit: use standard tools. Benefit: lower payload to transmit. Benefit: ability to use Fedora-19 minimal. Drawback: cpio is even less common than tar, even if it exists in Fedora-19 it can be removed without anyone notice. Drawback: most other distributions will not have cpio in their minimal installation. [[[ There was 4rd alternative, using python tar module to deploy tar. However, there is a bug in that module when processing last block if empty. This is edge condition but happened to at least one of the users and I could reproduce it. ]]] What option do you prefer? Regards, Alon Bar-Lev [1] http://gerrit.ovirt.org/#/c/17295/ [2] http://gerrit.ovirt.org/#/c/17396/ ___ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel ___ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel -- Cheers Douglas ___ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
Re: [Engine-devel] fail to add host from portal
Hello, On 07/24/2013 11:05 PM, Chen, Wei D wrote: It fails when add a host from portal, and error info as follows, anyone can give us some suggestion? 2013-07-25 22:55:39,539 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (VdsDeploy) Correlation ID: 296737fb, Call Stack: null, Custom Event ID: -1, Message: Installing Host onode. Logs at host located at: '/tmp/ovirt-host-deploy-20130725105531.log'. 2013-07-25 22:55:39,563 ERROR [org.ovirt.engine.core.bll.VdsDeploy] (VdsDeploy) Error during deploy dialog: java.lang.NullPointerException at org.ovirt.otopi.dialog.MachineDialogParser.cliEnvironmentGet(MachineDialogParser.java:236) [otopi.jar:] at org.ovirt.engine.core.bll.VdsDeploy$14.call(VdsDeploy.java:347) [bll.jar:] at org.ovirt.engine.core.bll.VdsDeploy._nextCustomizationEntry(VdsDeploy.java:579) [bll.jar:] at org.ovirt.engine.core.bll.VdsDeploy._threadMain(VdsDeploy.java:791) [bll.jar:] at org.ovirt.engine.core.bll.VdsDeploy.access$1800(VdsDeploy.java:76) [bll.jar:] at org.ovirt.engine.core.bll.VdsDeploy$44.run(VdsDeploy.java:882) [bll.jar:] at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_25] 2013-07-25 22:55:39,565 ERROR [org.ovirt.engine.core.bll.VdsDeploy] (pool-6-thread-5) [296737fb] Error during host onode.sh.intel.com install: java.lang.NullPointerException at org.ovirt.otopi.dialog.MachineDialogParser.cliEnvironmentGet(MachineDialogParser.java:236) [otopi.jar:] at org.ovirt.engine.core.bll.VdsDeploy$14.call(VdsDeploy.java:347) [bll.jar:] at org.ovirt.engine.core.bll.VdsDeploy._nextCustomizationEntry(VdsDeploy.java:579) [bll.jar:] at org.ovirt.engine.core.bll.VdsDeploy._threadMain(VdsDeploy.java:791) [bll.jar:] at org.ovirt.engine.core.bll.VdsDeploy.access$1800(VdsDeploy.java:76) [bll.jar:] at org.ovirt.engine.core.bll.VdsDeploy$44.run(VdsDeploy.java:882) [bll.jar:] at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_25] 2013-07-25 22:55:39,568 ERROR [org.ovirt.engine.core.bll.VdsDeploy] (pool-6-thread-5) [296737fb] Error during host onode.sh.intel.com install, prefering first exception: java.lang.NullPointerException at org.ovirt.otopi.dialog.MachineDialogParser.cliEnvironmentGet(MachineDialogParser.java:236) [otopi.jar:] at org.ovirt.engine.core.bll.VdsDeploy$14.call(VdsDeploy.java:347) [bll.jar:] at org.ovirt.engine.core.bll.VdsDeploy._nextCustomizationEntry(VdsDeploy.java:579) [bll.jar:] at org.ovirt.engine.core.bll.VdsDeploy._threadMain(VdsDeploy.java:791) [bll.jar:] at org.ovirt.engine.core.bll.VdsDeploy.access$1800(VdsDeploy.java:76) [bll.jar:] at org.ovirt.engine.core.bll.VdsDeploy$44.run(VdsDeploy.java:882) [bll.jar:] at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_25] 2013-07-25 22:55:39,569 ERROR [org.ovirt.engine.core.bll.InstallVdsCommand] (pool-6-thread-5) [296737fb] Host installation failed for host 00c50bb0-f843-442a-a032-acebe0d092c4, onode.: java.lang.NullPointerException at org.ovirt.otopi.dialog.MachineDialogParser.cliEnvironmentGet(MachineDialogParser.java:236) [otopi.jar:] at org.ovirt.engine.core.bll.VdsDeploy$14.call(VdsDeploy.java:347) [bll.jar:] at org.ovirt.engine.core.bll.VdsDeploy._nextCustomizationEntry(VdsDeploy.java:579) [bll.jar:] at org.ovirt.engine.core.bll.VdsDeploy._threadMain(VdsDeploy.java:791) [bll.jar:] at org.ovirt.engine.core.bll.VdsDeploy.access$1800(VdsDeploy.java:76) [bll.jar:] at org.ovirt.engine.core.bll.VdsDeploy$44.run(VdsDeploy.java:882) [bll.jar:] at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_25] 2013-07-25 22:55:39,572 INFO [org.ovirt.engine.core.vdsbroker.SetVdsStatusVDSCommand] (pool-6-thread-5) [296737fb] START, SetVdsStatusVDSCommand(HostName = onode, HostId = 00c50bb0-f843-442a-a032-acebe0d092c4, status=InstallFailed, nonOperationalReason=NONE), log id: 39c3919d 2013-07-25 22:55:39,581 INFO [org.ovirt.engine.core.vdsbroker.SetVdsStatusVDSCommand] (pool-6-thread-5) [296737fb] FINISH, SetVdsStatusVDSCommand, log id: 39c3919d 2013-07-25 22:55:39,589 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (pool-6-thread-5) [296737fb] Correlation ID: 296737fb, Call Stack: null, Custom Event ID: -1, Message: Host onode installation failed. Please refer to engine.log and log files under /var/log/ovirt-engine/host-deploy/ on the engine for further details.. On Engine side, can you please check the log available at: /var/log/ovirt-engine/host-deploy/ ? -- Cheers Douglas ___ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
[Engine-devel] testDisplayPort - VmMapperTest
Hi, Anyone else failing on this unittest? $ make install-dev PREFIX=$HOME/ovirt-engine BUILD_UT=1 Results : Tests in error: testDisplayPort(org.ovirt.engine.api.restapi.types.VmMapperTest) Tests run: 121, Failures: 0, Errors: 1, Skipped: 0 [INFO] [INFO] Reactor Summary: [INFO] [INFO] ovirt-root SUCCESS [0.443s] [INFO] oVirt Build Tools root SUCCESS [0.010s] [INFO] oVirt checkstyle .. SUCCESS [1.054s] [INFO] oVirt JBoss Modules Maven Plugin .. SUCCESS [3.084s] [INFO] oVirt Checkstyle Checks ... SUCCESS [0.762s] [INFO] oVirt Modules - backend ... SUCCESS [0.004s] [INFO] oVirt Manager . SUCCESS [0.004s] [INFO] oVirt Engine dependencies . SUCCESS [1.428s] [INFO] oVirt Modules - manager ... SUCCESS [0.466s] [INFO] CSharp Compatibility .. SUCCESS [2.694s] [INFO] Common Code ... SUCCESS [10.024s] [INFO] Common utilities .. SUCCESS [19.154s] [INFO] Data Access Layer . SUCCESS [7.966s] [INFO] engine scheduler bean . SUCCESS [1.462s] [INFO] Vds broker SUCCESS [7.028s] [INFO] Search Backend SUCCESS [2.866s] [INFO] Backend Logic @Service bean ... SUCCESS [28.853s] [INFO] oVirt RESTful API Backend Integration . SUCCESS [0.094s] [INFO] oVirt RESTful API interface ... SUCCESS [0.119s] [INFO] oVirt Engine API Definition ... SUCCESS [10.331s] [INFO] oVirt Engine API Commom Parent POM SUCCESS [0.068s] [INFO] oVirt Engine API Common JAX-RS SUCCESS [5.188s] [INFO] oVirt RESTful API Backend Integration Type Mappers FAILURE [1:49.300s] [INFO] oVirt RESTful API Backend Integration JAX-RS Resources SKIPPED [INFO] oVirt RESTful API Backend Integration Webapp .. SKIPPED [INFO] oVirt Engine Web Root . SKIPPED [INFO] oVirt Engine Tools SKIPPED [INFO] oVirt Modules :: Frontend . SKIPPED [INFO] oVirt Modules :: Webadmin . SKIPPED [INFO] oVirt Modules - ui SKIPPED [INFO] Extensions for GWT SKIPPED [INFO] UI Utils Compatibility (for UICommon) . SKIPPED [INFO] Frontend for GWT UI Projects .. SKIPPED [INFO] UICommonWeb ... SKIPPED [INFO] oVirt GWT UI common infrastructure SKIPPED [INFO] WebAdmin .. SKIPPED [INFO] UserPortal SKIPPED [INFO] oVirt Server EAR .. SKIPPED [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 3:33.247s [INFO] Finished at: Sat Jul 20 04:09:04 BRT 2013 [INFO] Final Memory: 165M/881M [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.7.2:test (default-test) on project restapi-types: There are test failures. Thanks! -- Cheers Douglas ___ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
Re: [Engine-devel] Unknown operation 'force-start' when starting VDSM
Hello Greg, On 07/18/2013 04:38 PM, Greg Sheremeta wrote: Engine is installed and working on a fresh laptop install of Fedora 19. Rebased ovirt-engine from gerrit/master this morning. Trying to install host on a fresh Fedora 19 VM -- I'm trying to get a nested host setup. Host installation fails with: Jul 18 16:24:52 ovirt-host-fedora-2 systemd[1]: Starting Virtual Desktop Server Manager... Jul 18 16:24:53 ovirt-host-fedora-2 systemd-vdsmd[3956]: Note: Forwarding request to 'systemctl disable libvirt-guests.service'. Jul 18 16:24:53 ovirt-host-fedora-2 systemd-vdsmd[3956]: vdsm: libvirt already configured for vdsm [ OK ] Jul 18 16:24:53 ovirt-host-fedora-2 systemd-vdsmd[3956]: Starting multipathd... Jul 18 16:24:53 ovirt-host-fedora-2 systemd-vdsmd[3956]: Redirecting to /bin/systemctl start multipathd.service Jul 18 16:24:53 ovirt-host-fedora-2 systemd-vdsmd[3956]: Redirecting to /bin/systemctl force-start iscsid.service Jul 18 16:24:53 ovirt-host-fedora-2 systemd-vdsmd[3956]: Unknown operation 'force-start'. Jul 18 16:24:53 ovirt-host-fedora-2 systemd[1]: vdsmd.service: control process exited, code=exited status=1 Jul 18 16:24:53 ovirt-host-fedora-2 systemd[1]: Failed to start Virtual Desktop Server Manager. Jul 18 16:24:53 ovirt-host-fedora-2 systemd[1]: Unit vdsmd.service entered failed state. I've never heard of force-start before, and googling for fedora force-start brings up this as the second result: https://ask.fedoraproject.org/question/27737/vdsmdservice-fails-bc-iscsid-is-started-using-force-start/ So someone else out there is having this problem too :) vdsm-4.10.3-18 should fix it. Please check: http://permalink.gmane.org/gmane.comp.emulators.ovirt.user/9488 -- Cheers Douglas ___ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
Re: [Engine-devel] Introduce mail
Oi Fellipe, On 06/27/2013 05:48 PM, Fellipe Henrique wrote: hello folks! I'm here today, to introduce myself. I want to start to contribute to oVirt project, I'm developing most of time in python, and I'll love to contribute in python, but can be in C. Nice, welcome! I love developing and virtualization, and I think this project have all I like. well, like I said, this is a introduce email, and I'll like suggestion how can I help, and show my code to you guys. Which part of world are you located? :) If you are Brazilian (I am guessing based on your last name), are you going to FISL next week? If yes, we will have a booth there with talks about oVirt, demos and I am pretty sure we can talk about development, debugging env (on node side), eclipse and so on. As Alon already shared, there are tasks that you can help. Fell free to contact me offline list for more details about FISL. -- Cheers Douglas ___ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
Re: [Engine-devel] NPE approving node
On 06/27/2013 04:50 AM, Juan Hernandez wrote: Any idea why? Facing the same issue with updated tree. Cannot approve node. $ git log -1 commit b5438e34e0b179ef4f8ee20ce6e0d7b25cd2a36a 2013-06-27 10:37:40,219 INFO [org.ovirt.engine.core.bll.ApproveVdsCommand] (pool-6-thread-5) [3dd1f412] Running command: ApproveVdsCommand internal: false. Entities affected : ID: 0be6cd89-c5f5-4a4e-b498-504bb2c23eb2 Type: VDS 2013-06-27 10:37:40,239 INFO [org.ovirt.engine.core.bll.InstallVdsCommand] (pool-6-thread-5) [3dd1f412] Before Installation host 0be6cd89-c5f5-4a4e-b498-504bb2c23eb2, h0.example.com 2013-06-27 10:37:40,294 ERROR [org.ovirt.engine.core.bll.InstallVdsCommand] (pool-6-thread-5) [3dd1f412] Host installation failed for host 0be6cd89-c5f5-4a4e-b498-504bb2c23eb2, h0.example.com.: java.lang.NullPointerException at org.ovirt.engine.core.utils.ssh.EngineSSHDialog.useDefaultKeyPair(EngineSSHDialog.java:32) [utils.jar:] at org.ovirt.engine.core.bll.VdsDeploy.useDefaultKeyPair(VdsDeploy.java:804) [bll.jar:] at org.ovirt.engine.core.bll.InstallVdsCommand.executeCommand(InstallVdsCommand.java:170) [bll.jar:] at org.ovirt.engine.core.bll.ApproveVdsCommand.executeCommand(ApproveVdsCommand.java:49) [bll.jar:] at org.ovirt.engine.core.bll.CommandBase.executeWithoutTransaction(CommandBase.java:1065) [bll.jar:] at org.ovirt.engine.core.bll.CommandBase.executeActionInTransactionScope(CommandBase.java:1150) [bll.jar:] at org.ovirt.engine.core.bll.CommandBase.runInTransaction(CommandBase.java:1613) [bll.jar:] at org.ovirt.engine.core.utils.transaction.TransactionSupport.executeInSuppressed(TransactionSupport.java:174) [utils.jar:] at org.ovirt.engine.core.utils.transaction.TransactionSupport.executeInScope(TransactionSupport.java:116) [utils.jar:] at org.ovirt.engine.core.bll.CommandBase.execute(CommandBase.java:1168) [bll.jar:] at org.ovirt.engine.core.bll.CommandBase.executeAction(CommandBase.java:316) [bll.jar:] at org.ovirt.engine.core.bll.MultipleActionsRunner.executeValidatedCommand(MultipleActionsRunner.java:174) [bll.jar:] at org.ovirt.engine.core.bll.MultipleActionsRunner.RunCommands(MultipleActionsRunner.java:156) [bll.jar:] at org.ovirt.engine.core.bll.MultipleActionsRunner$1.run(MultipleActionsRunner.java:94) [bll.jar:] at org.ovirt.engine.core.utils.threadpool.ThreadPoolUtil$InternalWrapperRunnable.run(ThreadPoolUtil.java:71) [utils.jar:] at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) [rt.jar:1.7.0_09-icedtea] at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) [rt.jar:1.7.0_09-icedtea] at java.util.concurrent.FutureTask.run(FutureTask.java:166) [rt.jar:1.7.0_09-icedtea] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_09-icedtea] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_09-icedtea] at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_09-icedtea] -- Cheers Douglas ___ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
Re: [Engine-devel] NPE approving node
On 06/28/2013 02:22 PM, Alon Bar-Lev wrote: - Original Message - From: Douglas Schilling Landgraf dougsl...@redhat.com To: engine-devel@ovirt.org Cc: Alon Bar-Lev alo...@redhat.com, Yaniv Bronheim ybron...@redhat.com Sent: Friday, June 28, 2013 9:55:02 PM Subject: Re: [Engine-devel] NPE approving node On 06/27/2013 04:50 AM, Juan Hernandez wrote: Any idea why? Facing the same issue with updated tree. Cannot approve node. $ git log -1 commit b5438e34e0b179ef4f8ee20ce6e0d7b25cd2a36a This[1] should have fixed that. Can you please send the exception? [1] http://gerrit.ovirt.org/#/c/16184/ I have cleanup/refresh my working tree, looks like it's gone. Thanks! -- Cheers Douglas ___ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
[Engine-devel] Jenkins failure - findbugs failed: Timeout: killed the sub-process
Hi, Anyone else facing the below jenkins failure when sending patches to gerrit? [ERROR] Failed to execute goal org.codehaus.mojo:findbugs-maven-plugin:2.5.2:findbugs (default-cli) on project jboss-modules-maven-plugin: Execution default-cli of goal org.codehaus.mojo:findbugs-maven-plugin:2.5.2:findbugs failed: Timeout: killed the sub-process - [Help 1] http://jenkins.ovirt.org/job/ovirt_engine_find_bugs_gerrit/2650/ Thanks! -- Cheers Douglas ___ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
