From 2941d88ef28166cd0ebd677c4de8176e1befe044 Mon Sep 17 00:00:00 2001 From: Sylvain Bauza Date: Fri, 27 Nov 2015 16:20:04 +0100 Subject: [PATCH] Add note for force_config_drive opt change Change 296479e1abbfccb04584e341002401909c85be77 removed support of 'always' for force_config_drive opt. We need to provide a reno file for that. Change-Id: I1c7ad84196acb045406bbd974fe2e846d135b87d --- .../notes/force_config_drive_opt-e087055e14c40d88.yaml | 7 +++++++ 1 file changed, 7 insertions(+) create mode 100644 releasenotes/notes/force_config_drive_opt-e087055e14c40d88.yaml diff --git a/releasenotes/notes/force_config_drive_opt-e087055e14c40d88.yaml b/releasenotes/notes/force_config_drive_opt-e087055e14c40d88.yaml new file mode 100644 index 0000000000..7ee8deeb27 --- /dev/null +++ b/releasenotes/notes/force_config_drive_opt-e087055e14c40d88.yaml @@ -0,0 +1,7 @@ +--- +upgrade: + - | + The ``force_config_drive`` configuration option provided an ``always`` + value which was deprecated in the previous release. That ``always`` value + is now no longer accepted and deployments using that value have to change + it to ``True`` before upgrading.