original report: https://bugzilla.redhat.com/show_bug.cgi?id=1705695
Note: This appears to be scale out of DVR enabled compute nodes with queens.
<copied text>
Description of problem:
neutron related containers are duplicated when running an overcloud deploy to scale-up ... this appear to be one of the cause:
May 1 17:46:10 openstack-overcloud-compute-0.localdomain os-collect-config: TASK [Debug output for task which failed: Start containers for step 2] *********
May 1 17:46:10 openstack-overcloud-compute-0.localdomain os-collect-config: ok: [localhost] => {
May 1 17:46:10 openstack-overcloud-compute-0.localdomain os-collect-config: "failed_when_result": false,
May 1 17:46:10 openstack-overcloud-compute-0.localdomain os-collect-config: "outputs.stdout_lines|default([])|union(outputs.stderr_lines|default([]))": [
May 1 17:46:10 openstack-overcloud-compute-0.localdomain os-collect-config: "Renaming \"neutron_l3_agent-x7llxanp\" to \"neutron_l3_agent\"",
May 1 17:46:10 openstack-overcloud-compute-0.localdomain os-collect-config: "Error renaming container: neutron_l3_agent-x7llxanp",
May 1 17:46:10 openstack-overcloud-compute-0.localdomain os-collect-config: "Error response from daemon: Error when allocating new name: Conflict. The container name \"/neutron_l3_agent\" is already in use by container c4a9db22dfea307ce06c1577d38ca32ecb8b1e0edd239b06b255eda57965413e. You have to remove (or rename) that container to be able to reuse that name.",
May 1 17:46:10 openstack-overcloud-compute-0.localdomain os-collect-config: "Error: failed to rename container named neutron_l3_agent-x7llxanp",
May 1 17:46:10 openstack-overcloud-compute-0.localdomain os-collect-config: "",
May 1 17:46:10 openstack-overcloud-compute-0.localdomain os-collect-config: "Renaming \"neutron_metadata_agent-b48p0c0k\" to \"neutron_metadata_agent\"",
May 1 17:46:10 openstack-overcloud-compute-0.localdomain os-collect-config: "Error renaming container: neutron_metadata_agent-b48p0c0k",
May 1 17:46:10 openstack-overcloud-compute-0.localdomain os-collect-config: "Error response from daemon: Error when allocating new name: Conflict. The container name \"/neutron_metadata_agent\" is already in use by container 007b1a0fb94e4b59acea71e5cc4f86213eeb08b8b661264d67a0daa6f6d3ac06. You have to remove (or rename) that container to be able to reuse that name.",
May 1 17:46:10 openstack-overcloud-compute-0.localdomain os-collect-config: "Error: failed to rename container named neutron_metadata_agent-b48p0c0k",
May 1 17:46:10 openstack-overcloud-compute-0.localdomain os-collect-config: "Renaming \"neutron_ovs_agent-kjigl1bh\" to \"neutron_ovs_agent\"",
May 1 17:46:10 openstack-overcloud-compute-0.localdomain os-collect-config: "Error renaming container: neutron_ovs_agent-kjigl1bh",
May 1 17:46:10 openstack-overcloud-compute-0.localdomain os-collect-config: "Error response from daemon: Error when allocating new name: Conflict. The container name \"/neutron_ovs_agent\" is already in use by container 2126f7af2874517ad300e112c0c40f53ecb283658b2f6475fa978e3639078d18. You have to remove (or rename) that container to be able to reuse that name.",
May 1 17:46:10 openstack-overcloud-compute-0.localdomain os-collect-config: "Error: failed to rename container named neutron_ovs_agent-kjigl1bh",
May 1 17:46:10 openstack-overcloud-compute-0.localdomain os-collect-config: "Cannot rename \"nova_statedir_owner-jg9m88xv\" since \"nova_statedir_owner\" still exists"
May 1 17:46:10 openstack-overcloud-compute-0.localdomain os-collect-config: ]
May 1 17:46:10 openstack-overcloud-compute-0.localdomain os-collect-config: }
Version-Release number of selected component (if applicable):
</copied text>
