ABCDEFGHIJKLMNOPQRSTUVWXYZAAABACADAEAF
1
Req #Bug/error condition IDVersion(s)Component Level Fault Handling Cloud Level Failure HandlingLog FormatHow to Re-create the BugSubmitter's NameEmailIRC HandleSize of DeploymentExisting Bug Report Link
2
Project ComponentFault ClassFault TypeFault DescriptionComponent Reaction to FaultFailure SeverityPriorityPolicy for managing the Failure
3
One or more cloud controllers and nova-compute and swift-proxy nodes are down or degradedTushar Katarki
4
Neutron, NovaIP address not assigned to VMP1 - Critical (4 hrs.)
5
Which service Is down or not functioning P2 - Important (24 hrs.)ssh to the controller and compute nodes and 'ps aux|grep <service name>Tushar Katarki
6
nova-list does not show all the compute nodes in the listP2 - Important (24 hrs.)1. Ensure nova service is running on the node 2. status nova-compute 3. # grep AMQP /var/log/nova/nova-compute shows an entry that nova is connected to an AMQP serverTushar Katarki
7
nova instance does not boot P1 - Critical (4 hrs.)1. check virsh list on the nova comute node and see if instance is boting 2. tail -f /var/log/nova/nova-compute.log u should see an entry or search by timestamp in the nova-compute.log close to when instance creation failed Tushar Katarki
8
VM Migrations that take too long fail due to keystone token timeoutVM in question goes into ERROR state.P1 - Critical (4 hrs.)Kalle Happonen
9
KiloAllRabbitMQA brief interruption to RabbitMQ results in multiple other components 'stopping' rather than re-connecte.g. services fill logs with 'reconnecting' messages but never suceed, or just stop responding despite process showing as alive in OSP1 - Critical (4 hrs.)restart the services that stopped responding, confirm heartbeat setupusually just a message saying the connection to MQ was lost then totally empty log after, or we get alert on /var/log being full because the service went nuts trying to reconnectXav Paicexavpaice
10
instances are running but are inaccessible through SSH and do not respond to any commandP2 - Important (24 hrs.)Tushar Katarki
11
instance deleted but still on hypervisorlog message, clean up?P2 - Important (24 hrs.)
12
Log message contains large amount raw dataP4 - Low (5 days)
13
LibertyContainer Not Found reported when too many objects in a containerMust reissue command multiple times before swift list will functionP4 - Low (5 days)
14
nova instance does not boot
1. check virsh list on the nova comute node and see if instance is boting 2. tail -f /var/log/nova/nova-compute.log u should see an entry or search by timestamp in the nova-compute.log close to when instance creation failed Tushar Katarki
15
https://bugs.launchpad.net/nova/+bug/1374508LibertyNovaComputeBooting instance from ISO image and trying to attach cinder volume to the instance results in nova volume-attach command will succeed. But, the operation will fail with errors in nova-compute.log https://review.openstack.org/#/c/259685/
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100