- Devel - oVirt List Archives

[Engine-devel] Best place for new interfaces used by bll
by Ravi Nori 22 Mar '13

22 Mar '13

Hi, I am working on refactoring some of the backend code in bll and need to create interfaces so that I can eliminate the dependency between bll and the new module. Currently I created the interfaces in org.ovirt.engine.core.common.interfaces, but from what I understand this module is used by both frontend and backend. The new interfaces will only be used by the backend. What would be the best place to put these new interfaces? Ravi

6 6

[Engine-devel] Error during "Create new VM"
by Deepak C Shetty 21 Mar '13

21 Mar '13

Hi, I get the following error in the engine web gui while trying to create a new VM (server or desktop) Error: gvm: Cannot add VM if custom VM properties are in invalid format. Please check the input. Whats custom property is it talking about ? Under 'Custom Property' in new VM Dialog.. it has nothing.. it says "no properties" I am on a git based engine setup.... trying to validate gluster storage domain, but unable to proceed from this step. Any workarounds/inputs appreciate thanx, deepak

2 4

[Engine-devel] watchdog patchset
by Laszlo Hornyak 21 Mar '13

21 Mar '13

Hi, The watchdog patch was broken down into a patchset: http://gerrit.ovirt.org/13057 http://gerrit.ovirt.org/13058 http://gerrit.ovirt.org/13059 http://gerrit.ovirt.org/13060 You are welcome to review it, it is working, however due to internal changes it is being completely rewritten. Laszlo

1 0

[Engine-devel] Features requests for the setup/configuration utilities - feedback requested
by Alex Lourie 19 Mar '13

19 Mar '13

Hi All As we are working on the configuration utilities (engine-setup, engine-upgrade and engine-cleanup), we would like to get as much community involvement as possible. As such, we'd like to hear the wishes of the community in regards with those tools. I've created a wiki page [1] where we will keep the list of feature requests. We would appreciate adding features to the list of by replying to this thread directly. Please do not bugs to that list - the bugs should be resolved in due course according to their priorities and should not affect the features that we would like to implement. Thank you. [1] http://www.ovirt.org/Features/Engine-Config-Utilities -- Alex Lourie Software Engineer in RHEVM Integration Red Hat

4 10

[Engine-devel] Controlling GWT compiler JVM arguments
by Vojtech Szocs 19 Mar '13

19 Mar '13

Hi guys, for those of you getting "Exception: java.lang.OutOfMemoryError" or similar errors during GWT compilation of WebAdmin/UserPortal, it's now possible to override default JVM arguments for GWT compiler via command line. For example: $ mvn clean install -Pdep,gwt-admin,gwt-user -Dgwt-plugin.extraJvmArgs="-Xms1024M -Xmx2048M -XX:PermSize=256M -XX:MaxPermSize=512M" Note: you can find default "gwt-plugin.extraJvmArgs" value in $OVIRT_HOME/frontend/webadmin/modules/pom.xml Regards, Vojtech

1 0

[Engine-devel] vfs_type not being sent by engine to VDSM for GLUSTER DOMAIN case
by Deepak C Shetty 19 Mar '13

19 Mar '13

This is a multi-part message in MIME format. --------------040206010801040103040709 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit I by mistake sent this earlier to users@ovirt I think the right list is engine-devel, hence resending. Sorry for the mispost earlier. -------- Original Message -------- Subject: vfs_type not being sent by engine to VDSM for GLUSTER DOMAIN case Date: Mon, 18 Mar 2013 20:23:57 +0530 From: Deepak C Shetty <deepakcs(a)linux.vnet.ibm.com> Organization: IBM India Pvt. Ltd. To: users(a)ovirt.org <users(a)ovirt.org>, Sharad Mishra <snmishra(a)us.ibm.com> Hi All, I am validating GLUSTERFS Storage domain engine patches (worked on by Sharad, in Cc) as posted here... http://gerrit.ovirt.org/#/q/status:open+project:ovirt-engine+branch:master+… against VDSM Glusterfs domain support (already upstream in VDSM) I see the below issue as part of me creatign a new Gluster Storage DOmain in the UI Engine logs... 2013-03-18 13:27:29,149 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.ConnectStorageServerVDSCommand] (http--0.0.0.0-8700-1) [4b751967] START, ConnectStorageServerVDSCommand(HostName = vm-vdsm-de-1, HostId = c0ff5edc-4e30-4553-9125-2d1cee9f19ec, storagePoolId = 00000000-0000-0000-0000-000000000000, storageType = GLUSTERFS, connectionList = [{ id: null, connection: vm-vdsm-de-1:dpkvol4, iqn: null, vfsType: glusterfs, mountOptions: null, nfsVersion: null, nfsRetrans: null, nfsTimeo: null };]), log id: f88d42d VDSM Logs... Thread-77::INFO::2013-03-18 13:32:35,541::logUtils::44::dispatcher::(wrapper) Run and protect: connectStorageServer(domType=7, spUUID='00000000-0000-0000-0000-000000000000', conList=[{'connection': 'vm-vdsm-de-1:dpkvol4', 'iqn': '', 'portal': '', 'user': '', 'password': '******', 'id': '00000000-0000-0000-0000-000000000000', 'port': ''}], options=None)*--> Notice no vfs_type here !!!* VDSM doesn't recv. the vfs_type in the conList dict !!! I had this small chat with Saggi of VDSM, just to confirm that there isn't a possibility that VDSM might be stripping args that are recd. from Engine.. and it doesn't. --------------------------------------------------------------------------------------------------------------------- <deepakcs> saggi, Hi <saggi> deepakcs: hi <deepakcs> saggi, Is it possible that VDSM might strip down some of the connparams that are recd. as part of connectStorageServer ? <deepakcs> saggi, In engine log for GLUSTERFS_DOMAIN i see vfsType being passed, but connectStorageServer log doesn't show vfs_type in the params dict <deepakcs> saggi, so wodering where vfs_type is getting dropped in this whole process <saggi> Probably not being sent <saggi> if it's not being logged <deepakcs> saggi, engine log has this.... <deepakcs> 2013-03-18 13:27:29,149 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.ConnectStorageServerVDSCommand] (http--0.0.0.0-8700-1) [4b751967] START, ConnectStorageServerVDSCommand(HostName = vm-vdsm-de-1, HostId = c0ff5edc-4e30-4553-9125-2d1cee9f19ec, storagePoolId = 00000000-0000-0000-0000-000000000000, storageType = GLUSTERFS, connectionList = [{ id: null, connection: vm-vdsm-de-1:dpkvol4, iqn: null, vfsType: glusterfs, mountOptions: null, nfsVersion: nul <deepakcs> l, nfsRetrans: null, nfsTimeo: null };]), log id: f88d42d <deepakcs> saggi, on VDSM side i see this... <deepakcs> Thread-77::INFO::2013-03-18 13:32:35,541::logUtils::44::dispatcher::(wrapper) Run and protect: connectStorageServer(domType=7, spUUID='00000000-0000-0000-0000-000000000000', conList=[{'connection': 'vm-vdsm-de-1:dpkvol4', 'iqn': '', 'portal': '', 'user': '', 'password': '******', 'id': '00000000-0000-0000-0000-000000000000', 'port': ''}], options=None) --> Notice no vfs_type here !!! <saggi> Then you are not sending the correct connection type <deepakcs> saggi, 'you' means the engine side of code ? engine patches is being done by Sharad, and I amtrying to work with them on this issue <deepakcs> saggi, domType=7 is GLUSTERFS_DOMAIN, so its correct on that front <saggi> If it show nfsRetrans you are using nfs which doesn't have a vfs_type argument <deepakcs> saggi, but engine log says storageType = GLUSTERFS <deepakcs> saggi, maybe i can send mail to users@ovirt list to see if anybody can provide more clues <deepakcs> saggi, but definitely this doesn't looks like a vdsm side of issue rite ? <saggi> We log the params as we get them <deepakcs> saggi, right, thats what i also see.. just wanted to confirm once with you, before i sent mail to ovirt folks --------------------------------------------------------------------------------------------------------------------- Can someone help provide any clues on what might be the issue here ? Because VDSM doesn't see vfs_type, the connectStorageServer fails and hence new SD cannot be created ! thanx, deepak --------------040206010801040103040709 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit <html> <head> <meta http-equiv="content-type" content="text/html; charset=ISO-8859-1"> </head> <body bgcolor="#FFFFFF" text="#000000"> <tt>I by mistake sent this earlier to users@ovirt<br> I think the right list is engine-devel, hence resending. Sorry for the mispost earlier.<br> </tt> <div class="moz-forward-container"><br> <br> -------- Original Message -------- <table class="moz-email-headers-table" border="0" cellpadding="0" cellspacing="0"> <tbody> <tr> <th align="RIGHT" nowrap="nowrap" valign="BASELINE">Subject: </th> <td>vfs_type not being sent by engine to VDSM for GLUSTER DOMAIN case</td> </tr> <tr> <th align="RIGHT" nowrap="nowrap" valign="BASELINE">Date: </th> <td>Mon, 18 Mar 2013 20:23:57 +0530</td> </tr> <tr> <th align="RIGHT" nowrap="nowrap" valign="BASELINE">From: </th> <td>Deepak C Shetty <a class="moz-txt-link-rfc2396E" href="mailto:deepakcs@linux.vnet.ibm.com"><deepakcs(a)linux.vnet.ibm.com></a></td> </tr> <tr> <th align="RIGHT" nowrap="nowrap" valign="BASELINE">Organization: </th> <td>IBM India Pvt. Ltd.</td> </tr> <tr> <th align="RIGHT" nowrap="nowrap" valign="BASELINE">To: </th> <td><a class="moz-txt-link-abbreviated" href="mailto:users@ovirt.org">users(a)ovirt.org</a> <a class="moz-txt-link-rfc2396E" href="mailto:users@ovirt.org"><users(a)ovirt.org></a>, Sharad Mishra <a class="moz-txt-link-rfc2396E" href="mailto:snmishra@us.ibm.com"><snmishra(a)us.ibm.com></a></td> </tr> </tbody> </table> <br> <br> <meta http-equiv="content-type" content="text/html; charset=ISO-8859-1"> <tt>Hi All,<br>     I am validating GLUSTERFS Storage domain engine patches (worked on by Sharad, in Cc) as posted here...<br> <a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://gerrit.ovirt.org/#/q/status:open+project:ovirt-engine+branch:master+…">http://gerrit.ovirt.org/#/q/status:open+project:ovirt-engine+branch:master+…</a><br> against VDSM Glusterfs domain support (already upstream in VDSM)<br> <br> I see the below issue as part of me creatign a new Gluster Storage DOmain in the UI<br> <br> Engine logs...<br> <br> 2013-03-18 13:27:29,149 INFO  [org.ovirt.engine.core.vdsbroker.vdsbroker.ConnectStorageServerVDSCommand] (http--0.0.0.0-8700-1) [4b751967] START, ConnectStorageServerVDSCommand(HostName = vm-vdsm-de-1, HostId = c0ff5edc-4e30-4553-9125-2d1cee9f19ec, storagePoolId = 00000000-0000-0000-0000-000000000000, storageType = GLUSTERFS, connectionList = [{ id: null, connection: vm-vdsm-de-1:dpkvol4, iqn: null, vfsType: glusterfs, mountOptions: null, nfsVersion: null, nfsRetrans: null, nfsTimeo: null };]), log id: f88d42d<br> <br> VDSM Logs...<br> <br> Thread-77::<a moz-do-not-send="true" class="moz-txt-link-freetext" href="INFO::2013-03-18">INFO::2013-03-18</a> 13:32:35,541::logUtils::44::dispatcher::(wrapper) Run and protect: connectStorageServer(domType=7, spUUID='00000000-0000-0000-0000-000000000000', conList=[{'connection': 'vm-vdsm-de-1:dpkvol4', 'iqn': '', 'portal': '', 'user': '', 'password': '******', 'id': '00000000-0000-0000-0000-000000000000', 'port': ''}], options=None)<b> --> Notice no vfs_type here !!!</b><br> <br> VDSM doesn't recv. the vfs_type in the conList dict !!!<br> <br> I had this small chat with Saggi of VDSM, just to confirm that there isn't a possibility that VDSM might be stripping args that are recd. from Engine.. and it doesn't.<br> <br> </tt><br> <tt><tt>---------------------------------------------------------------------------------------------------------------------<br> </tt><deepakcs> saggi, Hi<br> <saggi> deepakcs: hi<br> <br> <deepakcs> saggi, Is it possible that VDSM might strip down some of the connparams that are recd. as part of connectStorageServer ?<br> <deepakcs> saggi, In engine log for GLUSTERFS_DOMAIN i see vfsType being passed, but connectStorageServer log doesn't show vfs_type in the params dict<br> <deepakcs> saggi, so wodering where vfs_type is getting dropped in this whole process<br> <saggi> Probably not being sent<br> <saggi> if it's not being logged<br> <deepakcs> saggi, engine log has this....<br> <deepakcs> 2013-03-18 13:27:29,149 INFO  [org.ovirt.engine.core.vdsbroker.vdsbroker.ConnectStorageServerVDSCommand] (http--0.0.0.0-8700-1) [4b751967] START, ConnectStorageServerVDSCommand(HostName = vm-vdsm-de-1, HostId = c0ff5edc-4e30-4553-9125-2d1cee9f19ec, storagePoolId = 00000000-0000-0000-0000-000000000000, storageType = GLUSTERFS, connectionList = [{ id: null, connection: vm-vdsm-de-1:dpkvol4, iqn: null, vfsType: glusterfs, mountOptions: null, nfsVersion: nul<br> <deepakcs> l, nfsRetrans: null, nfsTimeo: null };]), log id: f88d42d<br> <deepakcs> saggi,  on VDSM side i see this...<br> <deepakcs> Thread-77::<a moz-do-not-send="true" class="moz-txt-link-freetext" href="INFO::2013-03-18">INFO::2013-03-18</a> 13:32:35,541::logUtils::44::dispatcher::(wrapper) Run and protect: connectStorageServer(domType=7, spUUID='00000000-0000-0000-0000-000000000000', conList=[{'connection': 'vm-vdsm-de-1:dpkvol4', 'iqn': '', 'portal': '', 'user': '', 'password': '******', 'id': '00000000-0000-0000-0000-000000000000', 'port': ''}], options=None) --> Notice no vfs_type here !!!<br> <saggi> Then you are not sending the correct connection type<br> <br> <deepakcs> saggi, 'you' means the engine side of code ? engine patches is being done by Sharad, and I amtrying to work with them on this issue<br> <br> <deepakcs> saggi, domType=7 is GLUSTERFS_DOMAIN, so its correct on that front<br> <saggi> If it show nfsRetrans you are using nfs which doesn't have a vfs_type argument<br> <deepakcs> saggi, but engine log says storageType = GLUSTERFS<br> <deepakcs> saggi, maybe i can send mail to users@ovirt list to see if anybody can provide more clues<br> <deepakcs> saggi, but definitely this doesn't looks like a vdsm side of issue rite ?<br> <saggi> We log the params as we get them<br> <br> <deepakcs> saggi, right, thats what i also see.. just wanted to confirm once with you, before i sent mail to ovirt folks<br> <br> ---------------------------------------------------------------------------------------------------------------------<br> <br> <br> Can someone help provide any clues on what might be the issue here ?<br> Because VDSM doesn't see vfs_type, the connectStorageServer fails and hence new SD cannot be created !<br> <br> thanx,<br> deepak<br> <br> </tt><br> <br> </div> <br> </body> </html> --------------040206010801040103040709--

3 2

[Engine-devel] restapi - domains
by Shireesh Anjal 18 Mar '13

18 Mar '13

Hi, We are trying to develop a simple android app to monitor and manage gluster clusters by consuming the restapi exposed by engine. The first screen is the login screen, which is similar to the webadmin login screen. Here, we want to populate the combo box of "domains" by fetching it from the restapi. However, the domains api cannot be invoked without authentication! So we have a sort of a chicken-and-egg problem. Any suggestions on how to tackle this? I feel the "domains" api should be "public", in the sense it should not expect authentication. Regards, Shireesh

6 9

[Engine-devel] [ATTANTION] NetworkManager - STP
by Alon Bar-Lev 18 Mar '13

18 Mar '13

Hello, On recent fedora-18 NetworkManager started to set default STP for the bridges to on, this is a change in the default of distribution, which up until now was off, I opened a bug[1]. If you experiencing disconnect of hosts from network due to STP detection, a workaround is available. Simply add: --- STP="off" --- To the wired interfaces (eth0, em1...) before host deployment, this will be copied to the management bridge and will prevent NetworkManager to use its default. Regards, Alon Bar-Lev. [1] https://bugzilla.redhat.com/show_bug.cgi?id=922702

1 0

[Engine-devel] Proposal for support ISO domain on other types of file based storage.
by Mark Wu 18 Mar '13

18 Mar '13

This is a multi-part message in MIME format. --------------070305010507040809030004 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Hi guys, Currently, ISO domain is only supported on NFS storage. It could improve the ease of use if it allows other types of file based storage to store ISO images. After an investigation, I found there's not any restriction on this idea. So the whole work is removing the limitation on engine side. That means engine should allow ISO domain could have different storage type from the data center it's attached, like what we do with nfs ISO domain in SAN DC. I start this idea with localfs. I know local storage can't be seen in cluster level. But it also provides a choice if no NFS available. VMs can be created on the host which has the ISO repo, and then be migrated to any other host in the cluster. I have done the initial patches: allow creation ISO domain on localfs [1] and support import ISO domain on localfs [2] I don't have much experience in java/j2ee/web development and engine architecture. The patches just work for me. I am not sure if it will bring some potential problems. So any feedback on the patch or the idea will be appreciated very much. Mark. [1] http://gerrit.ovirt.org/#/c/12687/ [2] http://gerrit.ovirt.org/#/c/12916/ --------------070305010507040809030004 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit <html> <head> <meta http-equiv="content-type" content="text/html; charset=ISO-8859-1"> </head> <body bgcolor="#FFFFFF" text="#000000"> Hi guys, <br> <br> Currently, ISO domain is only supported on NFS storage.  It could improve the ease of use if it allows other types<br> of file based storage to store ISO images. After an investigation,  I found there's not any restriction on this idea.<br> So the whole work is removing the limitation on engine side.  That means engine should allow ISO domain could <br> have different storage type from the data center it's attached, like what we do with nfs ISO domain in SAN DC.<br> <br> I start this idea with localfs. I know local storage can't be seen in cluster level. But it also provides a choice if no<br> NFS available. VMs can be created on the host which has the ISO repo, and then be migrated to any other host in the cluster.<br> I have done the initial patches: allow creation ISO domain on localfs [1] and support import ISO domain on localfs [2]<br> I don't have much experience in java/j2ee/web development and engine architecture.  The patches just work for me.<br> I am not sure if it will bring some potential problems.  So any feedback on the patch or  the idea will be appreciated very much.<br> <br> <br> Mark.<br> <meta http-equiv="content-type" content="text/html; charset=ISO-8859-1"> <br> [1] <a href="http://gerrit.ovirt.org/#/c/12687/">http://gerrit.ovirt.org/#/c/12687/</a><br> [2] <meta http-equiv="content-type" content="text/html; charset=ISO-8859-1"> <a href="http://gerrit.ovirt.org/#/c/12916/">http://gerrit.ovirt.org/#/c/12916/<br> </a> </body> </html> --------------070305010507040809030004--

3 9

[Engine-devel] make rpm error: No targets specified and no makefile found. Stop
by qyddbear 18 Mar '13

18 Mar '13

------=_Part_279309_491577683.1363594708599 Content-Type: text/plain; charset=GBK Content-Transfer-Encoding: 7bit Hi, I am a green learner, I tried to make ovirt-engine rpm from compiled source code. when I run make rpm, and the log as follows. Can anyone tell me what's the matter? Thanks! [root@localhost ovirt-engine-3.1.0]# make rpm sed -e 's/@PACKAGE_VERSION@/3.1.0/g' \ -e 's/@PACKAGE_RELEASE@/3.26/g' packaging/fedora/spec/ovirt-engine.spec.in > ovirt-engine.spec git ls-files | tar --files-from /proc/self/fd/0 -czf ovirt-engine-3.1.0.tar.gz ovirt-engine.spec rm -f ovirt-engine.spec You can use rpmbuild -tb ovirt-engine-3.1.0.tar.gz to produce rpms rm -rf /home/wqx/ovirt-engine-3.1.0/tmp.rpmbuild mkdir -p /home/wqx/ovirt-engine-3.1.0/tmp.rpmbuild/{SPECS,RPMS,SRPMS,SOURCES,BUILD,BUILDROOT} mkdir -p output rpmbuild -ts --define="_topdir /home/wqx/ovirt-engine-3.1.0/tmp.rpmbuild" ovirt-engine-3.1.0.tar.gz Wrote: /home/wqx/ovirt-engine-3.1.0/tmp.rpmbuild/SRPMS/ovirt-engine-3.1.0-3.26.el6.src.rpm mv /home/wqx/ovirt-engine-3.1.0/tmp.rpmbuild/SRPMS/*.rpm output rm -rf /home/wqx/ovirt-engine-3.1.0/tmp.rpmbuild srpm is ready at output rm -rf /home/wqx/ovirt-engine-3.1.0/tmp.rpmbuild mkdir -p /home/wqx/ovirt-engine-3.1.0/tmp.rpmbuild/{SPECS,RPMS,SRPMS,SOURCES,BUILD,BUILDROOT} mkdir -p output rpmbuild --define="_topdir /home/wqx/ovirt-engine-3.1.0/tmp.rpmbuild" --rebuild output/ovirt-engine-3.1.0*.src.rpm Installing output/ovirt-engine-3.1.0-3.26.el6.src.rpm Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.3JQHHM + umask 022 + cd /home/wqx/ovirt-engine-3.1.0/tmp.rpmbuild/BUILD + LANG=C + export LANG + unset DISPLAY + cd /home/wqx/ovirt-engine-3.1.0/tmp.rpmbuild/BUILD + rm -rf ovirt-engine-3.1.0 + /bin/mkdir -p ovirt-engine-3.1.0 + cd ovirt-engine-3.1.0 + /bin/tar -xf - + /usr/bin/gzip -dc /home/wqx/ovirt-engine-3.1.0/tmp.rpmbuild/SOURCES/ovirt-engine-3.1.0.tar.gz + STATUS=0 + '[' 0 -ne 0 ']' + /bin/chmod -Rf a+rX,u+w,g-w,o-w . + exit 0 Executing(%build): /bin/sh -e /var/tmp/rpm-tmp.qesWT3 + umask 022 + cd /home/wqx/ovirt-engine-3.1.0/tmp.rpmbuild/BUILD + cd ovirt-engine-3.1.0 + LANG=C + export LANG + unset DISPLAY + make -j1 PACKAGE_NAME=ovirt-engine ENGINE_NAME=ovirt-engine LOCALSTATE_DIR=/var ENGINE_STATE=/var/lib/ovirt-engine PREFIX=/usr SYSCONF_DIR=/etc BIN_DIR=/usr/bin DATAROOT_DIR=/usr/share MAN_DIR=/usr/share/man PYTHON=/usr/bin/python PYTHON_DIR=/usr/lib/python2.6/site-packages JAVA_DIR=/usr/share/java MAVENPOM_DIR=/usr/share/maven2/poms PKG_JAVA_DIR=/usr/share/java/ovirt-engine PKG_SYSCONF_DIR=/etc/ovirt-engine PKG_EAR_DIR=/usr/share/ovirt-engine/engine.ear PKG_PKI_DIR=/etc/pki/ovirt-engine PKG_JBOSS_MODULES=/usr/share/ovirt-engine/modules make[1]: Entering directory `/home/wqx/ovirt-engine-3.1.0/tmp.rpmbuild/BUILD/ovirt-engine-3.1.0' make[1]: *** No targets specified and no makefile found. Stop. make[1]: Leaving directory `/home/wqx/ovirt-engine-3.1.0/tmp.rpmbuild/BUILD/ovirt-engine-3.1.0' error: Bad exit status from /var/tmp/rpm-tmp.qesWT3 (%build) RPM build errors: Bad exit status from /var/tmp/rpm-tmp.qesWT3 (%build) make: *** [rpm] Error 1 There is a ovirt-engine.spec under /home/wqx/ovirt-engine-3.1.0/tmp.rpmbuild/BUILD/ovirt-engine-3.1.0 ------=_Part_279309_491577683.1363594708599 Content-Type: text/html; charset=GBK Content-Transfer-Encoding: 7bit <div style="line-height:1.7;color:#000000;font-size:14px;font-family:arial"><div style="line-height:1.7;color:#000000;font-size:14px;font-family:arial"><div>Hi, I am a green learner, I tried to make ovirt-engine rpm from compiled source code. when I run make rpm, and the log as follows. Can anyone tell me what's the matter? Thanks!</div><div><br></div><div>[root@localhost ovirt-engine-3.1.0]# make rpm</div><div><span style="background-color: rgb(192, 192, 192);">sed -e 's/@PACKAGE_VERSION@/3.1.0/g' \</span></div><div><span style="background-color: rgb(192, 192, 192);">            -e 's/@PACKAGE_RELEASE@/3.26/g' packaging/fedora/spec/ovirt-engine.spec.in > ovirt-engine.spec</span></div><div><span style="background-color: rgb(192, 192, 192);">git ls-files | tar --files-from /proc/self/fd/0 -czf ovirt-engine-3.1.0.tar.gz ovirt-engine.spec</span></div><div><span style="background-color: rgb(192, 192, 192);">rm -f ovirt-engine.spec</span></div><div><span style="background-color: rgb(192, 192, 192);"><br></span></div><div><span style="background-color: rgb(192, 192, 192);">You can use rpmbuild -tb ovirt-engine-3.1.0.tar.gz to produce rpms</span></div><div><span style="background-color: rgb(192, 192, 192);"><br></span></div><div><span style="background-color: rgb(192, 192, 192);">rm -rf /home/wqx/ovirt-engine-3.1.0/tmp.rpmbuild</span></div><div><span style="background-color: rgb(192, 192, 192);">mkdir -p /home/wqx/ovirt-engine-3.1.0/tmp.rpmbuild/{SPECS,RPMS,SRPMS,SOURCES,BUILD,BUILDROOT}</span></div><div><span style="background-color: rgb(192, 192, 192);">mkdir -p output</span></div><div><span style="background-color: rgb(192, 192, 192);">rpmbuild -ts --define="_topdir /home/wqx/ovirt-engine-3.1.0/tmp.rpmbuild" ovirt-engine-3.1.0.tar.gz</span></div><div><span style="background-color: rgb(192, 192, 192);">Wrote: /home/wqx/ovirt-engine-3.1.0/tmp.rpmbuild/SRPMS/ovirt-engine-3.1.0-3.26.el6.src.rpm</span></div><div><span style="background-color: rgb(192, 192, 192);">mv /home/wqx/ovirt-engine-3.1.0/tmp.rpmbuild/SRPMS/*.rpm output</span></div><div><span style="background-color: rgb(192, 192, 192);">rm -rf /home/wqx/ovirt-engine-3.1.0/tmp.rpmbuild</span></div><div><span style="background-color: rgb(192, 192, 192);"><br></span></div><div><span style="background-color: rgb(192, 192, 192);">srpm is ready at output</span></div><div><span style="background-color: rgb(192, 192, 192);"><br></span></div><div><span style="background-color: rgb(192, 192, 192);">rm -rf /home/wqx/ovirt-engine-3.1.0/tmp.rpmbuild</span></div><div><span style="background-color: rgb(192, 192, 192);">mkdir -p /home/wqx/ovirt-engine-3.1.0/tmp.rpmbuild/{SPECS,RPMS,SRPMS,SOURCES,BUILD,BUILDROOT}</span></div><div><span style="background-color: rgb(192, 192, 192);">mkdir -p output</span></div><div><span style="background-color: rgb(192, 192, 192);">rpmbuild --define="_topdir /home/wqx/ovirt-engine-3.1.0/tmp.rpmbuild"  --rebuild output/ovirt-engine-3.1.0*.src.rpm</span></div><div><span style="background-color: rgb(192, 192, 192);">Installing output/ovirt-engine-3.1.0-3.26.el6.src.rpm</span></div><div><span style="background-color: rgb(192, 192, 192);">Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.3JQHHM</span></div><div><span style="background-color: rgb(192, 192, 192);">+ umask 022</span></div><div><span style="background-color: rgb(192, 192, 192);">+ cd /home/wqx/ovirt-engine-3.1.0/tmp.rpmbuild/BUILD</span></div><div><span style="background-color: rgb(192, 192, 192);">+ LANG=C</span></div><div><span style="background-color: rgb(192, 192, 192);">+ export LANG</span></div><div><span style="background-color: rgb(192, 192, 192);">+ unset DISPLAY</span></div><div><span style="background-color: rgb(192, 192, 192);">+ cd /home/wqx/ovirt-engine-3.1.0/tmp.rpmbuild/BUILD</span></div><div><span style="background-color: rgb(192, 192, 192);">+ rm -rf ovirt-engine-3.1.0</span></div><div><span style="background-color: rgb(192, 192, 192);">+ /bin/mkdir -p ovirt-engine-3.1.0</span></div><div><span style="background-color: rgb(192, 192, 192);">+ cd ovirt-engine-3.1.0</span></div><div><span style="background-color: rgb(192, 192, 192);">+ /bin/tar -xf -</span></div><div><span style="background-color: rgb(192, 192, 192);">+ /usr/bin/gzip -dc /home/wqx/ovirt-engine-3.1.0/tmp.rpmbuild/SOURCES/ovirt-engine-3.1.0.tar.gz</span></div><div><span style="background-color: rgb(192, 192, 192);">+ STATUS=0</span></div><div><span style="background-color: rgb(192, 192, 192);">+ '[' 0 -ne 0 ']'</span></div><div><span style="background-color: rgb(192, 192, 192);">+ /bin/chmod -Rf a+rX,u+w,g-w,o-w .</span></div><div><span style="background-color: rgb(192, 192, 192);">+ exit 0</span></div><div><span style="background-color: rgb(192, 192, 192);">Executing(%build): /bin/sh -e /var/tmp/rpm-tmp.qesWT3</span></div><div><span style="background-color: rgb(192, 192, 192);">+ umask 022</span></div><div><span style="background-color: rgb(192, 192, 192);">+ cd /home/wqx/ovirt-engine-3.1.0/tmp.rpmbuild/BUILD</span></div><div><span style="background-color: rgb(192, 192, 192);">+ cd ovirt-engine-3.1.0</span></div><div><span style="background-color: rgb(192, 192, 192);">+ LANG=C</span></div><div><span style="background-color: rgb(192, 192, 192);">+ export LANG</span></div><div><span style="background-color: rgb(192, 192, 192);">+ unset DISPLAY</span></div><div><span style="background-color: rgb(192, 192, 192);">+ make -j1 PACKAGE_NAME=ovirt-engine ENGINE_NAME=ovirt-engine LOCALSTATE_DIR=/var ENGINE_STATE=/var/lib/ovirt-engine PREFIX=/usr SYSCONF_DIR=/etc BIN_DIR=/usr/bin DATAROOT_DIR=/usr/share MAN_DIR=/usr/share/man PYTHON=/usr/bin/python PYTHON_DIR=/usr/lib/python2.6/site-packages JAVA_DIR=/usr/share/java MAVENPOM_DIR=/usr/share/maven2/poms PKG_JAVA_DIR=/usr/share/java/ovirt-engine PKG_SYSCONF_DIR=/etc/ovirt-engine PKG_EAR_DIR=/usr/share/ovirt-engine/engine.ear PKG_PKI_DIR=/etc/pki/ovirt-engine PKG_JBOSS_MODULES=/usr/share/ovirt-engine/modules</span></div><div><span style="background-color: rgb(192, 192, 192);">make[1]: Entering directory `/home/wqx/ovirt-engine-3.1.0/tmp.rpmbuild/BUILD/ovirt-engine-3.1.0'</span></div><div><b style="background-color: rgb(192, 192, 192);">make[1]: *** No targets specified and no makefile found.  Stop.</b></div><div><span style="background-color: rgb(192, 192, 192);">make[1]: Leaving directory `/home/wqx/ovirt-engine-3.1.0/tmp.rpmbuild/BUILD/ovirt-engine-3.1.0'</span></div><div><span style="background-color: rgb(192, 192, 192);">error: Bad exit status from /var/tmp/rpm-tmp.qesWT3 (%build)</span></div><div><span style="background-color: rgb(192, 192, 192);"><br></span></div><div><span style="background-color: rgb(192, 192, 192);"><br></span></div><div><span style="background-color: rgb(192, 192, 192);">RPM build errors:</span></div><div><span style="background-color: rgb(192, 192, 192);">    Bad exit status from /var/tmp/rpm-tmp.qesWT3 (%build)</span></div><div><span style="background-color: rgb(192, 192, 192);">make: *** [rpm] Error 1</span></div><div><br></div><div><br></div><div>There is a ovirt-engine.spec under /home/wqx/ovirt-engine-3.1.0/tmp.rpmbuild/BUILD/ovirt-engine-3.1.0 </div><div><br></div><div><br></div></div></div><br><br><span title="neteasefooter"><span id="netease_mail_footer"></span></span> ------=_Part_279309_491577683.1363594708599--

2 3