Bug 1326356

Summary:	[GSS][RFE] Add logging of snapshot scheduler messages
Product:	Red Hat Gluster Storage	Reporter:	Riyas Abdulrasak <rnalakka>
Component:	snapshot	Assignee:	Bug Updates Notification Mailing List <rhs-bugs>
Status:	CLOSED WONTFIX	QA Contact:	storage-qa-internal <storage-qa-internal>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	rhgs-3.1	CC:	atumball, bkunal, rhs-bugs, rkavunga
Target Milestone:	---	Keywords:	FutureFeature, ZStream
Target Release:	---
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-05-08 05:13:12 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Bug Depends On:
Bug Blocks:	1408949, 1468983

Description Riyas Abdulrasak 2016-04-12 14:00:28 UTC

Description of problem:

At present , if the snapshot creation failed by a snapshot scheduler is not logged in snapshot_scheduler.log or any other logs, Making it difficult for the users to debug snapshot scheduler related issues.  Only the snapshot schedule creation related errors are logged, it is not logging the success/failure of the snapshot creation per schedules. In case snapshot scheduler fails to create a snapshot, it should log the reason behind the failure of snapshot creation for debugging the issue. 


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

Red Hat Gluster Storage 3.1.1

How reproducible:

Always

Steps to Reproduce:

1.  Create a snapshot schedule. 

2.  Simulate some failure conditions of snapshot schedule , like  Making the shared storage unavailable on the nodes , or communication issue between the nodes ...etc

3. Snapshot creation by schedule will fail , but no logs are generated related failure. 

Actual results:

Not logging snapshot creation failure per schedule. 


Expected results:

If the snapshot scheduler fails to create snapshots as per a schedule , it must be logged. 

Additional info:

Comment 3 Avra Sengupta 2016-11-17 06:19:17 UTC

There is no central log for snapshot scheduler. If the scheduler has been initialised on more than one node, any node can pick up the job. In case we log the outcome of the job success/failure, it will be logged in the node that picked up that job at that instance. Next time some other node can pick up the same job and that node's log might contain the outcome.

The point being for the same job, everytime it's executed the outcome might be present in different logs, which doesn't make anyone's life easier. Moreover with eventing coming in, for every snapshot action, and it's consecutive result an event will be generated.

With the above is this RFE still needed?

Comment 6 Mohammed Rafi KC 2017-08-18 06:52:37 UTC

There was a discussion for a centralized logging, if that happens we can take this RFE

Comment 7 Amar Tumballi 2017-08-28 11:35:09 UTC

Makes sense to make it a blocker on centralized logging for now. Considering the centralize logging feature would come in soon (say 6 more months) compared to the time bug already waited, its better to combine this effort with it.

Comment 10 Mohammed Rafi KC 2018-11-19 08:26:38 UTC

Bipin,

We are not enhancing snapshot scheduler for 3.x series. This RFE will be considered when we fix https://github.com/gluster/glusterd2/issues/1098.

With that note Can I close the bug with WONT_FIX