Instance stuck in Paused state

Bug #1317068 reported by Dmitry Ukov
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Invalid
High
Fuel DevOps

Bug Description

{
"mirantis": "no",
"ostf_sha": "fe718434f88f2ab167779770828a195f06eb29f8",
"nailgun_sha": "f3728d9dadcf9ae16856d8b5086937366384ae78",
"production": "docker",
"api": "1.0",
"fuelmain_sha": "d265b30f2bd13d70071fd11de16f731aa9d38d5b",
"astute_sha": "9c83d3ecec69df03cd94620e2df92249ba4ec786",
"release": "5.0",
"fuellib_sha": "cb5217ca3935a80b71d17d79ae0a19f6a0544906"
}

Steps to reproduse
1. Select Ubuntu release
2. Select HA mode
3. Select Neutron with VLAN
4. Use 3 nodes as controller
5. Use 1 node as compute
6. Deploy OpenStack
7. Spawn an instance

As a result instance will be in a Paused state. I'd tied to resume instance manually (virsh resume) but got an error message:
"
error: internal error unable to execute QEMU command 'cont': Resetting the Virtual Machine is required
"

It looks like a kernel bug
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1045027

Revision history for this message
Dmitry Ukov (dukov) wrote :
Mike Scherbakov (mihgen)
Changed in fuel:
milestone: none → 5.0
Revision history for this message
Vladimir Kuklin (vkuklin) wrote :

are you using hardware or virtual-based environment ?

Changed in fuel:
assignee: nobody → Sergii Golovatiuk (sgolovatiuk)
Revision history for this message
Dmitry Ukov (dukov) wrote :

Virtual based env

Revision history for this message
Sergii Golovatiuk (sgolovatiuk) wrote :

Unfortunately, I was not able to reproduce the bug. Also I checked the logs from latest tests and OSTF tests passed successfully. Most likely, the issue is related to your local environment.

Changed in fuel:
status: New → Incomplete
assignee: Sergii Golovatiuk (sgolovatiuk) → nobody
assignee: nobody → Fuel Library Team (fuel-library)
Mike Scherbakov (mihgen)
Changed in fuel:
milestone: 5.0 → 5.1
summary: - Insntance stuck in Paused state
+ Instance stuck in Paused state
Changed in fuel:
assignee: Fuel Library Team (fuel-library) → Fuel DevOps (fuel-devops)
importance: Undecided → High
Revision history for this message
Mike Scherbakov (mihgen) wrote :

Sergii, how is it related to DevOps?
There was no response / additional information about the issue for a month, so closing as Invalid.

Please reopen this bug if you face an issue again, and provide more information, if possible.

Changed in fuel:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.