yahoo-eng-team team mailing list archive

[Eduardo Santos <1943631@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

If the hostname has dots, as in for example "devstack.localdomain", when
trying to create an instance, Neutron will fail with "Failed to bind
port".

Reproduced with the latest DevStack from master on top of Ubuntu Server
20.04.3 LTS with latest packages installed. Minimal installation, no
additional packages installed (only removed python3-simplejson and
python3-pyasn1-modules due to recent issues with those packages[1]).

I find this weird, because afaik TripleO uses FQDNs, so in theory
Neutron with OVN should break their CI (although I'm not sure if they
use OVN or Open vSwitch). I'm still not sure if this is on my end or
not, but I was able to reproduce this consistently, trying different
hostnames, trying the most minimal local.conf possible (setting only
passwords), so I decided to report it as a bug.

Steps to reproduce:
1. Set the system's hostname to something with at least one dot
2. Deploy DevStack
3. Create instance on any network
4. Inspect devstack@q-svc.service to see the error

Expected output:
Instance is created successfully

Actual output:
Instance enters error state and devstack@q-svc.service reports this: https://paste.openstack.org/show/809315/

Version:
DevStack from master
Ubuntu Server 20.04.3 LTS
OVN mechanism driver

Environment (local.conf): https://paste.openstack.org/show/809316/

Perceived severity: low

[1] https://bugs.launchpad.net/devstack/+bug/1871485

** Affects: neutron
     Importance: Undecided
         Status: New

** Description changed:

  If the hostname has dots, as in for example "devstack.localdomain", when
  trying to create an instance, Neutron will fail with "Failed to bind
  port".
  
  Reproduced with the latest DevStack from master on top of Ubuntu Server
  20.04.3 LTS with latest packages installed. Minimal installation, no
  additional packages installed (only removed python3-simplejson and
  python3-pyasn1-modules due to recent issues with those packages[1]).
  
  I find this weird, because afaik TripleO uses FQDNs, so in theory
  Neutron with OVN should break their CI (although I'm not sure if they
  use OVN or Open vSwitch). I'm still not sure if this is on my end or
  not, but I was able to reproduce this consistently, trying different
  hostnames, trying the most minimal local.conf possible (setting only
  passwords), so I decided to report it as a bug.
  
  Steps to reproduce:
  1. Set the system's hostname to something with at least one dot
  2. Deploy DevStack
  3. Create instance on any network
  4. Inspect devstack@q-svc.service to see the error
  
  Expected output:
  Instance is created successfully
  
  Actual output:
  Instance enters error state and devstack@q-svc.service reports this: https://paste.openstack.org/show/809315/
  
  Version:
  DevStack from master
  Ubuntu Server 20.04.3 LTS
  OVN mechanism driver
  
  Environment (local.conf): https://paste.openstack.org/show/809316/
  
  Perceived severity: low
+ 
+ [1] https://bugs.launchpad.net/devstack/+bug/1871485

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1943631

Title:
  Neutron with OVN fails to bind port if hostname has dots

Status in neutron:
  New

Bug description:
  If the hostname has dots, as in for example "devstack.localdomain",
  when trying to create an instance, Neutron will fail with "Failed to
  bind port".

  Reproduced with the latest DevStack from master on top of Ubuntu
  Server 20.04.3 LTS with latest packages installed. Minimal
  installation, no additional packages installed (only removed
  python3-simplejson and python3-pyasn1-modules due to recent issues
  with those packages[1]).

  I find this weird, because afaik TripleO uses FQDNs, so in theory
  Neutron with OVN should break their CI (although I'm not sure if they
  use OVN or Open vSwitch). I'm still not sure if this is on my end or
  not, but I was able to reproduce this consistently, trying different
  hostnames, trying the most minimal local.conf possible (setting only
  passwords), so I decided to report it as a bug.

  Steps to reproduce:
  1. Set the system's hostname to something with at least one dot
  2. Deploy DevStack
  3. Create instance on any network
  4. Inspect devstack@q-svc.service to see the error

  Expected output:
  Instance is created successfully

  Actual output:
  Instance enters error state and devstack@q-svc.service reports this: https://paste.openstack.org/show/809315/

  Version:
  DevStack from master
  Ubuntu Server 20.04.3 LTS
  OVN mechanism driver

  Environment (local.conf): https://paste.openstack.org/show/809316/

  Perceived severity: low

  [1] https://bugs.launchpad.net/devstack/+bug/1871485

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1943631/+subscriptions