cloudstack-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sebastian Gomez <>
Subject Re: some issues after upgrade cloudstack to 4.9.2
Date Thu, 22 Jun 2017 21:17:10 GMT
The problem over upload from local and the problem with the console proxy
were not a problem with cloudstack, was a problem of our network

As I told before, we have public IPs and private IPs routed into the
backbone network, so used as "public" IPs also, both mixed.
The systemvm since 4.6 has a script /etc/init.d/cloud-early-config which
now creates routes for private networks (10.x, 172.16.x, 192.168.x) if the
public network is really public. In our case it was a problem, because the
public network for the cloud service is really public, but our
WorkingStations have private IPs (10.x). In this case, when the console
proxy starts, there is a new route for 10.x network over the management
interface, and the connection can't be stablished. The traffic from our
stations comes from public interface and return through the management
network (and is not routed).

We solved the problem tunning this script, commenting the line "ip route
add via $LOCAL_GW".

About the problem with upload from local, the reason is that we have not
well passed the certificates on our PRE environment, where we have tested
the upgrade.

Finally we have successfully executed the upgrade process, but with more
work than just the public process... But really, if everything were easy,
life would be boring!


Sebastián Gómez

On Thu, May 25, 2017 at 11:14 AM, Marc Poll Garcia <> wrote:

> Hi all,
> we have just upgraded our cloud environment based on Cloudstack 4.5.2 to
> 4.9.2 and we're expriencing some issues after this.
> Our setup is the following one:
> - 1 x cloudstack managment server
> - 1 x bbdd server cloudstack database on it
> - 2 x Vmware Hipervisors (hosts)
> I'm performing a list of tests:
> *- Sometimes, and randomly console from instances does not load.*
> *- Not possible to upload template from local.*
> We see the following on log:
> 2017-05-25 09:00:31,665 ERROR [c.c.s.ImageStoreUploadMonitorImpl]
> (Upload-Monitor-1:ctx-0b3bf6e9) (logid:e9c82a0f) *Template
> b87459ac-8fbe-4b34-ae25-21235c3fcd1d failed to upload due to operation
> timed out*
> 2017-05-25 09:02:18,265 ERROR [c.c.c.ClusterServiceServletContainer]
> (Thread-11:null) (logid:) *Unexpected exception *
> 2017-05-25 09:03:35,940 ERROR [c.c.c.ClusterManagerImpl] (main:null)
> (logid:) *Unable to ping management server at
> <> due to ConnectException*
> Why is it happening?
> It does not happen on our old 4.5.2 version.
> Is there any way to fix it? changing any global parameter or permissions
> issue?
> We need a clue with that because if affecting to our production
> environment.
> Thanks in advance.
> Kind regards.

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message