Bug 2228513
Summary: | [16.2] Ephemeral heat communication is not using svc fqdn and hitting proxy | |||
---|---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | Martin Schuppert <mschuppe> | |
Component: | osp-director-operator-container | Assignee: | Martin Schuppert <mschuppe> | |
Status: | CLOSED ERRATA | QA Contact: | ||
Severity: | medium | Docs Contact: | ||
Priority: | medium | |||
Version: | 16.2 (Train) | CC: | jschluet, pkomarov, tkajinam | |
Target Milestone: | --- | Keywords: | Triaged | |
Target Release: | --- | |||
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | ||||
Fixed In Version: | osp-director-operator-container-1.3.0-8 | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | ||
Clone Of: | ||||
: | 2229131 (view as bug list) | Environment: | ||
Last Closed: | 2023-08-22 00:09:39 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: | 2229131 |
Description
Martin Schuppert
2023-08-02 14:09:40 UTC
I'm not super familiar with OSPdO but I'm wondering if we would also want to consider disabling proxy for some containers. My understanding is that we needed proxy in mistral-executor container so that the container can access the container images in the external network, but the other containers such as heat container does not really require direct access to external URL and require only internal communication with the other services. # We can probably look into the same in normal Director deployment but I'm not too sure if we want to change the overall # mechanism at this stage. (In reply to Takashi Kajinami from comment #1) > I'm not super familiar with OSPdO but I'm wondering if we would also want to > consider disabling proxy for some containers. > My understanding is that we needed proxy in mistral-executor container so > that the container can access the container images > in the external network, but the other containers such as heat container > does not really require direct access to external URL > and require only internal communication with the other services. > > # We can probably look into the same in normal Director deployment but I'm > not too sure if we want to change the overall > # mechanism at this stage. In OSPdO we don't use mistral. An ephemeral heat env is used to created the ansible playbooks and then run in a deploy pod using the tripleoclient container image. So we only have mariadb, rabbit and heat (api/engine) during this time or creating the playbooks 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 (Moderate: Release of containers for OSP 16.2.z (Train) director Operator), 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-2023:4694 |