Public bug reported:
neutron.tests.tempest.scenario.test_dvr.NetworkDvrTest.test_vm_reachable_through_compute
[220.774590s] ... FAILED
neutron.tests.tempest.scenario.test_migration.NetworkMigrationFromDVRHA.test_from_dvr_ha_to_dvr
[319.845960s] ... FAILED
neutron.tests.tempest.scenario.test_migration.NetworkMigrationFromDVR.test_from_dvr_to_dvr_ha
[319.645897s] ... FAILED
neutron.tests.tempest.scenario.test_migration.NetworkMigrationFromDVRHA.test_from_dvr_ha_to_ha
[318.106647s] ... FAILED
neutron.tests.tempest.scenario.test_migration.NetworkMigrationFromDVR.test_from_dvr_to_ha
[318.342858s] ... FAILED
neutron.tests.tempest.scenario.test_migration.NetworkMigrationFromDVRHA.test_from_dvr_ha_to_legacy
[318.466020s] ... FAILED
neutron.tests.tempest.scenario.test_migration.NetworkMigrationFromDVR.test_from_dvr_to_legacy
[319.457491s] ... FAILED
neutron.tests.tempest.scenario.test_migration.NetworkMigrationFromHA.test_from_ha_to_dvr
[344.150677s] ... FAILED
neutron.tests.tempest.scenario.test_migration.NetworkMigrationFromLegacy.test_from_legacy_to_dvr
[339.829603s] ... FAILED
neutron.tests.tempest.scenario.test_migration.NetworkMigrationFromHA.test_from_ha_to_dvr_ha
[339.848078s] ... FAILED
The reason seems to be an inconsistency in these default config values:
enable_dvr = True
agent_mode = legacy
For consistency, either DVR should be disabled by default or the default
agent_mode should support DVR, so a default of dvr_snat would seem to be
the best solution.
** 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/1731857
Title:
DVR scenario tests fail in default deployment
Status in neutron:
New
Bug description:
neutron.tests.tempest.scenario.test_dvr.NetworkDvrTest.test_vm_reachable_through_compute
[220.774590s] ... FAILED
neutron.tests.tempest.scenario.test_migration.NetworkMigrationFromDVRHA.test_from_dvr_ha_to_dvr
[319.845960s] ... FAILED
neutron.tests.tempest.scenario.test_migration.NetworkMigrationFromDVR.test_from_dvr_to_dvr_ha
[319.645897s] ... FAILED
neutron.tests.tempest.scenario.test_migration.NetworkMigrationFromDVRHA.test_from_dvr_ha_to_ha
[318.106647s] ... FAILED
neutron.tests.tempest.scenario.test_migration.NetworkMigrationFromDVR.test_from_dvr_to_ha
[318.342858s] ... FAILED
neutron.tests.tempest.scenario.test_migration.NetworkMigrationFromDVRHA.test_from_dvr_ha_to_legacy
[318.466020s] ... FAILED
neutron.tests.tempest.scenario.test_migration.NetworkMigrationFromDVR.test_from_dvr_to_legacy
[319.457491s] ... FAILED
neutron.tests.tempest.scenario.test_migration.NetworkMigrationFromHA.test_from_ha_to_dvr
[344.150677s] ... FAILED
neutron.tests.tempest.scenario.test_migration.NetworkMigrationFromLegacy.test_from_legacy_to_dvr
[339.829603s] ... FAILED
neutron.tests.tempest.scenario.test_migration.NetworkMigrationFromHA.test_from_ha_to_dvr_ha
[339.848078s] ... FAILED
The reason seems to be an inconsistency in these default config
values:
enable_dvr = True
agent_mode = legacy
For consistency, either DVR should be disabled by default or the
default agent_mode should support DVR, so a default of dvr_snat would
seem to be the best solution.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1731857/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
