This is a bug to keep track of the effort to get a ceph2.5 container to release with OSP12.
This should be a collection of Blockers for why rhceph-rhel7-docker-2.4-4 build is not good enough for integration with OSP 12. CI Jobs, Manual Runs, Other bugs, Missing Features (for RFE's), Crash and Burn scenarios that are not recoverable.
This image contains numerous fixes such as: * dmcrypt activation fix after server reboot * container reboot for dmcrypt and osd with dedicated journal * apply correct ownership to devices prior activation (prevents errors such as "Permission Denied").
Deployment on osp12 with Ceph 2.4-4 container image failed. Deployment succeeded but on further investigation no OSD container images were instantiated. Error was: 2017-11-01 17:00:26 /entrypoint.sh: static: does not generate config chown: cannot access '/dev/sdk2': No such file or directory Across all osd devicesa. This was deployed with non-collocated journal. Deploying with docker-registry.engineering.redhat.com/ceph/rhceph-2-rhel7:candidate-50944-20171027124759 container image mitigated the issue and I was able to get a successful deployment
(In reply to Dave Wilson from comment #10) > Deployment on osp12 with Ceph 2.4-4 container image failed. Deployment > succeeded but on further investigation no OSD container images were > instantiated. > Error was: > 2017-11-01 17:00:26 /entrypoint.sh: static: does not generate config > chown: cannot access '/dev/sdk2': No such file or directory > > Across all osd devicesa. This was deployed with non-collocated journal. > Deploying with > docker-registry.engineering.redhat.com/ceph/rhceph-2-rhel7:candidate-50944- > 20171027124759 container image mitigated the issue and I was able to get a > successful deployment Thank you Dave, I created a bug to target the 2.4-4 container and this workaround specifically: https://bugzilla.redhat.com/show_bug.cgi?id=1508663 John
DFG:Ceph is tracking their GA blockers with the following tracker: https://bugzilla.redhat.com/show_bug.cgi?id=1484447 This bug is a sub-tracker focussed on issues in the 2.4-4 container image (and the above depends on it). Do we need a sub-tracker? DFG:Ceph would rather not have another tracker as per our bug-scrub call this morning as we think it causes confusion. *** This bug has been marked as a duplicate of bug 1484447 ***
Removing doc_text flag as this was already reported in the errata for BZ#1496509
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-2018:0621