Bug 1776155
| Summary: | OpenStack Config-Drive supportability | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Juan Luis de Sousa-Valadas <jdesousa> |
| Component: | Installer | Assignee: | Mike Fedosin <mfedosin> |
| Installer sub component: | openshift-installer | QA Contact: | Johnny Liu <jialiu> |
| Status: | CLOSED WONTFIX | Docs Contact: | |
| Severity: | urgent | ||
| Priority: | urgent | CC: | fgarciad, mfedosin, pprinett |
| Version: | 4.2.z | ||
| Target Milestone: | --- | ||
| Target Release: | 4.4.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-02-14 17:10:29 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: | |||
|
Description
Juan Luis de Sousa-Valadas
2019-11-25 09:06:22 UTC
Hello! In OCP we use the metadata service in three components: 1. In the installer, to inject ignition configs in the bootstrap machine and initial masters. 2. In cluster-api-provider-openstack, to inject ignition configs in workers and new masters. 3. In the in-tree cloud provider to get metadata for kubelet. We rely heavily on this service, and I'm afraid it will be hard to fix it in 4.2, since a lot of components are affected. We will investigate what changes need to be done in 4.3 to enable config-drive metadata and whether it is possible to backport the patches to 4.2. Meanwhile, until it's fixed, I think we should add the metadata service requirement to our documentation. Added a documentation bug https://bugzilla.redhat.com/show_bug.cgi?id=1777804 Documenation fix: https://github.com/openshift/installer/pull/2729 Installer fix: https://github.com/openshift/installer/pull/2734 Cloud provider fix: Upstream: https://github.com/kubernetes/kubernetes/pull/85755 Backport: https://github.com/openshift/origin/pull/24241 I have to say that it is impossible to use the config drive with OpenStack's cloud provider because it can't provide information about attached volumes. https://github.com/openshift/origin/blob/master/vendor/k8s.io/kubernetes/staging/src/k8s.io/legacy-cloud-providers/openstack/openstack_volumes.go#L518-L519 We documented that Nova's Metadata service is a hard requirement for us: https://github.com/openshift/installer/blob/master/docs/user/openstack/README.md#nova-metadata-service |