Bug 827013 - after the change to build on fedora 17, installCA_dev.sh doesn't work (in devel env)
Summary: after the change to build on fedora 17, installCA_dev.sh doesn't work (in dev...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: oVirt
Classification: Retired
Component: ovirt-engine-core
Version: unspecified
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
: ---
Assignee: Juan Hernández
QA Contact:
URL:
Whiteboard: integration infra
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-05-31 12:35 UTC by Eyal Edri
Modified: 2012-10-25 16:33 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2012-10-25 16:33:06 UTC
oVirt Team: ---
Embargoed:


Attachments (Terms of Use)

Description Eyal Edri 2012-05-31 12:35:06 UTC
Description of problem:

after commit 22032921e004c69eded531503e5b314bc8f87366 to ovirt-engine

installCA_dev.sh fails on:

Write out database with 1 new entries
Data Base Updated
Certificate reply was installed in keystore
/bin/build-classpath: error: Could not find apache-commons-codec Java extension for this JVM
/bin/build-classpath: error: Could not find ovirt-engine/compat Java extension for this JVM
/bin/build-classpath: error: Could not find ovirt-engine/engineencryptutils Java extension for this JVM
/bin/build-classpath: error: Some specified jars were not found
Error: Could not find or load main class org.ovirt.engine.core.engineencryptutils.StoreUtils


this means that you must build and install ovirt-engine rpms on the f17,
which will deploy the missing jars to /usr/share/java/ovirt-engine.




Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.git clone lastet ovirt-engine
2.run installCA_dev.sh 
3.see failure.
  
Actual results:


Expected results:


Additional info:

Comment 1 Juan Hernández 2012-06-06 17:49:31 UTC
In order to solve this problem I am partially reverting the use of the build-classpath tool in the CA scripts, in particular in store-utils.sh and generate-ssh-keys. The proposed change is this:

http://gerrit.ovirt.org/5110

Comment 2 Juan Hernández 2012-10-25 16:33:06 UTC
This has been without the need for the change in comment #1.


Note You need to log in before you can comment on or make changes to this bug.