QA:Testcase launch an instance on OpenStack

From FedoraProject

(Difference between revisions)
Jump to: navigation, search
(Created page with "{{QA/Test_Case |description=A brief description of the functionality being tested. |setup=Optionally include information on preparing the test environment |actions= Be as specifi...")
 
m
 
(28 intermediate revisions by 6 users not shown)
Line 1: Line 1:
 
{{QA/Test_Case
 
{{QA/Test_Case
|description=A brief description of the functionality being tested.
+
|description=Launch an instance on OpenStack.
 
|setup=Optionally include information on preparing the test environment
 
|setup=Optionally include information on preparing the test environment
 +
# Follow [[QA:Testcase_register_images_with_OpenStack]]
 +
 +
 
|actions=
 
|actions=
Be as specific as required for the target audience.  
+
 
# Start here ...
+
Launch an instance of one of the images downloaded and registered in the previous test case.
# Next do this ...
+
$> . ./keystonerc
# Finally click that
+
$> <nowiki>nova boot --image $(nova image-list | grep ami-tty | awk '{print $2}') --flavor 1 --key_name nova_key testvm</nowiki>
 +
 
 
|results=
 
|results=
The following must be true to consider this a successful test run. Be brief ... but explicit.  
+
 
# Step #1 completes without error
+
Verify that the instance has started.
# The system boots into runlevel 5
+
 
# Program completes wth exit code 0
+
 
 +
$> nova list
 +
+--------------------------------------+----------+--------+------------------+
 +
<nowiki>|                  ID                  |  Name  | Status |    Networks    |</nowiki>
 +
+--------------------------------------+----------+--------+------------------+
 +
<nowiki>| a47a424a-014b-4b81-97e6-b34d31b5589d | Server 1 | ACTIVE | testnet=10.0.0.2 |</nowiki>
 +
+--------------------------------------+----------+--------+------------------+
 +
 
 +
 
 +
It may take a while to transition from the BUILD to the ACTIVE state, as reported by 'nova list'.  
 +
 
 +
If the instance goes into the ERROR state, then check the nova-compute logs for errors:
 +
 
 +
$> grep ERROR /var/log/nova/compute.log
 +
 
 +
What might help is to restart the nova scheduler with 'sudo systemctl restart openstack-nova-scheduler.service' and try again in case the scheduler reports an error in the logs.
 +
 
 +
Confirm the VM running with virsh:
 +
 
 +
$> sudo virsh list
 +
  Id Name                State
 +
----------------------------------
 +
  1 instance-00000001    running
 +
 
 +
Get console output and ensure instance is fully started
 +
$> nova console-log --length 100 <instanceid>
 +
 
 +
Try SSH-ing into the instance:
 +
 
 +
$> ssh -i nova_key.priv -o UserKnownHostsFile=/dev/null root@10.0.0.2
 +
 
 +
Check for new errors in the logs:
 +
$> grep -i error /var/log/nova/*.log
 +
 
 +
Notes:
 +
* We use <code>/dev/null</code> for known hosts because the fingerprints associated with these IPs will change when you start over with your testing; updating known hosts gets annoying
 +
* You've probably got a stale dnsmasq process around if you see:
 +
dnsmasq: failed to create listening socket for 10.0.0.1: Address already in use
 +
 
 
}}
 
}}
  
 
[[Category:OpenStack Test Cases]]
 
[[Category:OpenStack Test Cases]]
[[Category:Cloud SIG]]
 

Latest revision as of 18:32, 25 October 2012

Contents

Description

Launch an instance on OpenStack.

Setup

Optionally include information on preparing the test environment

  1. Follow QA:Testcase_register_images_with_OpenStack

How to test

Launch an instance of one of the images downloaded and registered in the previous test case.

$> . ./keystonerc
$> nova boot --image $(nova image-list | grep ami-tty | awk '{print $2}') --flavor 1 --key_name nova_key testvm

Expected Results

Verify that the instance has started.


$> nova list
+--------------------------------------+----------+--------+------------------+
|                  ID                  |   Name   | Status |     Networks     |
+--------------------------------------+----------+--------+------------------+
| a47a424a-014b-4b81-97e6-b34d31b5589d | Server 1 | ACTIVE | testnet=10.0.0.2 |
+--------------------------------------+----------+--------+------------------+


It may take a while to transition from the BUILD to the ACTIVE state, as reported by 'nova list'.

If the instance goes into the ERROR state, then check the nova-compute logs for errors:

$> grep ERROR /var/log/nova/compute.log

What might help is to restart the nova scheduler with 'sudo systemctl restart openstack-nova-scheduler.service' and try again in case the scheduler reports an error in the logs.

Confirm the VM running with virsh:

$> sudo virsh list
 Id Name                 State
----------------------------------
 1 instance-00000001    running

Get console output and ensure instance is fully started

$> nova console-log --length 100 <instanceid>

Try SSH-ing into the instance:

$> ssh -i nova_key.priv -o UserKnownHostsFile=/dev/null root@10.0.0.2

Check for new errors in the logs:

$> grep -i error /var/log/nova/*.log

Notes:

  • We use /dev/null for known hosts because the fingerprints associated with these IPs will change when you start over with your testing; updating known hosts gets annoying
  • You've probably got a stale dnsmasq process around if you see:
dnsmasq: failed to create listening socket for 10.0.0.1: Address already in use