secure_auth forced client side in 2.3.2

Bug #1508450 reported by James Dooley on 2015-10-21
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Percona XtraBackup moved to https://jira.percona.com/projects/PXB
Triaged
Wishlist
Unassigned
2.3
Fix Released
Wishlist
Sergei Glushchenko
2.4
Won't Fix
Undecided
Unassigned
openstack-ansible
High
Kevin Carter

Bug Description

xtrabackup 2.3.2 appears to be forcing secure auth client side.

Although passwords should be updated, mysql 5.5 and older do not enforce secure_auth server side.

Ideally there should be a --skip-secure-auth flag to allow backing up servers with legacy passwords still set.

Reviewed: https://review.openstack.org/238748
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible/commit/?id=113597a7cf16c9ae791cc412b2e1a07188b28fd5
Submitter: Jenkins
Branch: master

commit 113597a7cf16c9ae791cc412b2e1a07188b28fd5
Author: Kevin Carter <email address hidden>
Date: Thu Oct 22 21:12:34 2015 -0500

    Pinned percona-xtrabackup to ensure stability

    This change makes it so that the xtrabackup plugin is pinned
    to a specific version via downloading the deb.

    This reinstates the galera affinity values for testing so that
    we're not skipping potentially broken code paths.

    Related-Bug: #1508411
    Related-Bug: #1508448
    Related-Bug: #1508450
    Change-Id: I288d6d9871eb9dfe0ecc547e50639078afdff79d
    Signed-off-by: Kevin Carter <email address hidden>

Changed in openstack-ansible:
status: New → Fix Released
importance: Undecided → High
assignee: nobody → Kevin Carter (kevin-carter)

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXB-1019

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers