Description of problem:
An updated version of the rhos docker image will be made available for RHCS 2.0.
This will be a separate release stream: the current image is:
the new one will be at
I (Federico) will be responsible for the RHN request paperwork if any is needed. Huamin Chen built the last image with Jim Curtis. Everyone is in CC.
THIS IS A TECH PREVIEW as of current planning.
Documentation exists in the form of a KB article, will need to be updated with references to the multiple available versions (1.3, upstream Hammer, 2, upstream Jewel).
The image is on docker registry as hchen/rhceph2. We have to use public docker registry for dev testing.
The git is at https://github.com/roofmonkey/rhcs/tree/v2.0
The latest drop as of now (Ceph-2-RHEL-7-20160623.6) has 2 of the three nfs-ganesha packages in it. I've contacted the devs to get the 3rd one (nfs-ganesha-ceph) added as well.
RHCS2.0 container installation through ansible fails due to bug: https://bugzilla.redhat.com/show_bug.cgi?id=1356105. This is still in POST and unless on_qa cannot proceed further. This is a blocker WRT ansible installation of RHCS 2.0
Adding doc draft version for reference: https://docs.google.com/document/d/1Ef5a_-Yjozy5Ue3C0M7mMQNn6zWZe0-514bhxKwFHI8/edit?ts=576a3d95#heading=h.f29ffgu8vo7g
 is a blocker for this bug, as we won't be able to ship a ceph ansible version with the fix for . so, moving the bug to assigned.
Discussed at program meeting on 22-Feb. This bug should be in ON_QA (In reply to krishnaram Karthick from comment #27)
>  is a blocker for this bug, as we won't be able to ship a ceph ansible
> version with the fix for . so, moving the bug to assigned.
>  https://bugzilla.redhat.com/show_bug.cgi?id=1420207
Discussed at program meeting on 22-Feb. This bug should be in ON_QA. The bug referenced above is targeted for a future release
Moving the bug to verified as the image is available now.
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.