Bug 798186 - engine setup: Failes when using seprate /usr partition
Summary: engine setup: Failes when using seprate /usr partition
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: oVirt
Classification: Retired
Component: ovirt-engine-installer
Version: unspecified
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
: ---
Assignee: Moran Goldboim
QA Contact:
URL:
Whiteboard: integration
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-02-28 09:20 UTC by W. de Heiden
Modified: 2012-12-17 07:26 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-12-17 07:26:33 UTC
oVirt Team: ---


Attachments (Terms of Use)

Description W. de Heiden 2012-02-28 09:20:36 UTC
Running engine-setup fails when using a seperate /var partion (seperated from  /) In /var/log/ovirt-engine/engine-setup_xxxxxxx.log:

  2012-02-18 14:46:16::ERROR::engine-setup::614::root:: Traceback
  (most
recent call last):
    File "/usr/bin/engine-setup", line 612, in _linkHttpParams
      os.link(target, link)
  OSError: [Errno 18] Invalid cross-device link

  2012-02-18 14:46:16::ERROR::engine-setup::728::root:: Traceback
  (most
recent call last):
    File "/usr/bin/engine-setup", line 712, in _editRootWar
      _linkHttpParams()
    File "/usr/bin/engine-setup", line 615, in _linkHttpParams
      raise Exception(output_messages.ERR_EXP_FAILED_ROOT_WAR)
  Exception: Could not copy ROOT.war configuration into Jboss profile

The installer tries to make a hard link to somewhere is /usr to /etc/ovirt-engine, which is not possible since /usr is on a separate
disk partition.

A workaround is to move /etc/overt-engine to
/usr/local/etc/ovirt-engine en create a symbolic link in /etc/

Comment 1 Ofer Schreiber 2012-05-08 07:58:21 UTC
We do the hard link since JBoss doesn't support symlinks yet.
This can be solved by http://gerrit.ovirt.org/#change,3782

Comment 2 Itamar Heim 2012-12-17 07:26:33 UTC
Closing old bugs. If this issue is still relevant/important in current version, please re-open the bug.


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