John Burwell created CLOUDSTACK-660:
---------------------------------------
Summary: Network Traffic Labels are not functional in Marvin
Key: CLOUDSTACK-660
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-660
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Components: Test Tools
Affects Versions: 4.1.0
Environment: devcloud
Reporter: John Burwell
Priority: Blocker
When attempting to configure traffic labels in a Marvin configuration file, the
following error occurs:
Traceback (most recent call last):
File
"/Users/jburwell/.homebrew/Cellar/python/2.7.3/Frameworks/Python.framework/Versions/2.7/lib/python2.7/runpy.py",
line 162, in _run_module_as_main
"__main__", fname, loader, pkg_name)
File
"/Users/jburwell/.homebrew/Cellar/python/2.7.3/Frameworks/Python.framework/Versions/2.7/lib/python2.7/runpy.py",
line 72, in _run_code
exec code in run_globals
File
"/Users/jburwell/.virtualenvs/cloudstack/lib/python2.7/site-packages/marvin/deployAndRun.py",
line 47, in <module>
deploy.deploy()
File
"/Users/jburwell/.virtualenvs/cloudstack/lib/python2.7/site-packages/marvin/deployDataCenter.py",
line 425, in deploy
self.createZones(self.config.zones)
File
"/Users/jburwell/.virtualenvs/cloudstack/lib/python2.7/site-packages/marvin/deployDataCenter.py",
line 290, in createZones
phynetwrk = self.createPhysicalNetwork(pnet, zoneId)
File
"/Users/jburwell/.virtualenvs/cloudstack/lib/python2.7/site-packages/marvin/deployDataCenter.py",
line 173, in createPhysicalNetwork
self.addTrafficTypes(phynetwrk.id, net.traffictypes)
File
"/Users/jburwell/.virtualenvs/cloudstack/lib/python2.7/site-packages/marvin/deployDataCenter.py",
line 255, in addTrafficTypes
[self.addTrafficType(physical_network_id, traffic_type) for traffic_type in
traffictypes]
File
"/Users/jburwell/.virtualenvs/cloudstack/lib/python2.7/site-packages/marvin/deployDataCenter.py",
line 261, in addTrafficType
if traffictype.labeldict:
TypeError: 'NoneType' object is not callable
Additionally, code inspection discovered that the KVM and XEN traffic labels
were logically switched -- causing the Xen traffic label to assigned KVM and
vice versa.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira