Currently used logic for enabling swiftcheck service is
not correct. Additional checks for Keystone availability
from Swift node should be added to HAProxy if management VIP
and Swift proxy IP addresses are from different L3 networks.
Change-Id: I9513fc9da02abdc24cc61a60c33181bb0fc9235b
Closes-bug: #1548275
(cherry picked from commit 766335df60c98b610748072b1f1663d482574a72)
(cherry picked from commit 1d5f133fb7162d10b42bfa305e6d1a96cc15ed1b)
Reviewed: https:/ /review. openstack. org/312600 /git.openstack. org/cgit/ openstack/ fuel-library/ commit/ ?id=74a367f8aff 0d9b55be857e0ef 9f8bec2c0ed884
Committed: https:/
Submitter: Jenkins
Branch: stable/8.0
commit 74a367f8aff0d9b 55be857e0ef9f8b ec2c0ed884
Author: Artem Panchenko <email address hidden>
Date: Mon Apr 4 16:47:03 2016 +0300
Fix logic for enabling 'swiftcheck' service
Currently used logic for enabling swiftcheck service is
not correct. Additional checks for Keystone availability
from Swift node should be added to HAProxy if management VIP
and Swift proxy IP addresses are from different L3 networks.
Change-Id: I9513fc9da02abd c24cc61a60c3318 1bb0fc9235b 10748072b1f1663 d482574a72) 0b42bfa305e6d1a 96cc15ed1b)
Closes-bug: #1548275
(cherry picked from commit 766335df60c98b6
(cherry picked from commit 1d5f133fb7162d1