force_config_drive=True don't go to db
Bug #1303714 reported by
Nikolay Starodubtsev
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
In Progress
|
Wishlist
|
sean mooney |
Bug Description
If we use --config-drive=True via client we'll have filled config_drive column in db. In the other hand if we use force_config_
tags: | added: db |
Changed in nova: | |
assignee: | nobody → Michael Still (mikalstill) |
Changed in nova: | |
status: | Confirmed → In Progress |
Changed in nova: | |
assignee: | nobody → Zhenzan Zhou (zhenzan-zhou) |
Changed in nova: | |
assignee: | Zhenzan Zhou (zhenzan-zhou) → Stephen Finucane (sfinucan) |
status: | Confirmed → In Progress |
Changed in nova: | |
assignee: | Stephen Finucane (sfinucan) → nobody |
status: | In Progress → Confirmed |
Changed in nova: | |
assignee: | nobody → Stephen Finucane (sfinucan) |
Changed in nova: | |
status: | Confirmed → In Progress |
Changed in nova: | |
assignee: | nobody → yuanyue (yyuanyuee) |
status: | Confirmed → In Progress |
Changed in nova: | |
assignee: | yuanyue (yyuanyuee) → Matthew Booth (mbooth-9) |
Changed in nova: | |
assignee: | Matthew Booth (mbooth-9) → sean mooney (sean-k-mooney) |
To post a comment you must log in.
Are you saying --config-drive=True via client and force_config_ drive=True via nova.conf should both set the config_drive db column? I believe it maybe intended to work that way because if force_config_ drive=False in nova.conf, setting --config-drive=True via client is a way to override the nova.conf setting.