Bug 1463059 – Ceph incremental backup fails in Mitaka

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1463059 - Ceph incremental backup fails in Mitaka

Summary:	Ceph incremental backup fails in Mitaka

Status:	NEW

Aliases:	None

Product:	Red Hat OpenStack
Classification:	Red Hat
Component:	openstack-cinder (Show other bugs)
Sub Component:
Version:	10.0 (Newton)
Hardware:	Unspecified Unspecified

Priority	medium Severity medium
Target Milestone:	---
Target Release:	10.0 (Newton)
Assigned To:	Eric Harney
QA Contact:	Yogev Rabl
Docs Contact:	Don Domingo

URL:
Whiteboard:
Keywords:	Triaged, ZStream

Depends On:	1375207
Blocks:
	Show dependency tree / graph

Reported:	2017-06-19 23:08 EDT by Don Domingo
Modified:	2018-10-13 21:52 EDT (History)
CC List:	5 users (show)

See Also:
Fixed In Version:
Doc Type:	If docs needed, set a value
Doc Text:	When using Red Hat Ceph Storage as a back end for both Block Storage (cinder) volumes and backups, any attempt to perform an incremental backup will result in a full backup instead, without any warning.
Story Points:	---
Clone Of:	1375207
Environment:
Last Closed:
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Comment 1 Red Hat Bugzilla Rules Engine 2017-06-19 23:08:32 EDT

This bugzilla has been removed from the release and needs to be reviewed and Triaged for another Target Release.

Comment 3 Red Hat Bugzilla Rules Engine 2017-06-19 23:11:05 EDT

This bugzilla has been removed from the release and needs to be reviewed and Triaged for another Target Release.

Comment 4 Red Hat Bugzilla Rules Engine 2017-06-20 00:27:58 EDT

This bugzilla has been removed from the release and needs to be reviewed and Triaged for another Target Release.

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