Actions
Issue #6973
closedCluster Install: Ensure database initialization is run only on one node
Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
Assignee:
-
Category:
Installer - Moved to GitHub issues
Sprint/Milestone:
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Version:
Platform Release:
OS:
Triaged:
No
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Quarter:
Description
I am running a cluster install with pulp/pulp_installer
. This is the following snippet of interest
Inventory:
[pulp]
pulp01
pulp02
pulp03
playbook
---
- hosts: pulp
roles:
- pulp_database
Current run create failures when running the migrations because it tries to run it on the different nodes, while it works fine on the first node it reaches it fails on the other 2 because unique constraint is violated.
Actions
cluster: Allow installer to finish with no failures
Currently running the installer in cluster setup will trigger 2 errors becauee it tries to run the db migration more than one time.
The following commit ensures that db migration are just run once from the pool of node selected.
fixes #6973