[Users] Trouble building Ovirt from source - "No rule to make target `install_tools'. Stop."

Juan Hernandez jhernand at redhat.com
Fri Mar 8 10:05:31 EST 2013


On 03/08/2013 03:51 PM, Juan Hernandez wrote:
> On 03/08/2013 03:49 PM, Yuval M wrote:
>> OK,
>> brand new machine,
>> Fedora 18 (x64),
>> Trying to install Ovirt 3.2 from sources according to:
>> http://www.ovirt.org/Building___Engine_Draft
>> <http://www.ovirt.org/Building_Engine_Draft>
>>
>> Everything is good up to the following stage:
>> "Now you need to do some adjustments to the configuration file
>> $HOME/ovirt-engine/installation/etc/sysconfig/ovirt-engine"
>>
>> The "sysconfig" directory does not exist. so does the "ovirt-engine"
>> configuration file (searched through the $HOME/ovirt-engine tree).
>> I didn't find any code in the Makefile
>> ($HOME/ovirt-engine/repository/Makefile) that would create them,
>> What am I missing?
>>
>
> This has changed recently and I didn't update that wiki page. The
> /etc/sysconig/ovirt-engine file has been replaced by
> /etc/ovirt-engine/engine.conf.
>

But wait, this change was made in the master branch, not in 3.2, so it 
shouldn't be a problem. Are you sure you are using the engine_3.2 branch?

>> Thanks,
>>
>> Yuval
>>
>> On Tue, Feb 26, 2013 at 3:25 PM, Juan Hernandez <jhernand at redhat.com
>> <mailto:jhernand at redhat.com>> wrote:
>>
>>      On 02/26/2013 02:19 PM, Doron Fediuck wrote:
>>
>>
>>
>>          ----- Original Message -----
>>
>>              From: "Yuval M" <yuvalme at gmail.com <mailto:yuvalme at gmail.com>>
>>              To: "Juan Hernandez" <jhernand at redhat.com
>>              <mailto:jhernand at redhat.com>>, users at ovirt.org
>>              <mailto:users at ovirt.org>
>>              Cc: "Limor Gavish" <lgavish at gmail.com
>>              <mailto:lgavish at gmail.com>>
>>              Sent: Sunday, February 24, 2013 11:38:12 PM
>>              Subject: Re: [Users] Trouble building Ovirt from source -
>>              "No rule to make target `install_tools'. Stop."
>>
>>
>>
>>
>>              Still having trouble with the build process (Ovirt 3.1):
>>              $ sudo make
>>              ... (success) ...
>>              $ sudo make install ...
>>
>>              inflating:
>>              /usr/local/share/ovirt-engine/__engine.ear/webadmin.war/META-__INF/maven/org.ovirt.engine.ui/__webadmin/pom.xml
>>              inflating:
>>              /usr/local/share/ovirt-engine/__engine.ear/webadmin.war/404.__html
>>              checkdir error:
>>              /usr/local/share/ovirt-engine/__engine.ear/engine-bll.jar
>>              exists but
>>              is not directory
>>              unable to process
>>              engine-bll.jar/org/ovirt/__engine/core/bll/VdsDeploy$32.__class.
>>              checkdir error:
>>              /usr/local/share/ovirt-engine/__engine.ear/engine-bll.jar
>>              exists but
>>              is not directory
>>              unable to process
>>              engine-bll.jar/org/ovirt/__engine/core/bll/__InitBackendServicesOnStartupBe__an.class.
>>              ...
>>              make: *** [install_artifacts] Error 2
>>
>>
>>
>>
>>              any insights?
>>
>>
>>              Thanks...
>>
>>
>>
>>              On Thu, Jan 24, 2013 at 8:52 PM, Juan Hernandez <
>>              jhernand at redhat.com <mailto:jhernand at redhat.com>
>>
>>                  wrote:
>>
>>
>>
>>
>>
>>              On 01/24/2013 04:20 PM, Yuval M wrote:
>>
>>
>>              Hi,
>>              I'm installing Ovirt 3.1 on Fedora using this guide:
>>              http://www.ovirt.org/Building_ oVirt_engine#Deploying_engine-
>>              config_.26_engine-manage- domains
>>
>>              and I'm getting the error in the subject from make.
>>              there is indeed no rule for install_tools in the makefile.
>>
>>              What am I missing?
>>
>>              Those instructions are out of date, use "make install". That
>>              installs
>>              the files, but you will still need some changes to make the
>>              engine
>>              work:
>>
>>              1. Create the ovirt user (the engine runs by default with this
>>              service, unless you change the /etc/syscofig/ovirt-engine
>>              file and
>>              add the ENGINE_USER and ENGINE_GROUP parameters):
>>
>>              useradd ovirt
>>
>>              2. Create (mkdir -p ...) and change the ownership of the
>>              directories
>>              that the engine needs to own to ovirt:ovirt (chown
>>              ovirt:ovirt ...):
>>
>>              /etc/ovirt-engine
>>              /var/log/ovirt-engine
>>              /var/lock/ovirt-engine
>>              /var/lib/ovirt-engine/content
>>              /var/lib/ovirt-engine/ deployments
>>              /var/tmp/ovirt-engine
>>              /var/cache/ovirt-engine
>>
>>              3. Enable the HTTP connector in the engine (the default is
>>              to enable
>>              only AJP, and that doesn't work without Apache as frontend)
>>              adding
>>              the following to the /etc/sysconfig/ovirt-engine file:
>>
>>              ENGINE_PROXY_ENABLED=false
>>              ENGINE_HTTP_ENABLED=true
>>              ENGINE_HTTP_PORT=8700
>>              ENGINE_HTTPS_ENABLED=false
>>              ENGINE_AJP_ENABLED=false
>>
>>              4. Configure database connection details (the default in
>>              development
>>              environments is to use the postgres user and the trust mode)
>>              adding
>>              this to /etc/sysconfig/ovirt-engine:
>>
>>              ENGINE_DB_USER=postgres
>>              ENGINE_DB_PASSWORD=
>>
>>              5. Make sure that you have the PostgreSQL JDBC driver
>>              installed (rpm
>>              -q postgresql-jdbc) and install it if needed (yum install
>>              postgresql-jdbc).
>>
>>              6. Now you can start the engine running the engine-service
>>              script:
>>
>>              engine-service start
>>
>>              Look at the system log (the file /var/log/messages) and the
>>              engine
>>              logs (the files /var/log/ovirt-engine/server. log and
>>              /var/log/ovirt-engine) for errors.
>>
>>              7. Connect to http://localhost:8700 and you should be able
>>              to login
>>              with user admin and letmein! as password.
>>
>>              Note that I am assuming that you already created the
>>              database, and
>>              that you want to use this installation for development. If
>>              you are
>>              looking for an production installation I suggest using the RPMs.
>>
>>              Also I tested this with the latest source from the
>>              repository, it
>>              will not work with older versions.
>>
>>              --
>>              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.
>>
>>
>>
>>          Any progress here?
>>
>>
>>      Yuval, that will not work with 3.1. Please use 3.2 and the following
>>      instructions:
>>
>>      http://www.ovirt.org/Building___Engine_Draft
>>      <http://www.ovirt.org/Building_Engine_Draft>
>>
>>
>>      --
>>      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.
>>
>>
>>
>>
>> _______________________________________________
>> Users mailing list
>> Users at ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
>>
>
>


-- 
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.


More information about the Users mailing list