Disable Bifrost cleaning by default
Cleaning was disabled by default in Bifrost (Ie1198768889bd468176cd68c8ccb48791c724262) until the Victoria release, when the default was changed. The 'kayobe overcloud provision' command does not handle cleaning states when moving nodes from manageable to available. This can lead to provisioning failures. This change disables cleaning to maintain backwards compatibility with earlier versions of Kayobe. Change-Id: I23eb5116d8d1944167a0d50cafe5b99f766ad687 Story: 2008850 Task: 42363
This commit is contained in:
parent
1561c27fba
commit
d45812d3ba
@ -73,6 +73,10 @@ noauth_mode: true
|
||||
# Enable discovery of nodes in Ironic Inspector.
|
||||
enable_inspector_discovery: true
|
||||
|
||||
# Disable cleaning for backwards compatibility. It is enabled by default in
|
||||
# Bifrost since the Victoria release.
|
||||
cleaning: false
|
||||
|
||||
{% if kolla_bifrost_extra_globals %}
|
||||
###############################################################################
|
||||
# Extra configuration
|
||||
|
@ -0,0 +1,7 @@
|
||||
---
|
||||
upgrade:
|
||||
- |
|
||||
Until the Victoria release, Bifrost disabled node cleaning, however it
|
||||
became enabled in Victoria. To maintain backward compatibility, Kayobe now
|
||||
modifies the configuration in Bifrost to disable node cleaning of overcloud
|
||||
hosts.
|
Loading…
x
Reference in New Issue
Block a user