Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1879923

Summary: [OSP16.1] Overcloud update (migration to ML2OVN) after 13-16.1 FFU failed on keystone init stage
Product: Red Hat OpenStack Reporter: Roman Safronov <rsafrono>
Component: puppet-keystoneAssignee: RHOS Maint <rhos-maint>
Status: CLOSED DUPLICATE QA Contact: Jeremy Agee <jagee>
Severity: high Docs Contact:
Priority: unspecified    
Version: 16.1 (Train)CC: abishop, ekuris, jjoyce, jlibosva, jschluet, lbragsta, slinaber, tvignaud
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-09-25 17:51: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:

Description Roman Safronov 2020-09-17 11:14:21 UTC
Description of problem:

Overcloud update (migration to ML2OVN) after OSP13->16.1 FFU failed on this stage
TASK [Wait for container-puppet tasks (bootstrap tasks) for step 3 to finish] ***
...
        "2020-09-17 06:21:46,570 ERROR: 650501 -- Error executing ['podman', 'container', 'exists', 'container-puppet-keystone_init_tasks']: returned 1",



Version-Release number of selected component (if applicable):
RHOS-16.1-RHEL-8-20200903.n.0
puppet-keystone-15.4.1-0.20200608233418.60532ba.el8ost.noarch

How reproducible:
Tried once and the issue happened

Steps to Reproduce:
1. Install OSP13 HA environment (3 controllers + 2 computes) with ML2OVS
2. Perform FFU fromOSP13 to OSP16.1 
Note: I used downstream CI job for steps 1-2. 
3. Run migration to ML2OVN according to the official documentation https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/16.1/html/networking_with_open_virtual_network/migrating-ml2ovs-to-ovn#ml2-ovs-to-ovn-migration-prepare

Actual results:
Migration to OVN failed on the keystone init stage

Expected results:
Overcloud update passed successfully the keystone init stage.

Additional info:

Comment 1 Roman Safronov 2020-09-17 11:16:15 UTC
I used the following overcloud deploy command

openstack overcloud deploy \
    --stack qe-Cloud-0 \
    --templates /usr/share/openstack-tripleo-heat-templates \
    -e /usr/share/openstack-tripleo-heat-templates/environments/cinder-backup.yaml \
    -e /home/stack/virt/config_lvm.yaml \
    -e /usr/share/openstack-tripleo-heat-templates/environments/network-isolation.yaml \
    -e /home/stack/virt/network/network-environment.yaml \
    -e /home/stack/virt/enable-tls.yaml \
    -e /home/stack/virt/inject-trust-anchor.yaml \
    -e /home/stack/virt/public_vip.yaml \
    -e /usr/share/openstack-tripleo-heat-templates/environments/ssl/tls-endpoints-public-ip.yaml \
    -e /home/stack/virt/hostnames.yml \
    -e /home/stack/virt/debug.yaml \
    -e /home/stack/virt/config_heat.yaml \
    -e /home/stack/virt/nodes_data.yaml \
    -e /home/stack/virt/performance.yaml \
    -e /home/stack/cli_opts_params.yaml \
    -e /home/stack/overcloud-params.yaml \
    -e /home/stack/containers-prepare-parameter.yaml \
    -e /usr/share/openstack-tripleo-heat-templates/environments/services/neutron-ovn-dvr-ha.yaml \
    -e /home/stack/ovn-extras.yaml \
     2>&1

Comment 4 Alan Bishop 2020-09-25 17:51:39 UTC
Marking this a duplicate of 1856906 because both BZ titles mention migration to OVN.

But it turns out both are duplicates of bug #1878492, which is a cinder issue. I will be posting more information shortly.

*** This bug has been marked as a duplicate of bug 1856906 ***