Uploaded image for project: 'Red Hat OpenStack Services on OpenShift'
  1. Red Hat OpenStack Services on OpenShift
  2. OSPRH-13605

BZ#1916070 proxy configuration updates in /etc/environment files are not being picked up in containers correctly

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • rhos-17.1.z
    • rhos-17.1.4
    • documentation
    • None
    • False
    • False
    • None
    • Undefined
    • Low

      Description of problem:

      At the moment being, octavia (but not limited to) containers do not have /etc/environment bound to the same file on the host.
      This means that any change to host /etc/environment (e.g. adding "no_proxy" or editing "https_proxy" ) will not be picked up by the containers even upon restarting the containers.

      As mentioned in RFE[1] for RHOSP16.0 (closed as EOL), restarting the containers is not enough to force the file inside the container to be updated.
      The container(s) need to be recreated. This often means to re-deploy the whole overcloud.

      Version-Release number of selected component (if applicable):

      • podman-1.6.4-16.module+el8.2.0+7659+b700d80e.x86_64
      • openstack-tripleo-heat-templates-11.3.2-1.20200914170177.el8ost.noarch
      • openstack-octavia-api-5.0.3-1.20200904153428.8c32d2e.el8ost.noarch [4]

      How reproducible:
      100%

      Steps to Reproduce:
      1. Edit the /etc/environment of overcloud nodes using ConfigurationHooks[5] (or even edit the file(s) manually)
      2. Restart octavia related containers
      3. Confirm that the overcloud nodes got the new /etc/environment, but the containers did not

      Actual results:
      No changes are applied

      Expected results:
      Changes to /etc/envirnoment are applied on `podman restart <container>`, without needing to re-create the containers

      Additional info:

      • One solution to this issue could be to include the binding to the host /etc/envirnoment as we're doing in mistral-executor [2].
        This would avoid to the operator to re-deploy the whole overcloud in order to update one single file.
      • Podman seems to have been worked on in this regards [3], but that's on RHEL8.3, as per RHOSP16.1 being tied to RHEL8.2 (podman 1.6.x), we need an alternative solution.

      [1] https://bugzilla.redhat.com/show_bug.cgi?id=1827224
      [2] https://github.com/openstack/tripleo-heat-templates/commit/9cb715a5e766909ad8ac4d2d949cc3c141d7923f
      [3] https://bugzilla.redhat.com/show_bug.cgi?id=1682970
      [4] https://catalog.redhat.com/software/containers/rhosp-rhel8/openstack-octavia-api/5de6c03bbed8bd164a0c1a2d?tag=16.1.3-5&digest=9e046a8ec9c6&architecture=amd64
      [5] https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/16.1/html/advanced_overcloud_customization/chap-configuration_hooks

              rhn-support-jelynch Jenny-Anne Lynch
              rhn-support-astupnik Alex Stupnikov
              rhos-dfg-df
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

                Created:
                Updated:
                Resolved: