Bug 1064777 - NPE is shown in the log while discovering new gluster volumes
Summary: NPE is shown in the log while discovering new gluster volumes
Keywords:
Status: CLOSED DUPLICATE of bug 1220263
Alias: None
Product: oVirt
Classification: Retired
Component: ovirt-engine-core
Version: 3.4
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 3.6.0
Assignee: Kanagaraj
QA Contact: bugs@ovirt.org
URL:
Whiteboard: gluster
Depends On:
Blocks: rhsc_qe_tracker_everglades
TreeView+ depends on / blocked
 
Reported: 2014-02-13 09:48 UTC by Kanagaraj
Modified: 2016-04-18 10:07 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-05-12 10:27:38 UTC
oVirt Team: Gluster
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 40799 0 master MERGED engine: Fixed issue with null brick during sync Never

Description Kanagaraj 2014-02-13 09:48:30 UTC
Description of problem:
NPE is thrown while the gluster sync discovers a new gluster volume which was created through gluster CLI and one of the bricks is present in a host which is not yet added to engine.


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


How reproducible:


Steps to Reproduce:
1. Create a new gluster cluster 
2. Add host1 to the cluster
3. Goto gluster CLI of host1 and peer probe host2
4. In gluster CLI, create a new distribute volume with one brick in each host
5. Observe engine log, a NPE will be thrown

Actual results:
NPE is seen in engine log


Expected results:
NPE should not be present, instead a warning should be shown to convey that respective host is not yet added/available in engine


Additional info:

Comment 1 Sandro Bonazzola 2014-03-04 09:28:01 UTC
This is an automated message.
Re-targeting all non-blocker bugs still open on 3.4.0 to 3.4.1.

Comment 2 Sandro Bonazzola 2014-05-08 13:55:50 UTC
This is an automated message.

oVirt 3.4.1 has been released.
This issue has been retargeted to 3.5.0 since it has not been marked as high priority or severity issue, please retarget if needed.

Comment 3 Sandro Bonazzola 2015-01-21 16:08:43 UTC
oVirt 3.5.1 has been released, re-targeting to 3.6.0 as not marked as urgent / high severity or priority

Comment 4 Sahina Bose 2015-05-12 10:27:38 UTC

*** This bug has been marked as a duplicate of bug 1220263 ***


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