yahoo-eng-team team mailing list archive

[Ian Wienand <iwienand@xxxxxxxxxx>]

Public bug reported:

Right now, centos7+neutron fails in tempest due to not setting netfilter
to run on bridges.  I have a review out for that [1]

However, correctly enabling these settings leads to two further tempest
failures

 tempest.scenario.test_network_v6.TestGettingAddress.test_dhcp6_stateless_from_os [79.318876s] ... FAILED
 tempest.scenario.test_network_v6.TestGettingAddress.test_slaac_from_os [70.714588s] ... FAILED

The failure is a lack of ipv6 communication

  tempest_lib.exceptions.SSHExecCommandFailed: Command 'ping6 -c1 -w1
-s56 2003::f816:3eff:fe6d:bd04', exit status: 1, Error:

I have two runs just executing these tests:

  * fail with net.bridge.bridge-nf-call-ip6tables=1 ->
         http://logs.openstack.org/89/179689/16/check/check-tempest-dsvm-centos7/8d6835c/
  * pass with net.bridge.bridge-nf-call-ip6tables=0 ->
         http://logs.openstack.org/89/179689/17/check/check-tempest-dsvm-centos7/dc97d29/

However, if I disable firewalld, this starts working
(http://logs.openstack.org/89/179689/21/check/check-tempest-dsvm-
centos7/530c356/)

I note that RDO, redhat's own deployment method, disables firewalld,
because it uses [2].  So I don't really expect this is high on anyone's
priority list, but that's where the logs are if we want to dig into this

[1] https://review.openstack.org/180867
[2] https://github.com/redhat-openstack/openstack-puppet-modules/blob/master/firewall/manifests/linux/redhat.pp#L27

** Affects: neutron
     Importance: Undecided
         Status: New

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

Title:
  centos7 + firewalld leads to tempest ipv6 failures

Status in OpenStack Neutron (virtual network service):
  New

Bug description:
  Right now, centos7+neutron fails in tempest due to not setting
  netfilter to run on bridges.  I have a review out for that [1]

  However, correctly enabling these settings leads to two further
  tempest failures

   tempest.scenario.test_network_v6.TestGettingAddress.test_dhcp6_stateless_from_os [79.318876s] ... FAILED
   tempest.scenario.test_network_v6.TestGettingAddress.test_slaac_from_os [70.714588s] ... FAILED

  The failure is a lack of ipv6 communication

    tempest_lib.exceptions.SSHExecCommandFailed: Command 'ping6 -c1 -w1
  -s56 2003::f816:3eff:fe6d:bd04', exit status: 1, Error:

  I have two runs just executing these tests:

    * fail with net.bridge.bridge-nf-call-ip6tables=1 ->
           http://logs.openstack.org/89/179689/16/check/check-tempest-dsvm-centos7/8d6835c/
    * pass with net.bridge.bridge-nf-call-ip6tables=0 ->
           http://logs.openstack.org/89/179689/17/check/check-tempest-dsvm-centos7/dc97d29/

  However, if I disable firewalld, this starts working
  (http://logs.openstack.org/89/179689/21/check/check-tempest-dsvm-
  centos7/530c356/)

  I note that RDO, redhat's own deployment method, disables firewalld,
  because it uses [2].  So I don't really expect this is high on
  anyone's priority list, but that's where the logs are if we want to
  dig into this

  [1] https://review.openstack.org/180867
  [2] https://github.com/redhat-openstack/openstack-puppet-modules/blob/master/firewall/manifests/linux/redhat.pp#L27

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