Unable to log into overcloud BM instance when using OVN
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
High
|
Harald Jensås |
Bug Description
cloud-init-
cloud-init-
Ironic service deployment have always enabled force_config_drive because with baremetal the config drive is required. (see: deployment/
Since the switch to OVN, the ovn service disables force_config_drive when OVNMetadataAgent is enabled.
There are usecases when operator wants to talk to metadata API from config-drive script (e.g. using curl to get data from metadata). That means it makes sense to have OVN Metadata Agent deployed while forcing config-drive to be used.
Changed in tripleo: | |
assignee: | nobody → Harald Jensås (harald-jensas) |
status: | Triaged → In Progress |
Reviewed: https:/ /review. opendev. org/660689 /git.openstack. org/cgit/ openstack/ tripleo- heat-templates/ commit/ ?id=7ac8e67d82e 688382c3ea13c48 b0cb55f759117b
Committed: https:/
Submitter: Zuul
Branch: master
commit 7ac8e67d82e6883 82c3ea13c48b0cb 55f759117b
Author: Jakub Libosvar <email address hidden>
Date: Wed May 22 13:47:37 2019 +0200
Set force_config_drive only when OVNMetadata is disabled
There are usecases when operator wants to talk to metadata API from
config-drive script (e.g. using curl to get data from metadata). That
means it makes sense to have OVN Metadata Agent deployed while forcing
config-drive to be used.
This patch sets force_config_drive to true only when OVNMetadataEnable config_ drive option, leaving it up to environment to define it.
is set to false. If it's set to true then it doesn't touch
force_
(The default for force_config_drive is false.)
Closes-Bug: #1830179 53c58eaa5500836 c692dd9321d
Change-Id: Ib956ff2f521b98