Bug 1662312
Summary: | openshift-ansible-3.11.51 prevents gluster-block from creating devices | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Niels de Vos <ndevos> |
Component: | Installer | Assignee: | Scott Dodson <sdodson> |
Installer sub component: | openshift-ansible | QA Contact: | Rachael <rgeorge> |
Status: | CLOSED ERRATA | Docs Contact: | |
Severity: | urgent | ||
Priority: | urgent | CC: | alsilva, aprajapa, bkunal, ealcaniz, gpei, knarra, kramdoss, lasilva, mrobson, mtaru, nberry, ndevos, olim, pdwyer, rcyriac, rgeorge, sdodson, travi |
Version: | 3.11.0 | ||
Target Milestone: | --- | ||
Target Release: | 3.11.z | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: |
An error in glusterfs pod mountpoints prevented use of gluster-block. Those mount points have been updated to resolve the problem.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2019-04-11 05:38:23 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: | |||
Bug Depends On: | |||
Bug Blocks: | 1653571, 1660280 |
Description
Niels de Vos
2018-12-27 15:49:07 UTC
https://github.com/openshift/openshift-ansible/pull/10934 is the PR for openshift-ansible/release-3.11. Niels, How comprehensive of a test matrix do we have around this stuff? Can we work through all the supported configurations to make sure that we've got all of them covered? (In reply to Scott Dodson from comment #2) > Niels, > > How comprehensive of a test matrix do we have around this stuff? Can we work > through all the supported configurations to make sure that we've got all of > them covered? Karthick, can you share the details with Scott? In openshift-ansible-3.11.67-1 Rachael, Can you please look at the bug and do the needful ? Thanks kasturi 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-2019:0636 |