Public bug reported:
This error happens intermittently, but always can be reproduced after
long run and have multiple vmware computer connect to the same vCenter
in our test environment:
2014-09-02 09:34:53.489 9439 ERROR nova.virt.vmwareapi.io_util [-] [Errno 32]
Broken pipe
2014-09-02 09:34:53
Public bug reported:
We are using non-administrator to connect the vCenter when start compute
service. In vCenter we defined a separate role (you can it in the
attachment) for this account and allow it to only access the cluster
that is used to provision VM and split with the management cluster.
Public bug reported:
Fail to boot a instance when using the nova-network, I got the error
message in log file
'InvalidVLANPortGroup: vSwitch which contains the port group
VS5_GUEST_SCODEV_G1_V231 is not associated with the desired physical
adapter. Expected vSwitch is vSwitch0, but the one associ
Public bug reported:
I am testing the vmware native driver of nova compute component.
My environment should be workable before I upgrade my vCenter and EXSi from 5.0
to 5.5.
After the upgrade, I found all the existing VMs boot from nova can not be
started in my vCenter with 'Operating system no
Public bug reported:
In order to manage the snapshot of vm in glance conveniently, we need know
which images in glance are captured from VM.
So we need add new property in glance metadata when create the vm snapshot, for
example: server_id = vm uuid. This new property will help to filter the ima
Public bug reported:
When try to create instance snapshot via 'nova image-create', I hint
following error in the nova log file:
2014-03-07 03:04:35.436 7213 DEBUG nova.virt.vmwareapi.vmware_images
[req-d82fb9c2-9325-43a4-814a-4ea1bae14c5c 8f4bfb793af946b6a25288456143e920
e4a913fb2d1e4a33a4acacc
6 matches
Mail list logo
