| Summary: | InternalIP node configuration fails when using OpenStack as cloud provider with OpenShift: hardcoded OpenStack network names | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Alexander Koksharov <akokshar> |
| Component: | Storage | Assignee: | Bradley Childs <bchilds> |
| Status: | CLOSED ERRATA | QA Contact: | Jianwei Hou <jhou> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 3.1.0 | CC: | agoldste, akokshar, aos-bugs, decarr, ghuang, jhou, jokerman, misalunk, mmccomas, mwysocki, pep, tdawson |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-05-12 16:27:34 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: | |
| Bug Depends On: | |||
| Bug Blocks: | 1267746 | ||
|
Description
Alexander Koksharov
2016-01-29 13:58:40 UTC
Upstream PR: https://github.com/kubernetes/kubernetes/pull/18829 merged on 1/29 Will be in next puddle We usually use openshift-ansible to setup the env on openstack. But now we don't how to trigger this related pr to verify this bug. Any suggestion step to verify this bug on openshift? I'm not sure - hopefully Alexander can provide the necessary info. if nobody response on this bug, I'll set it verified. I do not have access to our openstack setup and configurations, all I can do is to verify cinder configuration is correct and functional. The fix has not caused regression, so I'll move this bug to verified. *** Bug 1320959 has been marked as a duplicate of this bug. *** *** Bug 1331829 has been marked as a duplicate of this bug. *** 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/RHSA-2016:1064 |