cannot import name constants

Bug #1509934 reported by Atsushi SAKAI
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
networking-vsphere
Incomplete
Undecided
Unassigned
openstack-manuals
Fix Released
Medium
Unassigned

Bug Description

During Module importing on Config Reference Auto generation,
It appears following error.

Failed to import: networking_vsphere.nova.virt.vmwareapi.ovsvapp_vmops (cannot import name constants)

Without this fixes, under networking_vsphere.nova.virt.vmwareapi.ovsvapp_vmopts directory's
config parameter cannot be imported.

Autogeneration tool is located on
https://github.com/openstack/openstack-doc-tools/blob/master/autogenerate_config_docs/autohelp-wrapper

Related incident is follows
https://bugs.launchpad.net/openstack-manuals/+bug/1503967

Tom Fifield (fifieldt)
tags: added: autogenerate-config-docs doc-builds doc-tools vmware
Changed in openstack-manuals:
milestone: none → mitaka
importance: Undecided → Medium
status: New → Confirmed
Changed in openstack-manuals:
milestone: mitaka → newton
Revision history for this message
Aman Kumar (amank) wrote :

I am not sure what changes we need to do in Networking-vSphere.
It seems like fully openstack-manuals bug.

Changed in networking-vsphere:
status: New → Incomplete
Changed in openstack-manuals:
milestone: newton → ocata
Changed in openstack-manuals:
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.