Overcloud deployment failing in promotion jobs at glance-manage db_sync

[yatin]

Overcloud deployment is failing while running: glance-manage db_sync command with Error:-
DBError: (pymysql.err.InternalError) (1419, u'You do not have the SUPER privilege and binary logging is enabled (you *might* want to use the less safe log_bin_trust_function_creators variable)') [SQL: u\"\\nCREATE TRIGGER insert_visibility BEFORE INSERT ON images\\nFOR EACH ROW\\nBEGIN\\n -- NOTE(abashmak):\\n -- The following IF/ELSE block implements a priority decision tree.\\n -- Strict order MUST be followed to correctly cover all the edge cases.\\n\\n -- Edge case: neither is_public nor visibility specified\\n -- (or both specified as NULL):\\n IF NEW.is_public <=> NULL AND NEW.visibility <=> NULL THEN\\n SIGNAL SQLSTATE '45000' SET MESSAGE_TEXT = 'Invalid visibility value';\\n -- Edge case: both is_public and visibility specified:\\n ELSEIF NOT(NEW.is_public <=> NULL OR NEW.visibility <=> NULL) THEN\\n SIGNAL SQLSTATE '45000' SET MESSAGE_TEXT = 'Invalid visibility value';\\n -- Inserting with is_public, set visibility accordingly:\\n ELSEIF NOT NEW.is_public <=> NULL THEN\\n IF NEW.is_public = 1 THEN\\n SET NEW.visibility = 'public';\\n ELSE\\n SET NEW.visibility = 'shared';\\n END IF;\\n -- Inserting with visibility, set is_public accordingly:\\n ELSEIF NOT NEW.visibility <=> NULL THEN\\n IF NEW.visibility = 'public' THEN\\n SET NEW.is_public = 1;\\n ELSE\\n SET NEW.is_public = 0;\\n END IF;\\n -- Edge case: either one of: is_public or visibility,\\n -- is explicitly set to NULL:\\n ELSE\\n SIGNAL SQLSTATE '45000' SET MESSAGE_TEXT = 'Invalid visibility value';\\n END IF;\\nEND;\\n\"] (Background on this error at: http://sqlalche.me/e/2j85)"

Logs:- https://logs.rdoproject.org/openstack-periodic/periodic-tripleo-ci-centos-7-multinode-1ctlr-featureset017-master/5cad1e0/subnode-2/var/log/journal.txt.gz#_Feb_15_03_20_31

Looks like this is starting occuring after following glance change:- https://review.openstack.org/#/c/433934/

Recently following bug is fixed in kolla-ansible by setting log_bin_trust_function_creators=1 for this error:- https://bugs.launchpad.net/kolla-ansible/+bug/1748269

[yatin (yatinkarel)]

glance bug for the same issue: https://bugs.launchpad.net/glance/+bug/1749640. They proposed doc patch https://review.openstack.org/#/c/544792/ to handle this issue.

[Christian Schwede (cschwede)]

Related bug: https://bugs.launchpad.net/glance/+bug/1749640
Proposed fix: https://review.openstack.org/#/c/544792/

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/545245

[OpenStack Infra (hudson-openstack)]

Related fix proposed to branch: master
Review: https://review.openstack.org/545623

[Alan Pevec (apevec)]

Let's close this one as a duplicate of bug 1749640

[OpenStack Infra (hudson-openstack)]

Change abandoned by Christian Schwede (<email address hidden>) on branch: master
Review: https://review.openstack.org/545245
Reason: Abandoning this one in favor of https://review.openstack.org/#/c/544792/

[OpenStack Infra (hudson-openstack)]

Related fix proposed to branch: master
Review: https://review.openstack.org/546243

[OpenStack Infra (hudson-openstack)]

Change abandoned by Emilien Macchi (<email address hidden>) on branch: master
Review: https://review.openstack.org/545623

[OpenStack Infra (hudson-openstack)]

Change abandoned by Alex Schultz (<email address hidden>) on branch: master
Review: https://review.openstack.org/546243
Reason: https://review.openstack.org/#/c/433934/