Login
[x]
Log in using an account from:
Fedora Account System
Red Hat Associate
Red Hat Customer
Or login using a Red Hat Bugzilla account
Forgot Password
Login:
Hide Forgot
Create an Account
Red Hat Bugzilla – Bug 1310630
[?]
New
Simple Search
Advanced Search
My Links
Browse
Requests
Reports
Current State
Search
Tabular reports
Graphical reports
Duplicates
Other Reports
User Changes
Plotly Reports
Bug Status
Bug Severity
Non-Defaults
|
Product Dashboard
Help
Page Help!
Bug Writing Guidelines
What's new
Browser Support Policy
5.0.4.rh81 Release notes
FAQ
Guides index
User guide
Web Services
Contact
Legal
This site requires JavaScript to be enabled to function correctly, please enable it.
Bug 1310630
-
Newly created volume start, starting the bricks when server quorum not met
Summary:
Newly created volume start, starting the bricks when server quorum not met
Keywords
:
Reopened
Triaged
Status
:
CLOSED DUPLICATE of
bug 1310632
Alias:
None
Product:
GlusterFS
Classification:
Community
Component:
glusterd
Sub Component:
---
Version:
3.7.0
Hardware:
x86_64
OS:
Linux
Priority:
high
Severity:
high
Target Milestone:
---
Assignee:
Gaurav Kumar Garg
QA Contact:
Docs Contact:
URL:
Whiteboard:
Depends On:
1308402
Blocks:
TreeView+
depends on
/
blocked
Reported:
2016-02-22 12:02 UTC by
Gaurav Kumar Garg
Modified:
2016-06-05 23:38 UTC (
History
)
CC List:
8 users
(
show
)
amukherj
bsrirama
bugs
ggarg
hgowtham
rcyriac
smohan
storage-qa-internal
Fixed In Version:
Doc Type:
Bug Fix
Doc Text:
Clone Of:
1308402
Environment:
Last Closed:
2016-02-23 12:20:08 UTC
Regression:
---
Mount Type:
---
Documentation:
---
CRM:
Verified Versions:
Dependent Products:
Red Hat Enterprise Virtualization Manager
Red Hat Gluster Storage
Attachments
(Terms of Use)
Add an attachment
(proposed patch, testcase, etc.)
Comment 1
Gaurav Kumar Garg
2016-02-23 12:15:28 UTC
*** This bug has been marked as a duplicate of
bug 1310632
***
Comment 2
hari gowtham
2016-02-23 12:20:08 UTC
*** This bug has been marked as a duplicate of
bug 1310632
***
Note
You need to
log in
before you can comment on or make changes to this bug.