This test verifies that OVN writes some messages on neutron
server logs when an invalid dhcp option is provided at port creation or
update
The port is successfully created/updated (no API error response), but
the logs indicate the option has not really had any effect
Change-Id: I8b0d7da50b20542a5af1666131e9c2c98764537c
Create a server with a port using extra-dhcp-opts parameter and check
the opts provided are actually applied to the VM instance
Change-Id: I2670d1fe122bf6736eea4d17c0b360e02272e415
test_neutron_agents_are_alive only retried neutron agent list requests
when the error received was a ServiceUnavailable exception. With this
patch, the retry mechanism is extended to the more generic
NeutronClientException
We detected some faults tests failed because of a temporary 504 Gateway
Timeout error and this patch should fix that
Change-Id: I4709c7bc45dd806304fac74befb309261970ada6
It assumes that old OVN configuration will not have the two
agents we typically use to recognise OVN and OVS configurations
has OVS agent: -> is OVS (OSP 13 or OSP 16+)
has OVN agent: -> is OVN (OSP 16+)
has any agent: -> is OVN (OSP 13)
Change-Id: I2588ebe38aeb9e07026abe5585085335d377ea89
Since OVN driver was moved to the Neutron repo, sevice for
ovn-metadata-agent is called 'neutron-ovn-metadata-agent' instead of old
'networking-ovn-metadata-agent'.
This patch makes Tobiko faults tests aware of it so it can works fine
in both cases.
Change-Id: I961745f5610e3793bfb272451269259661498dc9
When we use devstack based environment, services like Nova or
Neutron are logging to the journalctl instead of files.
So we need to have som LogDigger class which will be able to parse
such logs in same way like log files.
This patch adds such class and also adds to the topology class
parameters which defines what LogDigger class should be used for
the topology and what are service names to log file names mappings.
Change-Id: Ice25bfa0cae60dc2b5402e59f549e2287808ba87
Nova should update neutron in case port is attached to the instance
that has been booted recently. We should see the log with server id
and port id on one of the controller nodes.
Change-Id: Id0b0a10cf83ee8d2173dd25b7417f6f8f96af3ac
Test is destroying physical bridges on the node where router is
hosted so that floating IP shouldn't work at all.
Then it creates bridges again and checks if neutron-ovs-agent
was able to properly recover from that and FIP will work again.
Unfortunatelly this test can't work in e.g. devstack based u/s jobs
as there is additional bridge br-infra which provides connection between
nodes and this br-infra bridge is connected with br-ex by patch port.
When tobiko deletes br-ex and creates it again, there is this patch port
to br-infra missing and test is failing alwasy.
Test should works fine on deployments based on TripleO.
Change-Id: I125285f5f8abd2b2a285a7e46c954d6180d3ec32
This new test case checks if dnsmasq process spawned for network
works fine when neutron-dhcp-agent is stopped and than started again.
Dnsmasq process should be running fine for all this time and should
not change its PID.
Change-Id: Iad7317761830d6dc07a84bce07a0437ca7e9d602
Esternal network ID is stored in a Heat stack to keep the same network
ID for later test case executions.
Remove logic to found for looking for an external network from
DevStack plugin.
Change-Id: Ic7fe03324f4f328488988435530e127cedfab781
This also fixes handling of unique parameter in below functions:
- find_network
- find_port
- find_subnet
Rename wrapper of neutron 'list_l3_agent_hosting_routers'
Neutron client method with the same name.
Add 'find_l3_agent_hosting_router' function
Change-Id: I03a4a4351ec349eb818861d3f43fc075cb6537d9
This patch adds basic tests for router, like:
* test if router's internal IPv4 address is reachable from VM,
* test if router's internal IPv6 address is reachable from VM,
* test if external gateway IP address is reachable from VM,
* test if router is scheduled on proper number of L3 agents (if
agents scheduler extension is available)
* test if qrouter- namespaces are created properly on hosts where
router is scheduled (if agents scheduler extension is available)
To make those tests, additional method for neutron client is added to
list l3 agents hosting given router.
Change-Id: I1ce358eb7a48c1343f626f6bee01d9b26f79473f
Federico Ressi