Change of DNS name for public endpoints after environment reset breaks deploy
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Fix Released
|
High
|
Maciej Kwiek | ||
7.0.x |
Fix Released
|
High
|
Denis Meltsaykin |
Bug Description
Fuel 7.0:
{"build_id": "301", "build_number": "301", "release_versions": {"2015.1.0-7.0": {"VERSION": {"build_id": "301", "build_number": "301", "api": "1.0", "fuel-library_sha": "5d50055aeca1dd
Steps to reproduce:
1) Create the environment with default settings in "Public TLS" section (DNS hostname for public TLS endpoints set to default "public.fuel.local"
2) Deploy environment
3) Reset environment
4) Change DNS hostname for public TLS endpoints to "public.test.local"
5) Try to deploy environment
Deployment will fail with error like:
(/Stage[
Diagnostic snapshot from this fuel master is about 700M, attaching only puppet log from affected controller.
Changed in fuel: | |
assignee: | nobody → Fuel Library Team (fuel-library) |
importance: | Undecided → High |
milestone: | none → 8.0 |
Changed in fuel: | |
status: | New → Confirmed |
tags: | added: area-library |
tags: |
added: area-python removed: area-library |
Changed in fuel: | |
assignee: | Fuel Python Team (fuel-python) → Maciej Kwiek (maciej-iai) |
tags: | added: team-bugfix |
tags: | added: on-verification |
Changed in fuel: | |
status: | Fix Committed → Fix Released |
tags: | added: customer-found |
tags: | added: on-verification |
Since a user can rename any node after reset, we should clear TLS config on reset env. There's no value in re-using the old cert data because it will not be valid for the new deployment. Passing to fuel-python