Bug 782567 - engine-setup: use symlink to vdsm-bootstrap script directory and not manually copy them
Summary: engine-setup: use symlink to vdsm-bootstrap script directory and not manually...
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: oVirt
Classification: Retired
Component: ovirt-engine-installer
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Ofer Schreiber
QA Contact:
URL:
Whiteboard: infra
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-01-17 17:51 UTC by Haim
Modified: 2014-01-13 00:50 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-07-25 09:31:20 UTC
oVirt Team: ---
Embargoed:

Attachments (Terms of Use)

Description Haim 2012-01-17 17:51:11 UTC 
Description of problem:


engine-setup copies all vdsm-bootstrap script to /usr/share/ovirt-engine/engine.ear/components.war/vds/ instead of having an a link to the original directory at /usr/share/vdsm-bootstrap. 
this configuration leads to bug where one decide to update\replace vdsm-bootstrap rpm (which is independent to engine-setup), and leaves him with old script downloaded to hosts.


git commit: d5d2d03f82d9c2a80a47407ddd6a3104c58c7314
Comment 1 Ofer Schreiber 2012-05-08 07:49:20 UTC 
We're coping the vdsm-bootstrap files since JBoss doesn't support symlinks yet.
Comment 2 Ofer Schreiber 2012-07-25 09:31:20 UTC 
Fixed. we're using a file servlet, no more symlinks/copy.
Note You need to log in before you can comment on or make changes to this bug.