New Question

pilotbri's profile - activity

2015-11-14 00:24:21 +0200 received badge  Famous Question (source)
2015-09-28 06:04:04 +0200 received badge  Notable Question (source)
2015-09-27 03:31:28 +0200 received badge  Enthusiast
2015-09-26 03:22:42 +0200 commented question instances not getting network.

anyone? I'm kinda stuck.

2015-09-26 03:22:23 +0200 received badge  Popular Question (source)
2015-09-24 06:50:52 +0200 asked a question instances not getting network.

using latest download of v-magine, hyper-v windows server 2016 tech preview 3, neither Windows eval instance nor imported Ubuntu image are getting dhcp addresses

here is what I think is the relevant neutron log entries. I'm really new to Openstack so I'm not sure where to look next.

2015-09-23 21:34:41.515 672 INFO hyperv.neutron.hypervneutronagent [req-015bbdbb-ffec-4f82-839d-b2bc8ad25e11 ] Adding port 0155e112-af36-4386-8080-793dd6aed36e 2015-09-23 21:34:41.515 672 INFO hyperv.neutron.hypervneutronagent [req-015bbdbb-ffec-4f82-839d-b2bc8ad25e11 ] Port 0155e112-af36-4386-8080-793dd6aed36e updated. Details: {u'profile': {}, u'allowedaddresspairs': [], u'adminstateup': True, u'networkid': u'd8021f82-622b-4568-a7c2-656dd92572d3', u'segmentationid': 505, u'deviceowner': u'compute:nova', u'physicalnetwork': u'physnet1', u'macaddress': u'fa:16:3e:32:2b:4d', u'device': u'0155e112-af36-4386-8080-793dd6aed36e', u'portsecurityenabled': True, u'portid': u'0155e112-af36-4386-8080-793dd6aed36e', u'fixedips': [{u'subnetid': u'72dca1ff-2b9b-4e81-9e75-3557e0caa45d', u'ipaddress': u'172.17.15.103'}], u'networktype': u'vlan'} 2015-09-23 21:34:42.967 672 ERROR hyperv.neutron.hypervneutronagent [req-015bbdbb-ffec-4f82-839d-b2bc8ad25e11 ] Error in agent event loop 2015-09-23 21:34:42.967 672 TRACE hyperv.neutron.hypervneutronagent Traceback (most recent call last): 2015-09-23 21:34:42.967 672 TRACE hyperv.neutron.hypervneutronagent File "C:\Program Files (x86)\Cloudbase Solutions\OpenStack\Nova\Python27\lib\site-packages\hyperv\neutron\hypervneutronagent.py", line 356, in daemonloop 2015-09-23 21:34:42.967 672 TRACE hyperv.neutron.hypervneutronagent sync = self.processnetworkports(portinfo) 2015-09-23 21:34:42.967 672 TRACE hyperv.neutron.hypervneutronagent File "C:\Program Files (x86)\Cloudbase Solutions\OpenStack\Nova\Python27\lib\site-packages\hyperv\neutron\hypervneutronagent.py", line 332, in _processnetworkports 2015-09-23 21:34:42.967 672 TRACE hyperv.neutron.hypervneutronagent resynca = self.treatdevicesadded(portinfo['added']) 2015-09-23 21:34:42.967 672 TRACE hyperv.neutron.hypervneutronagent File "C:\Program Files (x86)\Cloudbase Solutions\OpenStack\Nova\Python27\lib\site-packages\hyperv\neutron\hypervneutronagent.py", line 296, in treatdevicesadded 2015-09-23 21:34:42.967 672 TRACE hyperv.neutron.hypervneutronagent devicedetails['adminstateup']) 2015-09-23 21:34:42.967 672 TRACE hyperv.neutron.hypervneutronagent File "C:\Program Files (x86)\Cloudbase Solutions\OpenStack\Nova\Python27\lib\site-packages\hyperv\neutron\hypervneutronagent.py", line 264, in treatvifport 2015-09-23 21:34:42.967 672 TRACE hyperv.neutron.hypervneutronagent physicalnetwork, segmentationid) 2015-09-23 21:34:42.967 672 TRACE hyperv.neutron.hypervneutronagent File "C:\Program Files (x86)\Cloudbase Solutions\OpenStack\Nova\Python27\lib\site-packages\hyperv\neutron\hypervneutronagent.py", line 195, in _portbound 2015-09-23 21:34:42.967 672 TRACE hyperv.neutron.hypervneutronagent self.utils.connectvnictovswitch(map['vswitchname'], portid) 2015-09-23 21:34:42.967 672 TRACE hyperv.neutron.hypervneutronagent File "C:\Program Files (x86)\Cloudbase Solutions\OpenStack\Nova\Python27\lib\site-packages\hyperv\neutron\utilsv2.py", line 86, in connect ... (more)

2015-09-23 20:53:10 +0200 commented answer v-magine hanging on 2016 tech preview 3

my instances were not coming up with network interfaces. I believe its because my vswitch was tagged, so I've rebuilt using v-magine and I'll test tonight.

2015-09-23 07:12:28 +0200 answered a question v-magine hanging on 2016 tech preview 3

I just downloaded v-magine this evening and it looks like the problem is fixed. Now to tackle the networking issues.