Bug 889752 - adding local storage fails on AIO setup: 400 Bad request
Summary: adding local storage fails on AIO setup: 400 Bad request
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: sanlock
Version: 18
Hardware: Unspecified
OS: Linux
urgent
unspecified
Target Milestone: ---
Assignee: David Teigland
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: storage integration
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-12-23 09:55 UTC by Ohad Basan
Modified: 2014-10-30 22:34 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-01-24 10:37:43 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
engine setup log (106.06 KB, text/x-log)
2012-12-23 09:55 UTC, Ohad Basan
no flags Details

Description Ohad Basan 2012-12-23 09:55:24 UTC
Created attachment 667945 [details]
engine setup log

Description of problem:
when setting an all-in-one setup on a fedora18 system the setup fails during "adding local storage" phase

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


How reproducible:
always

Steps to Reproduce:
1.install ovirt-engine+all in one plugin on fedora18
2.run engine-setu
3.
  
Actual results:
setup quits with error 400

Expected results:

Comment 1 Moran Goldboim 2012-12-25 13:41:29 UTC
does it happen consistently? is it still happening.
if not, please close.

Comment 2 Ohad Basan 2012-12-25 17:01:59 UTC
this is not consistent
haven't seen it for a few days...
I'll reopen it if it occurs again.

Comment 3 Ohad Basan 2012-12-27 11:23:54 UTC
Reopened.
The problem persists.

Comment 4 Sandro Bonazzola 2013-01-22 16:03:13 UTC
I have experienced an error like this just today.
I had to set selinux policy to permissive and install sanlock from http://koji.fedoraproject.org/koji/buildinfo?buildID=377815 in order to successfully setup the system.

Comment 5 Ohad Basan 2013-01-24 10:37:43 UTC
This bug was solved in version 2.6-7 of sanlock package


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