Incorrect URL in XML used by libvirt to launch instance

Bug #1695533 reported by Rahul Sharma
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Invalid
Undecided
Unassigned

Bug Description

I launched an instance using Devstack running on QEMU hypervisor. I dumped the XML of VM to see what things are getting configured and found a URL in the XML. The URL points to a page which no longer exists on the openstack.org website. I guess this URL gets embedded in each VM's XML. Though it does nothing (maybe pointing to the syntax used to define XML), and I am interested in this URL. I have filed this bug so that the URL can be corrected or can be removed from the XML. Attached is the full dumpxml. Here is a snippet of it:

  <metadata>
    <nova:instance xmlns:nova="http://openstack.org/xmlns/libvirt/nova/1.0">
      <nova:package version="16.0.0"/>
      <nova:name>ttt</nova:name>

Steps to reproduce:
1. Launch an instance
2. Goto compute node where the instance is running.
3. Do "virsh dumpxml <instance-name>"
4. Check the URL in dumped output.

Revision history for this message
Rahul Sharma (rahulsharmaait) wrote :
Revision history for this message
Markus Zoeller (markus_z) (mzoeller) wrote :

I don't think that this is a valid bug, as the XML namespace URI is usually not a "real" URI. In Wikipedia you will also find:

    "[...] the namespace specification does not
    require nor suggest that the namespace URI
    be used to retrieve information. [...]"

https://en.wikipedia.org/wiki/XML_namespace

FWIW:
The XML metadata in the domain XML got introduced with commit
    https://github.com/openstack/nova/commit/bf02f13
The blueprint is this:
    http://specs.openstack.org/openstack/nova-specs/specs/juno/implemented/libvirt-driver-domain-metadata.html

Changed in nova:
status: New → Invalid
Revision history for this message
Markus Zoeller (markus_z) (mzoeller) wrote :

@Rahul: I closed this bug report because of the given explanation in the previous comment. If you disagree with my reasoning, please reopen the bug (== set the status back to 'new').

Revision history for this message
Rahul Sharma (rahulsharmaait) wrote :

Thanks @Markus. That makes sense.

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.