Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

This project is now read‑only. Starting Monday, February 2, please use https://ibm-ceph.atlassian.net/ for all bug tracking management.

Bug 1486957

Summary:	resync downstream with upstream - 2
Product:	[Red Hat Storage] Red Hat Ceph Storage	Reporter:	seb
Component:	Container	Assignee:	Sébastien Han <shan>
Status:	CLOSED ERRATA	QA Contact:	Harish NV Rao <hnallurv>
Severity:	medium	Docs Contact:
Priority:	low
Version:	3.0	CC:	anharris, dang, hchen, jim.curtis, kdreyer, pprakash, seb
Target Milestone:	rc
Target Release:	3.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	rhceph:ceph-3.0-rhel-7-docker-candidate-15872-20170919152848	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-12-05 23:18:20 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:
Embargoed:

Description seb 2017-08-30 21:38:39 UTC

Description of problem:

Resync the downstream image with the latest upstream code.


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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 2 Harish NV Rao 2017-08-31 07:31:57 UTC

@Seb, is BZ 1476835 dup of this bz? if not what is the difference between two?

Comment 3 seb 2017-08-31 17:40:55 UTC

@Harish, it's not a dump, it's just a new resync.
There has been to many commits since the last resync and I cannot open on BZ for each. So it's easier (not ideal I know) this way.

Comment 5 Ken Dreyer (Red Hat) 2017-08-31 17:52:52 UTC

Sébastien, would you please explain to the QE team what exactly is changing in this BZ?

"Steps to Reproduce:", "Actual results:", "Expected results:" are blank above. The QE team has no context to provide the qa_ack here or test this BZ to verify that this BZ is resolved. Why should they accept these changes?

Comment 6 seb 2017-09-01 12:05:32 UTC

@Ken, sorry about that, actual there is nothing in particular to test. We just need to make sure all the scenario work. This is a resync, so it's not a bug but more an update of the image.
Thanks.

Comment 7 Harish NV Rao 2017-09-05 11:29:03 UTC

No specific tests other than basic test scenarios planned for 3.0 will be executed.

Comment 9 Harish NV Rao 2017-11-13 08:02:10 UTC

Planned tests have passed.

Comment 12 errata-xmlrpc 2017-12-05 23:18:20 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://access.redhat.com/errata/RHEA-2017:3388