Ask Your Question
0

Network interface could not be raised for external network of vlan/flat type

asked 2019-05-11 07:01:49 -0500

marcus.frenkel gravatar image

updated 2019-05-12 17:05:42 -0500

I installed Openstack on Ubuntu Server 18.04.2 LTS following the official manual for Queens. The network service is configured for Self-service networks. My setup involves one controller and one compute node, each with two network interfaces, one used as management and the other as provider interface. I use horizon for configuration.

What I need is to have public fixed IPs assigned to instances, allowing them to have Internet connectivity through gateway set on the external physical network. I also need public floating IPs for some instances, in addition to the public fixed IPs. I do not need private IPs/network for projects/instances. The reason why I decided for the Self-service network option is to benefit from the floating IPs feature.

The last physical switch port facing the provider interface on the compute node is configured as access (not trunk).

I created a network in the Admin section, with these parameters:

  • Project: Test Project
  • Provider Network Type: flat
  • Physical Network: provider
  • Enable Admin State: checked
  • Shared: checked
  • External Network: checked
  • Create Subnet: checked
  • Network Address: X.X.X.X/24
  • Gateway IP: The gateway IP set on external physical router
  • Enable DHCP: checked
  • DNS Name Servers: Y.Y.Y.Y

I created an image with official Debian cloud image for Openstack, specifically this one.

I launched an instance with above network and image. The problem is that the network interface could not be raised. From the log: Starting Raise network interfaces... A start job is running for Raise network interfaces (30s / 5min 1s)

The same issue happens if I create a network of type "vlan", using specific VLAN tag (Segmentation ID), as well as using trunk port type with the VLAN tag passed on the physical switch port facing the provider interface on the compute node.

However, if I create the network from the project section, in which case there is no option to select "Provider Network Type" and "Physical Network", then when I boot the instance with this network and image specified above the interface is raised and a fixed IP and route to the gateway is setup in debian. There is no connectivity to external network (Internet) with this setup though, because the network is not setup as external, but I did it just to test if the interface will be raised.

Any help?

edit retag flag offensive close merge delete

1 answer

Sort by ยป oldest newest most voted
0

answered 2019-05-12 15:28:21 -0500

marcus.frenkel gravatar image

updated 2019-05-12 17:05:00 -0500

I found a solution in a post on ask.cloudbase.it. The controller node was installed in Hyper-V VM. I enabled MAC address spoofing in Hyper-V VM settings for the second interface which is the provider interface for the controller node. Without this option enabled, there was no communication between the provider interfaces on the controller and compute node, preventing DHCP agent to deliver IP for the instance.

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools

2 followers

Stats

Asked: 2019-05-11 07:01:49 -0500

Seen: 47 times

Last updated: May 12