Bug 1637413 - 3.11: APP pod unable to start after target port failure in cases where single paths are mounted on APP pods(BZ#1599742)
Summary: 3.11: APP pod unable to start after target port failure in cases where single...
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Storage
Version: 3.11.0
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 3.11.z
Assignee: Jan Safranek
QA Contact: Liang Xia
Depends On: 1609703 1637422
Blocks: 1596021 1598740 1609788
TreeView+ depends on / blocked
Reported: 2018-10-09 08:42 UTC by Jan Safranek
Modified: 2020-05-20 19:50 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1609703
Last Closed: 2018-11-20 03:10:46 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:3537 0 None None None 2018-11-20 03:11:30 UTC

Comment 1 Jan Safranek 2018-10-09 09:05:07 UTC
3.11.1 PR: https://github.com/openshift/ose/pull/1432

Comment 3 Liang Xia 2018-11-06 02:37:35 UTC
Verified multi-path is mounted on the node where the pod is running.

oc v3.11.39
kubernetes v1.11.0+d4cacc0
features: Basic-Auth GSSAPI Kerberos SPNEGO

Also did some regression testing, and no issue found.

Comment 5 errata-xmlrpc 2018-11-20 03:10:46 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.


Note You need to log in before you can comment on or make changes to this bug.