Bug 1329095 - mariadb and keystone down after an upgrade from liberty to mitaka
Summary: mariadb and keystone down after an upgrade from liberty to mitaka
Keywords:
Status: CLOSED EOL
Alias: None
Product: RDO
Classification: Community
Component: openstack-tripleo
Version: Liberty
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: GA
: trunk
Assignee: James Slagle
QA Contact: Shai Revivo
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-21 08:12 UTC by mathieu bultel
Modified: 2017-06-18 06:03 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-06-18 06:03:38 UTC

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description mathieu bultel 2016-04-21 08:12:08 UTC 
When upgrading for stable liberty to mitaka (current-passed-ci)
after a yum update on the Undercloud, mariadb and keystone are down.

Mariadb can't be restart, need to kill the mysql pid before, then the service is able to start.

It looks like during the upgrade of the package mariadb can't stop the process and restart properly.

Then keystone can't start because it trying to find the config_file:
/usr/share/keystone/keystone-dist-paste.ini
Which doesn't exist on the deployment.

This issue is reproducible.
Comment 2 Christopher Brown 2017-06-17 19:32:02 UTC 
Ugh, stale bug, should probably be closed now.
Note You need to log in before you can comment on or make changes to this bug.