Related to the terminated state of the partition is not handled

Bug #1717871 reported by sreeteja
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nova-dpm
New
Undecided
Unassigned

Bug Description

Terminated state is not handled properly..
https://github.com/openstack/nova-dpm/blob/802dc7f80a565d832ea434d179d848c58421f50a/nova_dpm/virt/dpm/vm.py#L51

According to the webservice API documentation

"terminated" - The partition was previously active on the CPC,
but is no longer executing the operating system because all
processors have been stopped by the operating system via some
in-band action. This status may indicate that the operating
system has been shut down or has “crashed”. This status
represents a condition between "active" and "stopped". Although
the partition is not executing the operating system, all CPC
memory, processor, and adapter resources defined for it remain
allocated to it. The Stop Partition action can be used to release
the partition's non-reserved resources and place it in "stopped"
status.

So a work around needs to be implemented by stopping the partition which is in terminated state inorder to release the resources

sreeteja (sreeteja)
affects: mos → nova-dpm
Revision history for this message
Markus Zoeller (markus_z) (mzoeller) wrote :

Here's the state transition diagram of Nova: https://docs.openstack.org/nova/latest/reference/vm-states.html

Is there anyone for the DPM partitions? Starting from state "terminated", which status transitions are possible? Depending on that we could map to "stopped" or "error".

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.