Public bug reported:
The `nova network-create` is *silently* ignoring the --bridge when using
the VlanManager. The bridge name is hardcoded to "br%s" % vlan.
https://github.com/openstack/nova/blob/stable/juno/nova/network/manager.py#L1361
[root@jhenner-vmware ~(keystone_admin)]# nova network-cre
Public bug reported:
Quite often, the tempest ssh tests fails, probably because of some
problem with loading user-data served on the network. My theory is that
the ssh is started after cloud-init in cirros, and this causes
connection reset.
I have found that many logs in the gat exhibits similar
Adding log with TRACE
augeas-libs.x86_641.1.0-12.el7 @rhel7-released
openstack-nova-api.noarch 2014.1.2-1.el7ost @puddle
openstack-nova-common.noarch 2014.1.2-1.el7ost @puddle
openstack-nova-compute.noarch
** Also affects: oslo.vmware
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1367741
Title:
The `fault` should be included to
Public bug reported:
... because it can contain important information. For example:
(TaskInfo){
key = "task-34928"
task =
(task){
value = "task-34928"
_type = "Task"
}
description =
(LocalizableMessage){
key = "com.vmware.vim.vpxd.vpx.vmprov
Public bug reported:
This may be a DUP of #1240355 but I am not sure.
I have three hosts which all are connected to the same shared NFS
datastore and glance configured to use it. I am uploading the an and
then try to download, but download returns empty string and there is an
ERROR in the glance/
Public bug reported:
I have python-glance-2014.1.2-1.el7ost.noarch
when configuring
default_store=vmware_datastore
known_stores = glance.store.vmware_datastore.Store
vmware_server_host = 10.34.69.76
vmware_server_username=root
vmware_server_password=qum5net
vmware_datacenter_path="New Datacente
Public bug reported:
tempest.api.compute.floating_ips.test_floating_ips_actions.FloatingIPsTestXML.test_associate_disassociate_floating_ip
is failing because it failed when updating ebtables
** Affects: nova
Importance: Undecided
Status: New
--
You received this bug notification b
Public bug reported:
in the libvirt log:
qemu-kvm: -drive
file=/var/lib/nova/instances/a2f907b5-6fe2-402a-86fe-81c44058a929/disk,if=none,id=drive-virtio-disk0,format=qcow2,cache=none:
could not open disk image
/var/lib/nova/instances/a2f907b5-6fe2-402a-86fe-81c44058a929/disk: Could not
open fi
Public bug reported:
# nova list --name \*
ERROR: The server has either erred or is incapable of performing the requested
operation. (HTTP 500) (Request-ID: req-e399bee0-2491-4e4a-9197-944b19c86075)
** Affects: nova
Importance: Undecided
Status: New
** Attachment added: "log"
h
This also happens with Neutron
** Changed in: nova
Status: Invalid => New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/955792
Title:
No public IP addresses lis
Public bug reported:
1) Glance is hiding error messages when used with --location. If the URL
returns HTTP 404, glance is just ignoring it.
2) Reply to GET request to http://CENSORED:9292/v1/images/2e34a168-62ca-
412d-84bb-852fcaf2a391 contains header:
location: http://CENSORED:9292/v1/images
Public bug reported:
# glance image-create --name temporary_test --id
0bfbc34b-0ec8-4802-8f61-f45f0613fb54
# glance member-create --can-share 0bfbc34b-0ec8-4802-8f61-f45f0613fb54 'I do
not exist!'
# echo $?
0
# glance image-delete 0bfbc34b-0ec8-4802-8f61-f45f0613fb54
I expected it to return som
Public bug reported:
Description of problem:
In the nova conf, there is:
# VNC starting port (integer value)
#vnc_port=5900
Which means the default value is 5900, but it is not so. with this
configuration, vmware VMs seems to have ports >=9100
Version-Release number of selected component (if a
Public bug reported:
Checking the code, nova scrub should disassociate the network associated
with the given tenant, but it fails to do so. There is no error in log.
openstack-nova-api.noarch 2013.2.1-1.el6ost
@puddle
openstack-nova-cert.noarch
Public bug reported:
when using
compute_driver=vmwareapi.VMwareVCDriver
volume_driver=cinder.volume.drivers.vmware.vmdk.VMwareVcVmdkDriver
after creating a VM and cinder volume and attaching it:
nova boot --image cirros-0.3.1-x86_64-disk.vmdk --flavor m1.tiny foo
cinder create --display-name baz
Public bug reported:
Issuing
[root@jhenner-node ~(keystone_admin)]# nova secgroup-add-rule default tcp 33
33 0.0.0.0/0
+-+---+-+---+--+
| IP Protocol | From Port | To Port | IP Range | Source Group |
+-+---+-+--
Public bug reported:
nova rescue of VM on vmWare will create a additional VM ($ORIGINAL_ID-
rescue), but after that, the original VM has status ACTIVE. This leads
to
[root@jhenner-node ~(keystone_admin)]# nova unrescue foo
ERROR: Cannot 'unrescue' while instance is in vm_state stopped (HTTP 409)
Public bug reported:
Description of problem:
The vmwareapi.VMwareVCDriver seems to not suport pausing a VM. Issuing the nova
pause results in ERROR in log. It probably should not be rated as ERROR but as
WARNING.
Version-Release number of selected component (if applicable):
openstack-nova-compu
19 matches
Mail list logo
