cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Will Stevens (JIRA)" <j...@apache.org>
Subject [jira] [Issue Comment Deleted] (CLOUDSTACK-5697) multiple public ranges don't work with vxlan on KVM
Date Thu, 02 Jan 2014 16:30:51 GMT

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-5697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Will Stevens updated CLOUDSTACK-5697:
-------------------------------------

    Comment: was deleted

(was: I am not sure if it is related to this bug, but it seems like it might be.  

I am not able to deploy my environment with the 'untagged' vlan tag anymore.

Here is my devcloud config (I have been using this forever):
"ipranges": [
    {
        "startip": "192.168.80.100", 
        "endip": "192.168.80.199", 
        "netmask": "255.255.255.0", 
        "vlan": "untagged", 
        "gateway": "192.168.80.2"
    }
], 


The error when I try to deploy my server:
[DEBUG] Executing command line: python ../marvin/marvin/deployDataCenter.py -i devcloud.cfg
Traceback (most recent call last):
  File "../marvin/marvin/deployDataCenter.py", line 572, in <module>
    deploy.deploy()
  File "../marvin/marvin/deployDataCenter.py", line 556, in deploy
    self.createZones(self.config.zones)
  File "../marvin/marvin/deployDataCenter.py", line 428, in createZones
    zoneId)
  File "../marvin/marvin/deployDataCenter.py", line 167, in createVlanIpRanges
    self.apiClient.createVlanIpRange(vlanipcmd)
  File "/mnt/hgfs/palo_alto/cloudstack/tools/marvin/marvin/cloudstackAPI/cloudstackAPIClient.py",
line 871, in createVlanIpRange
    response = self.connection.marvinRequest(command, response_type=response, method=method)
  File "/mnt/hgfs/palo_alto/cloudstack/tools/marvin/marvin/cloudstackConnection.py", line
272, in marvinRequest
    response = jsonHelper.getResultObj(response.json(), response_type)
  File "/mnt/hgfs/palo_alto/cloudstack/tools/marvin/marvin/jsonHelper.py", line 148, in getResultObj
    raise cloudstackException.cloudstackAPIException(respname, errMsg)
cloudstackException.cloudstackAPIException: Execute cmd: createvlaniprange failed, due to:
errorCode: 431, errorText:Vlan id is required when add ip range to the public network

Should 'untagged' still a valid vlan option?)

> multiple public ranges don't work with vxlan on KVM
> ---------------------------------------------------
>
>                 Key: CLOUDSTACK-5697
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5697
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: KVM
>    Affects Versions: 4.3.0
>            Reporter: Marcus Sorensen
>            Assignee: Marcus Sorensen
>             Fix For: 4.3.0
>
>
> You can add multiple VLAN/VNI network ranges to your public traffic in cloudstack, these
don't work with VXLAN on KVM. In other words, only guest traffic type creates VNI interfaces
and bridges. Tested a solution and will push shortly.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Mime
View raw message