cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rohit Yadav (JIRA)" <>
Subject [jira] [Resolved] (CLOUDSTACK-3671) Set Host, Management Network and Storage Network Properly when there are multiple interfaces
Date Fri, 08 Aug 2014 09:29:14 GMT


Rohit Yadav resolved CLOUDSTACK-3671.

    Resolution: Won't Fix

Hi Soheil, the values in db specifically 192.168.56.x comes only when you deploydb with the
devcloud profile (i.e. working with devcloud). There is a developer profile, developers are
encourage to put their developer-prefill.sql.override file for their environment specific

In case of multiple nics, CloudStack uses the pessimistic approach and picks the first one
that it finds, I understand the issue you're raising here but how do you propose we fix it?
Closing this by design (won't fix), if you've some idea let's reopen and fix it.

> Set Host, Management Network and Storage Network Properly when there are multiple interfaces
> --------------------------------------------------------------------------------------------
>                 Key: CLOUDSTACK-3671
>                 URL:
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Management Server
>    Affects Versions: 4.2.0
>            Reporter: Soheil Eizadi
>            Priority: Minor
>             Fix For: 4.4.0
> The behavior on CloudStack Management Server that has multiple interfaces is that is
does not set the values of following configuration parameter:
> host
> secstorage.allowed.internal.sites
> They get set to the default one that is in the database initialization (192.168.56.x),
which are bogus as they typically don't match any interfaces on the host and problem with
this behavior is that you don't get any errors but see second order problems. The typical
problem seen is with the SSVM being created but not being able to communicate back to the
Host at address.
> The workaround to this problem is to set the values of configuration values:
> host
> secstorage.allowed.internal.sites
> Restart your CSM and also delete the System VMs so they have the proper host information
when they are recreated.

This message was sent by Atlassian JIRA

View raw message