Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
K
Kolla Ansible
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package Registry
Container Registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Very Demiurge Very Mindful
Kolla Ansible
Commits
02ba8bb8
Commit
02ba8bb8
authored
4 years ago
by
Zuul
Committed by
Gerrit Code Review
4 years ago
Browse files
Options
Downloads
Plain Diff
Merge "Prevent overwriting existing Keystone Fernet keys"
parents
42f57166
8389140f
No related branches found
No related tags found
No related merge requests found
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
ansible/roles/keystone/tasks/bootstrap_service.yml
+18
-0
18 additions, 0 deletions
ansible/roles/keystone/tasks/bootstrap_service.yml
releasenotes/notes/prevent-keystone-bootstrap-limit-f0250725633c16de.yaml
+7
-0
7 additions, 0 deletions
...es/prevent-keystone-bootstrap-limit-f0250725633c16de.yaml
with
25 additions
and
0 deletions
ansible/roles/keystone/tasks/bootstrap_service.yml
+
18
−
0
View file @
02ba8bb8
...
...
@@ -6,10 +6,28 @@
-
keystone_fernet
register
:
container_facts
# FIXME(mgoddard): This does not catch some cases we might consider
# bootstrapped:
# * the keystone_fernet container is created but not running
# * the keystone_fernet volume exists but no container
# Probably what we care about is the existence of Fernet key 0.
-
name
:
Group nodes where keystone_fernet is running
group_by
:
key
:
keystone_fernet_{{ container_facts['keystone_fernet'].State | default('bootstrap') }}
# NOTE(mgoddard): If we bootstrap Fernet keys on an existing cluster, this
# would overwrite existing keys, and invalidate tokens created from them.
-
name
:
Fail if any hosts need bootstrapping and not all hosts targeted
fail
:
msg
:
>
Some hosts ({{ groups['keystone_fernet_bootstrap'] | join(', ') }}) need
Fernet key bootstrapping, but not all Keystone hosts are in the target
list. Stopping as it may be unsafe to proceed. Please run without --limit
or --serial to bootstrap these hosts.
when
:
-
groups['keystone_fernet_running'] is not defined
-
groups['keystone'] | difference(ansible_play_batch) | list | length >
0
-
name
:
Running Keystone bootstrap container
vars
:
keystone
:
"
{{
keystone_services.keystone
}}"
...
...
This diff is collapsed.
Click to expand it.
releasenotes/notes/prevent-keystone-bootstrap-limit-f0250725633c16de.yaml
0 → 100644
+
7
−
0
View file @
02ba8bb8
---
fixes
:
-
|
Prevents adding a new Keystone host to an existing cluster when not
targeting all Keystone hosts (e.g. due to ``--limit`` or ``--serial``
arguments), to avoid overwriting existing Fernet keys. `LP#1891364
<https://bugs.launchpad.net/kolla-ansible/+bug/1891364>`__
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment