[
https://issues.apache.org/jira/browse/CLOUDSTACK-9649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15772775#comment-15772775
]
ASF subversion and git services commented on CLOUDSTACK-9649:
-------------------------------------------------------------
Commit 20986ba51215b75c67b0c4035d55a27c3de313d1 in cloudstack's branch
refs/heads/4.9 from [~rohit.ya...@shapeblue.com]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=20986ba ]
Merge pull request #1854 from shapeblue/4.9-multiplex-testing
4.9 multiplex testingThis merges several PRs in this PR, this is for speeding
up test efforts.
* pr/1854:
CLOUDSTACK-9688: Fix VR smoke test failure in vpc_vpn
CLOUDSTACK-9688: Fix failing test_volumes on centos7/kvm
CLOUDSTACK-9676 Start instance fails after reverting to a VM snapshot, when
there are child VM snapshots
CLOUDSTACK-9612: Fixed issue in restarting redundant network with cleanup Rvr
Network with cleanup which is updated from the isolated network is failed.
Corrected the column name string issue.
CLOUDSTACK-9676 Start instance fails after reverting to a VM snapshot, when
there are child VM snapshots
CLOUDSTACK-9673 Exception occured while creating the CPVM in the VmWare Setup
over standard vSwitches
CLOUDSTACK-9617: Fixed enabling remote access after PF or LB configured on
vpn tcp ports
CLOUDSTACK-9615: Fixed applying ingress rules without ports
CLOUDSTACK-9639: Unable to create shared network with vLan isolation
CLOUDSTACK-9597: Should not fetch resource count for removed entity
CLOUDSTACK-9649: In the management server log there is an error related to
0.0.0.0 IP address
Signed-off-by: Rohit Yadav <rohit.ya...@shapeblue.com>
> In the management server log there is an error related to 0.0.0.0 IP address
> ----------------------------------------------------------------------------
>
> Key: CLOUDSTACK-9649
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9649
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Management Server, VMware
> Affects Versions: 4.9.0
> Reporter: Sudhansu Sahu
> Assignee: Sudhansu Sahu
>
> ISSUE
> ============
> In the management server log there is an error
> 2016-10-01 00:07:31,670 ERROR [c.c.h.v.r.VmwareResource]
> (DirectAgent-417:ctx-e8c89b3f strmg-esx-01, cmd: GetRouterAlertsCommand)
> (logid:7beb3819) Command failed due to Exception: java.io.IOException
> Message: There was a problem while connecting to 0.0.0.0:3922
> In case of basic zone and VMWare ESXi host, the NIC 2 always gets 0.0.0.0 as
> IP address. Looks like we are generating an error for connecting through this
> invalid IP.
> 2016-10-01 04:37:31,680 DEBUG [c.c.a.m.AgentManagerImpl]
> (RouterStatusMonitor-1:ctx-8880f9c8) (logid:946838b8) Details from executing
> class com.cloud.agent.api.routing.GetRouterAlertsCommand: Command failed due
> to Exception: java.io.IOException
> Message: There was a problem while connecting to 0.0.0.0:3922
> 2016-10-01 04:37:31,680 WARN [c.c.n.r.VirtualNetworkApplianceManagerImpl]
> (RouterStatusMonitor-1:ctx-8880f9c8) (logid:946838b8) Unable to get alerts
> from router r-4-VM Command failed due to Exception: java.io.IOException
> Message: There was a problem while connecting to 0.0.0.0:3922
> 2016-10-01 04:37:31,682 DEBUG [c.c.n.ExternalDeviceUsageManagerImpl]
> (ExternalNetworkMonitor-1:ctx-913c7bae) (logid:1b926a60) External devices
> stats collector is running...
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
