Bug 1471241 - ship ceph-ansible and Ansible in RHCEPH 3
Summary: ship ceph-ansible and Ansible in RHCEPH 3
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Ceph Storage
Classification: Red Hat Storage
Component: Build
Version: 3.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: rc
: 3.0
Assignee: Ken Dreyer (Red Hat)
QA Contact: Vasishta
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-07-14 19:19 UTC by Ken Dreyer (Red Hat)
Modified: 2022-02-21 18:21 UTC (History)
4 users (show)

Fixed In Version: RHEL: ceph-ansible-3.0.0-0.1.rc3.el7cp Ubuntu: ceph-ansible_3.0.0~rc3-2redhat1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-12-05 23:36:49 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:3387 0 normal SHIPPED_LIVE Red Hat Ceph Storage 3.0 bug fix and enhancement update 2017-12-06 03:03:45 UTC

Description Ken Dreyer (Red Hat) 2017-07-14 19:19:53 UTC 
Description of problem:
ceph-ansible and ceph-installer currently ship in the RH Storage Console 2 product. It makes more sense to tie these packages to Ceph's lifecycle than to Storage Console's.

Steps to Reproduce:
1. Enable RH Ceph Storage 3 repositor(ies) according to documentation
2. Ensure RH Storage Console repositories are disabled
3. Install ceph-ansible according to documentation

Expected results:
ceph-ansible installation succeeds
Comment 8 Vasishta 2017-09-12 13:24:34 UTC 
1) Enabled Tools repo
$  yum repolist |grep Tools
download-node-02.eng.bos.redhat.com_composes_auto_ceph-3.0-rhel-7_latest-RHCEPH-3-RHEL-7_compose_Tools_x86_64_os_

2) Made sure RHSCONwas not enabled

$ yum repolist |grep rhscon 
$

3) Installed ceph-ansible
$ rpm -qa |grep ceph-ansible
ceph-ansible-3.0.0-0.1.rc6.el7cp.noarch

Moving to VERIFIED state.


Regards,
Vasishta
Comment 11 errata-xmlrpc 2017-12-05 23:36:49 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/RHBA-2017:3387
Note You need to log in before you can comment on or make changes to this bug.