© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
(Get the code!)
I have created test case for verifying the bug. Please execute these test case once the fix is done.
Test case id: OPNST_Neutron Bug: neutron metadata- after adding a network port to a neutron router, static route is still sent to new VMs
Metric: 30 minutes
Test purpose: neutron metadata- after adding a network port to a neutron router, static route is still sent to new VMs
Configuration: An OpenStack environment with at least one controller (with keystone, glance), one compute node and one network node installed.
Test tool: tempest
References: Bug_ 1549860: neutron metadata- after adding a network port to a neutron router, static route is still sent to new VMs
Applicability: Test can be adding a network port to a neutron router, static route is still sent to new VMs
Pre-test conditions: Openstack should be installed and all the services up and running
Step Description:
1. Create an instance
2. set enable_
3. create n/w without no-gateway option
4. check the opts file in /var/lib/
5. create a router and attach the network which u have created in previous step to the router
6. check the opts file in /var/lib/
7. restart the dhcp-agent
Result:
1. User should be able to create an instance and the instance should be in active state
2. User should be able to set the value
3. User should be able to create a network
4. Opts file should have the network entry
5. User should be able to create the router and able to attach the n/w to the router
6. Entry should be removed from the opts file
7. Dhcp-agent restart should not have any impact
Test verdict: Test case pass only if the instance should communicate to the metadata through qrouter once the router added to the network