cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rohit Yadav (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-7674) Upgrade to 4.3.1 did not update broadcast_uri in networks table for basic zone type
Date Fri, 05 Dec 2014 14:15:12 GMT

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-7674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14235508#comment-14235508
] 

Rohit Yadav commented on CLOUDSTACK-7674:
-----------------------------------------

Is this issue fixed [~creategui]? I see that your vlan_id column issue works for you, what
is the issue related to broadcast_uri?

> Upgrade to 4.3.1 did not update broadcast_uri in networks table for basic zone type
> -----------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-7674
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7674
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Management Server, Upgrade
>    Affects Versions: 4.3.1
>         Environment: CS Manager on Ubuntu 12.04 from standard repo
> Hosts: XenServer 6.0.2
> Zone: Basic
> Network Offering: DefaultSharedNetworkOffering
>            Reporter: Carlos Reategui
>            Priority: Critical
>
> In previous versions, the broadcast_uri in the Networks table was NULL for Guest network
in a Basic Zone with a network offering of DefaultSharedNetworkOffering.  From 4.3.1 (maybe
4.3.0 too but not sure) it can not be NULL and must be set to "vlan://untagged".  The upgrade
scripts do not do this and therefore one is unable to create new instances.  
> I don't know if this affect other hypervisors besides XenServer.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message