Hi Ilya,
-----Original Message-----
From: Francois Gaudreault [mailto:[email protected]]
Sent: Thursday, March 28, 2013 11:59 AM
To: [email protected]
Subject: Couple VMWare Issues with 4.1
Hi,
I have other small issues with VMWare and 4.1. Let me know if I should open
tickets for those.
1 - VM Statistics
We keep getting those errors in the log:
INFO [agent.manager.AgentManagerImpl] (AgentTaskPool-6:) Agent is
determined to be up and running ERROR
[vmware.resource.VmwareResource] (DirectAgent-383:yul01vi13.ops.dot)
Unable to execute GetVmStatsCommand due to : Exception:
java.lang.NullPointerException
Message: null
java.lang.NullPointerException
WARN [cloud.vm.UserVmManagerImpl] (StatsCollector-2:) Unable to obtain
VM statistics.
ERROR [vmware.resource.VmwareResource] (DirectAgent-
67:yul01vi12.ops.dot) Unable to execute GetVmStatsCommand due to :
Exception: java.lang.NullPointerException
Message: null
java.lang.NullPointerException
WARN [cloud.vm.UserVmManagerImpl] (StatsCollector-2:) Unable to obtain
VM statistics.
We are not sure tho if it's related to permissions, but the user sees every
performance metrics on vSphere, so I doubt it.
How often do you get this error? I did see this once in my 4.1 env on the
startup, but I haven't seen it again.
One other thing to note, you cant change VM names, CS strictly binds to VM
names.
Quite often actually. Every time we try to access VM stats from the UI,
or at regular intervals (internal recurrent task maybe?).
2 - Public VLAN created on vSwitch0 even if we tell to use vSwitch2.
For some reason, CS creates a tagged port-group on the vSwitch0 for the
public interface of the VR even if we told CS to use vSwitch2. In fact, CS
creates and uses the public port-group on the vSwitch2... So why it creates
an unused port-group on vSwitch0? See attached screenshot.
Preparing NIC device on network cloud.public.142.0.1-vSwitch0 INFO
[vmware.resource.VmwareResource] (DirectAgent-47:yul01vi13.ops.dot)
Prepare NIC device based on NicTO: {"deviceId":4,"networkRateMbps":-
1,"defaultNic":false,"ip":"0.0.0.0","netmask":"255.255.255.255","gateway":"1
0.0.142.1","mac":"02:00:3b:5a:00:02","dns1":"10.0.31.24","dns2":"10.0.31.28",
"broadcastType":"Vlan","type":"Public","broadcastUri":"vlan://142","isolatio
nUri":"vlan://142","isSecurityGroupEnabled":false}
INFO [vmware.resource.VmwareResource] (DirectAgent-
47:yul01vi13.ops.dot) Prepare network on vSwitch: P[vSwitch0:untagged]
with name prefix: cloud.public INFO [vmware.mo.HypervisorHostHelper]
(DirectAgent-47:yul01vi13.ops.dot) Network cloud.public.142.0.1-vSwitch0 is
ready on vSwitch vSwitch0 INFO [vmware.mo.HypervisorHostHelper]
(DirectAgent-47:yul01vi13.ops.dot) Network cloud.public.142.0.1-vSwitch0 is
ready on vSwitch vSwitch0 INFO [vmware.resource.VmwareResource]
(DirectAgent-47:yul01vi13.ops.dot) Preparing NIC device on network
cloud.public.142.0.1-vSwitch0
This is a bug, if I'm not mistaken I've seen some reference in source code to
try to use vSwitch0 as default, unless another vSwitch is defined (in your
case, its vSwitch2).
Specifically, the create-schema.sql file and VmwareManagerImpl.java have hardcoded references of
vSwitch0 - that technically should be overridden by "vmware traffic label" defined in
"physical network" settings. Something with a logic there did not go smooth and hence
additional creation of unused port-group on vSwitch0.
Please file the bug and include the content above.
Will do.
Thanks!
--
Francois Gaudreault
Architecte de Solution Cloud | Cloud Solutions Architect
[email protected]
514-629-6775
- - -
CloudOps
420 rue Guy
Montréal QC H3J 1S6
www.cloudops.com
@CloudOps_
