Bug 1586132

Summary: OSP13 minor update: docker/services/pacemaker/ovn-dbs.yaml is missing update_tasks
Product: Red Hat OpenStack Reporter: Marius Cornea <mcornea>
Component: openstack-tripleo-heat-templatesAssignee: Numan Siddique <nusiddiq>
Status: CLOSED ERRATA QA Contact: Raviv Bar-Tal <rbartal>
Severity: urgent Docs Contact:
Priority: urgent    
Version: 13.0 (Queens)CC: amuller, bcafarel, dbecker, ekuris, jschluet, lmarsh, mburns, mcornea, morazi, nusiddiq, tfreger
Target Milestone: z1Keywords: Triaged, ZStream
Target Release: 13.0 (Queens)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: openstack-tripleo-heat-templates-8.0.2-39 Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-07-19 14:27:12 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 Marius Cornea 2018-06-05 14:52:26 UTC
Description of problem:

http://git.openstack.org/cgit/openstack/tripleo-heat-templates/tree/docker/services/pacemaker/ovn-dbs.yaml is missing update_tasks so the minor update process doesn't load the new image for ovn-dbs-bundle-docker containers after minor update process has completed.

Comment 2 Numan Siddique 2018-06-07 07:29:12 UTC
Can you please share the commands to run a minor stack update ?

Comment 3 Numan Siddique 2018-06-07 18:51:24 UTC
On a OSP13 OVN deployment,

1. I first ran the below command to prepare the update 

$openstack overcloud update prepare \
--timeout 100 \
--templates /usr/share/openstack-tripleo-heat-templates \
--stack overcloud \
--libvirt-type kvm \
--ntp-server clock.redhat.com \
-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/hostnames.yml \
-e /usr/share/openstack-tripleo-heat-templates/environments/services-docker/neutron-ovn-ha.yaml \
-e /home/stack/virt/nodes_data.yaml \
-e /home/stack/virt/extra_templates.yaml \
-e /home/stack/virt/docker-images.yaml \
--container-registry-file /home/stack/virt/docker-images.yaml \
--log-file overcloud_deployment_update_prep.log


2. Then I ran the below command to run the update

$openstack overcloud update run  --nodes Controller --playbook all

And I am getting the below error always. I tested without my fix in 
 docker/services/pacemaker/ovn_dbs.yaml and with my fix.

http://pastebin.test.redhat.com/600905


Am I doing anything wrong here ?

Can you please provide the steps you run to update the stack.

Thanks

Comment 4 Marius Cornea 2018-06-07 18:57:45 UTC
The error looks to me like missing ansible-pacemaker module which is done by the undercloud update(pre-requisite for the overcloud update).

The minor update steps are documented here:
https://docs.google.com/document/d/1ArKKxlJE_ggHo-mU_IIrtr-dqy05-2peKBPbFtNrwZQ/edit

Comment 5 Numan Siddique 2018-06-07 19:26:16 UTC
Thanks for sharing the document.

Comment 22 Raviv Bar-Tal 2018-07-08 11:28:20 UTC
Hi Marius,
I do not see this container "ovn-dbs-bundle-docker" on the overcloud or in the undercloud registry,
Do I need some special deployment command or adding yaml files to the deploy command in order to use this docker.

Comment 24 Eran Kuris 2018-07-10 05:19:41 UTC
Fix verified :
Minor update from puddle-2018-07-03.3
to puddle 2018-07-06.1/

openstack-tripleo-heat-templates-8.0.2-43.el7ost.noarch

The file exists:
/undercloud-0/usr/share/openstack-tripleo-heat-templates/docker/services/pacemaker/ovn_dbs.yaml


https://rhos-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/DFG/view/network/view/networking-ovn/job/DFG-network-networking-ovn-update-13_director-rhel-virthost-3cont_2comp_2net-ipv4-geneve-composable/22/testReport/

Comment 26 errata-xmlrpc 2018-07-19 14:27:12 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2018:2214