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 1201959

Summary:	[Ceph-1.2] Requesting updating Ceph-1.2's python-requests pkg upgrade to version from 1.1.0-3.1.1.el6 to 2.6.0-3.el6
Product:	[Red Hat Storage] Red Hat Ceph Storage	Reporter:	Linda Wang <lwang>
Component:	RADOS	Assignee:	Boris Ranto <branto>
Status:	CLOSED WONTFIX	QA Contact:	ceph-qe-bugs <ceph-qe-bugs>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	1.2.3	CC:	bkabrda, branto, ceph-eng-bugs, dzafman, kchai, kdreyer, lwang, nlevine, sgraf, tmuthami
Target Milestone:	rc
Target Release:	1.2.4
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	python-requests-2.6.0-3.el6	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-12-08 16:36:51 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 Linda Wang 2015-03-14 01:38:01 UTC

Description of problem:

Currently Ceph-1.2 ships with python-requests-1.1.0-3.el6 version,
however, in RHEL6.7, we plan to ship with python-requests-1.1.0-8.el6,
same with Openstack5,0 and OpenStackForeman.  It will be very helpful
if Ceph-1.2.3 upgrade its python-requests to 1.1.0-8.el6; so that
it can match with RHEL6.7, which will ship later than the Ceph-1.2.3,
as well as OpenStack and OpenStackForeman.

This way, it will reduce support and testing matrix, and allow cross 
product compatibility. 


Version-Release number of selected component (if applicable):
1.1.0-3.el6



Expected results:
1.1.0-8.el6

Comment 2 Ken Dreyer (Red Hat) 2015-03-24 15:33:58 UTC

Discussed with Boris today over IRC. We're both ok with simply tagging RHEL 6.7's python-requests-1.1.0-10.el6 build into ceph-1.2-rhel-6-candidate and shipping that in RHCeph.

Comment 3 Boris Ranto 2015-03-24 16:12:50 UTC

Setting the flags, I suppose we use rhc‑1.2.z for async updates, now.

Comment 4 Linda Wang 2015-03-25 17:51:28 UTC

Hi Ken,

I will defer your question to Slavek, whom is
responsible for these packages.. or perhaps someone
he hand this off to. Put needinf on 
bkabrda.

Comment 6 Boris Ranto 2015-03-25 18:13:05 UTC

I've already tagged the latest rhel-6 build to the rhel-6 red velvet ceph branch. Now, we should decide whether we want to fix this in an async update (the impact of the change is fairly minor, here so that is good but the severity is probably not high enough) or it can wait for a point release.

Comment 7 Ken Dreyer (Red Hat) 2015-04-06 15:27:21 UTC

(In reply to Boris Ranto from comment #6)
> I've already tagged the latest rhel-6 build to the rhel-6 red velvet ceph
> branch. Now, we should decide whether we want to fix this in an async update
> (the impact of the change is fairly minor, here so that is good but the
> severity is probably not high enough) or it can wait for a point release.

From what I last heard from Neil, it can wait for a 1.2.4 point release

Comment 8 Neil Levine 2015-10-14 23:38:55 UTC

Let's still target for 1.2.4

Comment 9 Ken Dreyer (Red Hat) 2015-10-15 14:16:45 UTC

python-requests-2.6.0-3.el6 shipped in RHEL 6 in https://access.redhat.com/errata/RHEA-2015:1418

Comment 11 Ken Dreyer (Red Hat) 2015-12-08 16:36:51 UTC

Closing all RHCS 1.2 bugs, since we are not planning to do a formal RHCS 1.2.4 release.

RHEL 6.7 shipped, and customers should be using the latest python-requests package.