Error: internal error no supported architecture for os type 'hvm'

Bug #804450 reported by Diego Lalo
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Invalid
Undecided
Unassigned

Bug Description

Hi everyone, I think maybe I found a bug because I updated all the nova packages and I still have the issue, here are the packages I have:

nova-api_2011.3~d3~20110701.1244-0ubuntu0ppa1~maverick1_all.deb
-rw-r--r-- 1 root root 24528 2011-07-01 17:12 nova-common_2011.3~d3~20110701.1244-0ubuntu0ppa1~maverick1_all.deb
-rw-r--r-- 1 root root 9768 2011-07-01 17:12 nova-compute_2011.3~d3~20110701.1244-0ubuntu0ppa1~maverick1_all.deb
-rw-r--r-- 1 root root 1794284 2011-07-01 17:12 nova-doc_2011.3~d3~20110701.1244-0ubuntu0ppa1~maverick1_all.deb
-rw-r--r-- 1 root root 11094 2011-07-01 17:12 nova-network_2011.3~d3~20110701.1244-0ubuntu0ppa1~maverick1_all.deb
-rw-r--r-- 1 root root 9868 2011-07-01 17:12 nova-objectstore_2011.3~d3~20110701.1244-0ubuntu0ppa1~maverick1_all.deb
-rw-r--r-- 1 root root 9542 2011-07-01 17:12 nova-scheduler_2011.3~d3~20110701.1244-0ubuntu0ppa1~maverick1_all.deb

The problem is that I can't launch instances, when I try to launch a new instance I get the following error in nova-compute.log:

2011-07-01 18:43:08,309 DEBUG nova.rpc [-] unpacked context: {'timestamp': u'2011-07-01T17:43:07Z', 'msg_id': None, 'remote_address': u'10.0.20.30', 'project': u'proj1', 'is_admin': True, 'user': u'diegote', 'request_id': u'W0CKDSKB0W1-1DSL3HOP', 'read_deleted': False} from (pid=1811) _unpack_context /usr/lib/pymodules/python2.6/nova/rpc.py:451
2011-07-01 18:43:08,360 AUDIT nova.compute.manager [W0CKDSKB0W1-1DSL3HOP diegote proj1] instance 2: starting...
2011-07-01 18:43:08,460 DEBUG nova.rpc [-] Making asynchronous call on network ... from (pid=1811) multicall /usr/lib/pymodules/python2.6/nova/rpc.py:481
2011-07-01 18:43:08,460 DEBUG nova.rpc [-] MSG_ID is 69e816d625cb4c0a94934bd309166836 from (pid=1811) multicall /usr/lib/pymodules/python2.6/nova/rpc.py:484
2011-07-01 18:43:08,951 DEBUG nova.compute.manager [-] instance network_info: |[[{u'injected': False, u'bridge': u'br100', u'cidr_v6': None, u'cidr': u'192.168.3.0/25', u'id': 1}, {u'label': u'public', u'broadcast': u'192.168.3.127', u'ips': [{u'ip': u'192.168.3.3', u'netmask': u'255.255.255.128', u'enabled': u'1'}], u'mac': u'02:16:3e:1f:d2:ac', u'rxtx_cap': 0, u'dns': [u'8.8.4.4'], u'gateway': u'192.168.3.1'}]]| from (pid=1811) _run_instance /usr/lib/pymodules/python2.6/nova/compute/manager.py:295
2011-07-01 18:43:08,967 DEBUG nova.utils [-] Attempting to grab semaphore "ensure_bridge" for method "ensure_bridge"... from (pid=1811) inner /usr/lib/pymodules/python2.6/nova/utils.py:600
2011-07-01 18:43:08,967 DEBUG nova.utils [-] Attempting to grab file lock "ensure_bridge" for method "ensure_bridge"... from (pid=1811) inner /usr/lib/pymodules/python2.6/nova/utils.py:605
2011-07-01 18:43:08,968 DEBUG nova.utils [-] Running cmd (subprocess): ip link show dev br100 from (pid=1811) execute /usr/lib/pymodules/python2.6/nova/utils.py:143
2011-07-01 18:43:09,195 DEBUG nova.virt.libvirt_conn [-] instance instance-00000002: starting toXML method from (pid=1811) to_xml /usr/lib/pymodules/python2.6/nova/virt/libvirt/connection.py:1035
2011-07-01 18:43:09,273 DEBUG nova.virt.libvirt_conn [-] instance instance-00000002: finished toXML method from (pid=1811) to_xml /usr/lib/pymodules/python2.6/nova/virt/libvirt/connection.py:1039
2011-07-01 18:43:09,274 INFO nova [-] called setup_basic_filtering in nwfilter
2011-07-01 18:43:09,276 INFO nova [-] ensuring static filters
2011-07-01 18:43:09,299 DEBUG nova.virt.libvirt.firewall [-] iptables firewall: Setup Basic Filtering from (pid=1811) setup_basic_filtering /usr/lib/pymodules/python2.6/nova/virt/libvirt/firewall.py:537
2011-07-01 18:43:09,299 DEBUG nova.utils [-] Attempting to grab semaphore "iptables" for method "_do_refresh_provider_fw_rules"... from (pid=1811) inner /usr/lib/pymodules/python2.6/nova/utils.py:600
2011-07-01 18:43:09,300 DEBUG nova.utils [-] Attempting to grab file lock "iptables" for method "_do_refresh_provider_fw_rules"... from (pid=1811) inner /usr/lib/pymodules/python2.6/nova/utils.py:605
2011-07-01 18:43:09,303 DEBUG nova.utils [-] Attempting to grab semaphore "iptables" for method "apply"... from (pid=1811) inner /usr/lib/pymodules/python2.6/nova/utils.py:600
2011-07-01 18:43:09,303 DEBUG nova.utils [-] Attempting to grab file lock "iptables" for method "apply"... from (pid=1811) inner /usr/lib/pymodules/python2.6/nova/utils.py:605
2011-07-01 18:43:09,304 DEBUG nova.utils [-] Running cmd (subprocess): sudo iptables-save -t filter from (pid=1811) execute /usr/lib/pymodules/python2.6/nova/utils.py:143
2011-07-01 18:43:09,332 DEBUG nova.utils [-] Running cmd (subprocess): sudo iptables-restore from (pid=1811) execute /usr/lib/pymodules/python2.6/nova/utils.py:143
2011-07-01 18:43:09,361 DEBUG nova.utils [-] Running cmd (subprocess): sudo iptables-save -t nat from (pid=1811) execute /usr/lib/pymodules/python2.6/nova/utils.py:143
2011-07-01 18:43:09,395 DEBUG nova.utils [-] Running cmd (subprocess): sudo iptables-restore from (pid=1811) execute /usr/lib/pymodules/python2.6/nova/utils.py:143
2011-07-01 18:43:09,465 DEBUG nova.utils [-] Attempting to grab semaphore "iptables" for method "apply"... from (pid=1811) inner /usr/lib/pymodules/python2.6/nova/utils.py:600
2011-07-01 18:43:09,466 DEBUG nova.utils [-] Attempting to grab file lock "iptables" for method "apply"... from (pid=1811) inner /usr/lib/pymodules/python2.6/nova/utils.py:605
2011-07-01 18:43:09,466 DEBUG nova.utils [-] Running cmd (subprocess): sudo iptables-save -t filter from (pid=1811) execute /usr/lib/pymodules/python2.6/nova/utils.py:143
2011-07-01 18:43:09,496 DEBUG nova.utils [-] Running cmd (subprocess): sudo iptables-restore from (pid=1811) execute /usr/lib/pymodules/python2.6/nova/utils.py:143
2011-07-01 18:43:09,532 DEBUG nova.utils [-] Running cmd (subprocess): sudo iptables-save -t nat from (pid=1811) execute /usr/lib/pymodules/python2.6/nova/utils.py:143
2011-07-01 18:43:09,573 DEBUG nova.utils [-] Running cmd (subprocess): sudo iptables-restore from (pid=1811) execute /usr/lib/pymodules/python2.6/nova/utils.py:143
2011-07-01 18:43:09,614 DEBUG nova.utils [-] Running cmd (subprocess): mkdir -p /var/lib/nova/instances/instance-00000002/ from (pid=1811) execute /usr/lib/pymodules/python2.6/nova/utils.py:143
2011-07-01 18:43:09,631 INFO nova.virt.libvirt_conn [-] instance instance-00000002: Creating image
2011-07-01 18:43:09,650 DEBUG nova.utils [-] Attempting to grab semaphore "00000002" for method "call_if_not_exists"... from (pid=1811) inner /usr/lib/pymodules/python2.6/nova/utils.py:600
2011-07-01 18:43:09,651 DEBUG nova.utils [-] Running cmd (subprocess): cp /var/lib/nova/instances/_base/00000002 /var/lib/nova/instances/instance-00000002/kernel from (pid=1811) execute /usr/lib/pymodules/python2.6/nova/utils.py:143
2011-07-01 18:43:09,764 DEBUG nova.utils [-] Attempting to grab semaphore "00000003" for method "call_if_not_exists"... from (pid=1811) inner /usr/lib/pymodules/python2.6/nova/utils.py:600
2011-07-01 18:43:09,767 DEBUG nova.utils [-] Running cmd (subprocess): cp /var/lib/nova/instances/_base/00000003 /var/lib/nova/instances/instance-00000002/ramdisk from (pid=1811) execute /usr/lib/pymodules/python2.6/nova/utils.py:143
2011-07-01 18:43:09,857 DEBUG nova.utils [-] Attempting to grab semaphore "356a192b7913b04c54574d18c28d46e6395428ab_sm" for method "call_if_not_exists"... from (pid=1811) inner /usr/lib/pymodules/python2.6/nova/utils.py:600
2011-07-01 18:43:09,858 DEBUG nova.utils [-] Running cmd (subprocess): qemu-img create -f qcow2 -o cluster_size=2M,backing_file=/var/lib/nova/instances/_base/356a192b7913b04c54574d18c28d46e6395428ab_sm /var/lib/nova/instances/instance-00000002/disk from (pid=1811) execute /usr/lib/pymodules/python2.6/nova/utils.py:143
2011-07-01 18:43:09,997 ERROR nova.exception [-] Uncaught exception
(nova.exception): TRACE: Traceback (most recent call last):
(nova.exception): TRACE: File "/usr/lib/pymodules/python2.6/nova/exception.py", line 87, in _wrap
(nova.exception): TRACE: return f(*args, **kw)
(nova.exception): TRACE: File "/usr/lib/pymodules/python2.6/nova/virt/libvirt/connection.py", line 591, in spawn
(nova.exception): TRACE: domain = self._create_new_domain(xml)
(nova.exception): TRACE: File "/usr/lib/pymodules/python2.6/nova/virt/libvirt/connection.py", line 1085, in _create_new_domain
(nova.exception): TRACE: domain = self._conn.defineXML(xml)
(nova.exception): TRACE: File "/usr/lib/python2.6/dist-packages/libvirt.py", line 1368, in defineXML
(nova.exception): TRACE: if ret is None:raise libvirtError('virDomainDefineXML() failed', conn=self)
(nova.exception): TRACE: libvirtError: internal error no supported architecture for os type 'hvm'
(nova.exception): TRACE:
2011-07-01 18:43:10,027 ERROR nova.compute.manager [-] Instance '2' failed to spawn. Is virtualization enabled in the BIOS? Details: internal error no supported architecture for os type 'hvm'
(nova.compute.manager): TRACE: Traceback (most recent call last):
(nova.compute.manager): TRACE: File "/usr/lib/pymodules/python2.6/nova/compute/manager.py", line 311, in _run_instance
(nova.compute.manager): TRACE: self.driver.spawn(instance, network_info, bd_mapping)
(nova.compute.manager): TRACE: File "/usr/lib/pymodules/python2.6/nova/exception.py", line 93, in _wrap
(nova.compute.manager): TRACE: raise Error(str(e))
(nova.compute.manager): TRACE: Error: internal error no supported architecture for os type 'hvm'
(nova.compute.manager): TRACE:
2011-07-01 18:43:10,621 INFO nova.compute.manager [-] Updating host status
2011-07-01 18:43:10,658 INFO nova.compute.manager [-] Found instance 'instance-00000002' in DB but no VM. State=8, so setting state to shutoff.
2011-07-01 18:43:10,658 INFO nova.compute.manager [-] DB/VM state mismatch. Changing state from '8' to '5'

I went to /var/lib/nova/instances/instance-00000002/ and watched libvirt.xml file, here is it's contents:

<domain type='kvm'>
    <name>instance-00000002</name>
    <memory>524288</memory>
    <os>
            <type>hvm</type>
            <kernel>/var/lib/nova/instances/instance-00000002/kernel</kernel>
                <cmdline>root=/dev/vda console=ttyS0</cmdline>
                <initrd>/var/lib/nova/instances/instance-00000002/ramdisk</initrd>
    </os>
    <features>
        <acpi/>
    </features>
    <vcpu>1</vcpu>
    <devices>
        <disk type='file'>
            <driver type='qcow2'/>
            <source file='/var/lib/nova/instances/instance-00000002/disk'/>
            <target dev='vda' bus='virtio'/>
        </disk>

        <interface type='bridge'>
            <source bridge='br100'/>
            <mac address='02:16:3e:1f:d2:ac'/>
            <!-- <model type='virtio'/> CANT RUN virtio network right now -->
            <filterref filter="nova-instance-instance-00000002-02163e1fd2ac">
                <parameter name="IP" value="192.168.3.3" />
                <parameter name="DHCPSERVER" value="192.168.3.1" />
            </filterref>
        </interface>
        <!-- The order is significant here. File must be defined first -->
        <serial type="file">
            <source path='/var/lib/nova/instances/instance-00000002/console.log'/>
            <target port='1'/>
        </serial>

        <console type='pty' tty='/dev/pts/2'>
            <source path='/dev/pts/2'/>
            <target port='0'/>
        </console>

        <serial type='pty'>
            <source path='/dev/pts/2'/>
            <target port='0'/>
        </serial>

        <graphics type='vnc' port='-1' autoport='yes' keymap='en-us' listen='0.0.0.0'/>
    </devices>
</domain>

After googling a little I tried this modification:

<type arch="i686">hvm</type>

with this modification I executed: "virsh create libvirt.xml" and the domain was successfully created. I'm not sure if this is a bug or not but I post it anyway :)

Cheers
Diego

Revision history for this message
Thierry Carrez (ttx) wrote :

This is the error you get with KVM when running on unsupported hardware. You need a VT-enabled processor to use KVM, and make sure that virtualization is enabled in the BIOS. The "kvm-ok" command on Ubuntu can help you in troubleshooting that.

Changed in nova:
status: New → Invalid
Revision history for this message
Diego Lalo (diego-lalo) wrote :

     Hi Thierry, this is the output of kvm-ok on the machine I had the problem:

kvm-ok
INFO: Your CPU supports KVM extensions
INFO: /dev/kvm exists
KVM acceleration can be used

With this version of the nova packages I don't have the error I posted:

ii nova-api 2011.3~bzr1058-0ubuntu0ppa1~maverick1 OpenStack Compute - API frontend
ii nova-common 2011.3~bzr1058-0ubuntu0ppa1~maverick1 OpenStack Compute - common files
ii nova-compute 2011.3~bzr1058-0ubuntu0ppa1~maverick1 OpenStack Compute - compute node
ii nova-doc 2011.3~bzr1058-0ubuntu0ppa1~maverick1 OpenStack Compute - documetation
ii nova-network 2011.3~bzr1058-0ubuntu0ppa1~maverick1 OpenStack Compute - Network manager
ii nova-objectstore 2011.3~bzr1058-0ubuntu0ppa1~maverick1 OpenStack Compute - object store
ii nova-scheduler 2011.3~bzr1058-0ubuntu0ppa1~maverick1 OpenStack Compute - virtual machine scheduler
ii python-nova 2011.3~bzr1058-0ubuntu0ppa1~maverick1 OpenStack Compute Python libraries
ii python-novaclient 2.4-0ubuntu1~ppa1

Cheers
Diego

Revision history for this message
Thierry Carrez (ttx) wrote :

Interesting. So you have the issue with rev1244 but not with rev1058... Is it the only difference ? For example, is libvirt version the same in both cases ?

I'm asking because the error you get is actually not from Nova, but from libvirt (nova calls virDomainDefineXML() and libvirt answers "internal error no supported architecture for os type 'hvm'", which is the cryptic error that libvirt returns when CPU does not support KVM extensions).

Changed in nova:
status: Invalid → Incomplete
Revision history for this message
Diego Lalo (diego-lalo) wrote :

Yes Thierry, is the same version:

root@eucalyptus:~# libvirtd --version
libvirtd (libvirt) 0.8.8
root@eucalyptus:~#

root@openstack-in-a-box-1rev87:~# libvirtd --version
libvirtd (libvirt) 0.8.8
root@openstack-in-a-box-1rev87:~#

Now I'm also having another problem when I try to create a network for the project I think it is a bug because I don't have this issue with rev1058 but I have it with rev1244, the machine that has rev1244 is eucalyptus and the machine which has the revision1058 is openstack-in-a-box-rev87

Revision history for this message
Thierry Carrez (ttx) wrote :

Hmm, I don't get it... <type>hvm</type> has been there forever and the libvirt version looks the same...

Could you try "virsh create libvirt.xml" with both versions of the XML file (<type arch="i686">hvm</type> and <type>hvm</type>) on both machines ?

Also provide the exact version of the libvirt package (dpkg -l python-libvirt) for each.

Revision history for this message
Diego Lalo (diego-lalo) wrote :
Download full text (6.5 KiB)

 Hi Thierry sorry for the delay, I was working on other stuffs, here is the info:

MACHINE 1 => eucalyptus
root@eucalyptus:/var/lib/nova/instances/instance-00000001# dpkg -l | grep nova
ii nova-api 2011.3~d3~20110630.1236-0ubuntu0ppa1~maverick1 OpenStack Compute - API frontend
ii nova-common 2011.3~d3~20110630.1236-0ubuntu0ppa1~maverick1 OpenStack Compute - common files
ii nova-compute 2011.3~d3~20110630.1236-0ubuntu0ppa1~maverick1 OpenStack Compute - compute node
ii nova-network 2011.3~d3~20110630.1236-0ubuntu0ppa1~maverick1 OpenStack Compute - Network manager
ii nova-objectstore 2011.3~d3~20110630.1236-0ubuntu0ppa1~maverick1 OpenStack Compute - object store
ii nova-scheduler 2011.3~d3~20110630.1236-0ubuntu0ppa1~maverick1 OpenStack Compute - virtual machine scheduler
ii python-nova 2011.3~d3~20110630.1236-0ubuntu0ppa1~maverick1 OpenStack Compute Python libraries
ii python-novaclient 2.4.2~bzr25-0ubuntu0ppa1~maverick3 client library for OpenStack Compute API

MACHINE 2 =>openstack-in-a-box-1rev87
root@openstack-in-a-box-1rev87:/var/lib/nova/instances/instance-00000001# dpkg -l | grep nova
ii nova-api 2011.3~bzr1058-0ubuntu0ppa1~maverick1 OpenStack Compute - API frontend
ii nova-common 2011.3~bzr1058-0ubuntu0ppa1~maverick1 OpenStack Compute - common files
ii nova-compute 2011.3~bzr1058-0ubuntu0ppa1~maverick1 OpenStack Compute - compute node
ii nova-doc 2011.3~bzr1058-0ubuntu0ppa1~maverick1 OpenStack Compute - documetation
ii nova-network 2011.3~bzr1058-0ubuntu0ppa1~maverick1 OpenStack Compute - Network manager
ii nova-objectstore 2011.3~bzr1058-0ubuntu0ppa1~maverick1 OpenStack Compute - object store
ii nova-scheduler 2011.3~bzr1058-0ubuntu0ppa1~maverick1 OpenStack Compute - virtual machine scheduler
ii python-nova 2011.3~bzr1058-0ubuntu0ppa1~maverick1 OpenStack Compute Python libraries
ii python-novaclient 2.4-0ubuntu1~ppa1 client library for OpenStack Compute API

PYHTON-LIBVIRT ON BOTH MACHINES

MACHINE1)
root@eucalyptus:~# dpkg -l python-libvirt
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Description
+++-============================================-============================================-========================================================================================================
ii python-libvirt ...

Read more...

Revision history for this message
Thierry Carrez (ttx) wrote :

Might be that "openstack-in-a-box-1rev87" is a 32-bit machine, and for some reason "hvm" assumes 64-bit. Could you run "virsh capabilities" on both ?

Revision history for this message
Diego Lalo (diego-lalo) wrote :
Download full text (4.8 KiB)

root@eucalyptus:~# virsh capabilities
<capabilities>

  <host>
    <uuid>c0c3001e-8c00-01db-14ac-00248c88a29d</uuid>
    <cpu>
      <arch>x86_64</arch>
      <model>Opteron_G2</model>
      <vendor>AMD</vendor>
      <topology sockets='1' cores='2' threads='1'/>
      <feature name='3dnowprefetch'/>
      <feature name='cr8legacy'/>
      <feature name='extapic'/>
      <feature name='cmp_legacy'/>
      <feature name='3dnow'/>
      <feature name='3dnowext'/>
      <feature name='fxsr_opt'/>
      <feature name='mmxext'/>
      <feature name='ht'/>
      <feature name='vme'/>
    </cpu>
    <migration_features>
      <live/>
      <uri_transports>
        <uri_transport>tcp</uri_transport>
      </uri_transports>
    </migration_features>
    <secmodel>
      <model>apparmor</model>
      <doi>0</doi>
    </secmodel>
  </host>

  <guest>
    <os_type>hvm</os_type>
    <arch name='i686'>
      <wordsize>32</wordsize>
      <emulator>/usr/bin/qemu</emulator>
      <machine>pc-0.14</machine>
      <machine canonical='pc-0.14'>pc</machine>
      <machine>pc-0.13</machine>
      <machine>pc-0.12</machine>
      <machine>pc-0.11</machine>
      <machine>pc-0.10</machine>
      <machine>isapc</machine>
      <domain type='qemu'>
      </domain>
    </arch>
    <features>
      <cpuselection/>
      <deviceboot/>
      <pae/>
      <nonpae/>
      <acpi default='on' toggle='yes'/>
      <apic default='on' toggle='no'/>
    </features>
  </guest>

  <guest>
    <os_type>hvm</os_type>
    <arch name='x86_64'>
      <wordsize>64</wordsize>
      <emulator>/usr/bin/qemu-system-x86_64</emulator>
      <machine>pc-0.14</machine>
      <machine canonical='pc-0.14'>pc</machine>
      <machine>pc-0.13</machine>
      <machine>pc-0.12</machine>
      <machine>pc-0.11</machine>
      <machine>pc-0.10</machine>
      <machine>isapc</machine>
      <domain type='qemu'>
      </domain>
    </arch>
    <features>
      <cpuselection/>
      <deviceboot/>
      <acpi default='on' toggle='yes'/>
      <apic default='on' toggle='no'/>
    </features>
  </guest>

</capabilities>

root@openstack-in-a-box-1rev87:~# virsh capabilities
<capabilities>

  <host>
    <uuid>8080001e-8c00-01c3-0f4c-00248c2e5088</uuid>
    <cpu>
      <arch>x86_64</arch>
      <model>Opteron_G3</model>
      <vendor>AMD</vendor>
      <topology sockets='1' cores='3' threads='1'/>
      <feature name='osvw'/>
      <feature name='3dnowprefetch'/>
      <feature name='cr8legacy'/>
      <feature name='extapic'/>
      <feature name='cmp_legacy'/>
      <feature name='3dnow'/>
      <feature name='3dnowext'/>
      <feature name='pdpe1gb'/>
      <feature name='fxsr_opt'/>
      <feature name='mmxext'/>
      <feature name='ht'/>
      <feature name='vme'/>
    </cpu>
    <migration_features>
      <live/>
      <uri_transports>
        <uri_transport>tcp</uri_transport>
      </uri_transports>
    </migration_features>
    <secmodel>
      <model>apparmor</model>
      <doi>0</doi>
    </secmodel>
  </host>

  <guest>
    <os_type>hvm</os_type>
    <arch name='i686'>
      <wordsize>32</wordsize>
      <emulator>/usr/bin/qemu</emulator>
      <machine>pc-0.14</machine>
      <machine canonical='...

Read more...

Revision history for this message
Thierry Carrez (ttx) wrote :

Now I'm very confused :)

Revision history for this message
Thierry Carrez (ttx) wrote :

...and I can't reproduce that -- do you reproduce on a pristine install ?

Revision history for this message
Thierry Carrez (ttx) wrote :

We cannot solve the issue you reported without more information. Could you please provide the requested information ?

Revision history for this message
Thierry Carrez (ttx) wrote :

This bug lacks the necessary information to effectively reproduce and fix it, therefore it has been closed. Feel free to reopen the bug by providing the requested information and set the bug status back to ''New''.

Changed in nova:
status: Incomplete → Invalid
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.