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

Neutron agent containers are not cleaned after adoption

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • rhos-18.0.4
    • None
    • edpm-ansible
    • None
    • 3
    • False
    • Hide

      None

      Show
      None
    • False
    • ?
    • ?
    • OSPRH-10468 - NFV Adoption [FR1]
    • openstack-ansible-ee-container-1.0.4-1
    • ?
    • ?
    • None
    • Moderate

      It seems that after adoption, both old and new dhcp agent containers are running:

       2abedccea863  quay.io/tripleowallabycentos9/openstack-neutron-dhcp-agent:current-tripleo
                                                               kolla_start           45 hours a
go    Up 45 hours (unhealthy)              neutron_dhcp
f42f6fbde901  quay.io/podified-antelope-centos9/openstack-neutron-dhcp-agent:current-podified
                                                               kolla_start           30 minutes
 ago  Up 30 minutes                        neutron_dhcp_agent

      we should make sure during the adption process that old one is not running anymore afer adoption.

      The issue was originally reported by ihrachys on slack: https://redhat-internal.slack.com/archives/C046JULBVJ7/p1714599356871259

       

      Other agents may also be affected (sriov, metadata).

       

      We should also confirm that no `tripleo_*` systemd units are left in the system, even if containers are e.g. not running.

              jlibosva Jakub Libosvar
              skaplons@redhat.com Slawomir Kaplonski
              Fiorella Yanac Fiorella Yanac
              rhos-dfg-networking-squad-neutron
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated: