Bug 1118818

Summary: Luns either missing from or having no 'volume_group_id' in the luns table in the RHEV database.
Product: Red Hat Enterprise Virtualization Manager Reporter: Gordon Watson <gwatson>
Component: ovirt-engineAssignee: Daniel Erez <derez>
Status: CLOSED ERRATA QA Contact: Ori Gofen <ogofen>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 3.3.0CC: acanan, amureini, derez, gwatson, iheim, lpeer, ogofen, rbalakri, Rhev-m-bugs, scohen, tnisan, yeylon
Target Milestone: ---   
Target Release: 3.5.0   
Hardware: x86_64   
OS: Linux   
Whiteboard: storage
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-02-11 18:05:42 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Storage RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1142923, 1156165    

Description Gordon Watson 2014-07-11 15:14:50 UTC
Description of problem:

There have been a couple of cases recently where luns that were already part of an existing domain were showing up as available for selection when editing a storage domain.

The reason was that the luns were missing from the luns table in the database or the 'volume_group_id' was null.

The database had to be modified manually to rectify this.


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

RHEV 3.3


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

The intent of this bug is to document that the database had to be modified manually in order to resolve the problem.

The steps taken to do this are in a subsequent private comment.

Comment 3 Allon Mureinik 2014-07-13 06:10:41 UTC
Daniel, don't your changes in 3.4 and 3.5 cover this?

Comment 8 Ori Gofen 2014-07-15 15:20:51 UTC
verified on oVirt 3.5 beta

Comment 10 errata-xmlrpc 2015-02-11 18:05:42 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHSA-2015-0158.html