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

Disable and uninstall 17 data plane services after adoption

XMLWordPrintable

    • Disable and uninstall 17 data plane services after adoption
    • 10
    • False
    • Hide

      None

      Show
      None
    • False
    • OSPRH-3714Red Hat OpenStack 18.0 Data Plane Adoption [FR1]
    • Not Selected
    • Proposed
    • Committed
    • To Do
    • OSPRH-3714 - Red Hat OpenStack 18.0 Data Plane Adoption [FR1]
    • openstack-ansible-ee-container-1.0.0-42
    • Proposed
    • Proposed
    • 0% To Do, 0% In Progress, 100% Done
    • Regression Only

      After adoption, the 17 services and containers on data plane nodes are still present, they are just stopped.

      They need to be disabled and uninstalled so that they are not mistakenly re-activated.

      See this log from an adoption job showing some of the leftover services:

      https://sf.hosted.upshift.rdu2.redhat.com/logs/openstack-periodic-integration-rhos-18-rhel9/code.engineering.redhat.com/tripleo-ci/master/periodic-rhel-9-rhos-17.1-extracted-crc-data-plane-adoption/8418423/controller/ci-framework-data/logs/openstack-k8s-operators-openstack-must-gather/sos-reports/_all_nodes/sosreport-standalone.localdomain/sos_commands/systemd/systemctl_list-unit-files

      That job uses a standalone 17 environment, so it shows both control plane and data plane services.

      We can add a role in edpm-ansible to clean up these leftover services, and add a step in the adoption guide to create an additional OpenStackDataPlaneDeployment to execute the role.

              jpodivin@redhat.com Jiri Podivin
              jslagle@redhat.com James Slagle
              rhos-dfg-df
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: