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

Carlos Reategui commented on CLOUDSTACK-7674:
---------------------------------------------

Not sure that will fix my problem.  My vlan table got updated properly by this 
code.  The problem was the networks table.

from my prior backup:
INSERT INTO `vlan` VALUES 
(1,'5ebc3075-2946-4be4-9e7a-f32a86e7edfc','untagged','172.30.45.1','255.255.255.0','172.30.45.100-172.30.45.174','DirectAttached',1,204,200,NULL,NULL,NULL);
after update:
INSERT INTO `vlan` VALUES 
(1,'5ebc3075-2946-4be4-9e7a-f32a86e7edfc','vlan://untagged','172.30.45.1','255.255.255.0','172.30.45.100-172.30.45.174','DirectAttached',1,204,200,NULL,NULL,NULL);

As you can see the vlan_id got updated properly.

The problem for me was that the broadcast_uri for the guest network in the 
`networks` table stayed NULL.


> 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)

Reply via email to