[Docs] Wrong name of configuration drive format parameter

Bug #1665976 reported by Alexander Rubtsov on 2017-02-19
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Oleksiy Molchanov

Bug Description

 --- Related links ---
Related guide: https://docs.openstack.org/developer/fuel-docs/userdocs/fuel-user-guide/configure-environment/config-drive-format.html
Related commit: https://review.openstack.org/#/c/321517/1/userdocs/fuel-user-guide/configure-environment/config-drive-format.rst

 --- Description ---
The current parameter name "config_drive_format option" is wrong.
The corresponding Puppet manifest handles "config_drive_format" value: https://review.openstack.org/#/c/295298/4/deployment/puppet/openstack_tasks/manifests/roles/compute.pp

 --- Impact ---
With this parameter in place, the deployed environment doesn't get the specified value of configuration drive format in nova.conf

 --- Actual value ---
config_drive_format option

 --- Expected value ---

Alexander Rubtsov (arubtsov) wrote :
Changed in fuel:
importance: Undecided → Medium
Changed in fuel:
assignee: nobody → Michael Glaser (mikeg451)
Michael Glaser (mikeg451) wrote :

Alexander, Doesn't this also need to be changed in Newton?

Alexander Rubtsov (arubtsov) wrote :


As this option is in place in the corresponding Puppet manifest for stable/newton, I suppose the documentation change is relevant for Newton as well:

Fix proposed to branch: master
Review: https://review.openstack.org/436061

Changed in fuel:
status: New → In Progress
Michael Glaser (mikeg451) wrote :

Will unassign myself from the Mitaka change since I'm getting a error when I do a git review for Mitaka and Newton changes:

git review
Errors running git rebase -i remotes/gerrit/master
error: could not apply 30d90cb... Added NFV features to the Fuel User Guide

Will let someone with better git knowledge than I have work on the Mitaka change.

Changed in fuel:
milestone: none → 10.x-updates

Change abandoned by Joshua Hesketh (<email address hidden>) on branch: stable/mitaka
Review: https://review.openstack.org/436976
Reason: This branch (stable/mitaka) is at End Of Life

Alexander Rubtsov (arubtsov) wrote :

Another customer has hit this issue.
Could you please correct the documentation for Mitaka?

Michael Glaser (mikeg451) wrote :


The fix for this in Mitaka was committed in February by Oleksiy with 1 review.
it was abandon by in Sept with the comment: (stable/mitaka) is at End Of Life

The master branch fix for this was committed in February, but has never gotten any reviews:

The newton branch fix was committed in February and has a single review:

The fixes are out there, but the CR's need to take a look and merge or comment.

Michael Glaser (mikeg451) wrote :

There have been no reviews for this commit to fix this.
I'll abandon the commit and release the bug to someone else.

Changed in fuel:
assignee: Michael Glaser (mikeg451) → nobody

Change abandoned by Michael Glaser (<email address hidden>) on branch: master
Review: https://review.openstack.org/436061
Reason: No reviews after almost a year so will abandon and let someone else give it a go.

Change abandoned by Andreas Jaeger (<email address hidden>) on branch: stable/newton
Review: https://review.opendev.org/436977
Reason: This repo is retired now, no further work will get merged.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers