Public bug reported:
Description
===
Ironic serial console doesn't get disabled when instance is deleted.
I filed the bug in Nova because it seems better to request disabling the
console from virt driver at destoying an instance.
Steps to reproduce
==
* Enroll an ironic
Public bug reported:
Description
===
An instance may not be created with a flavor which using a resource class for a
bare metal node when a resource class is set to a bare metal node in ironic
with 'openstack baremetal node set' command after the node is once enrolled.
It seems that thi
Public bug reported:
After a bare metal instance creation is started, an InventoryInUse
exception is logged as ERROR with stack trace in the log of n-cpu.
Ironic virt driver returns an empty inventory for a node which is
allocated[1]. Due to this, the resource tracker tried to delete this
invento
Public bug reported:
Description
===
When deleting a bare metal instance, even if ironic fails to unprovision a
node, network resources are deallocated. Then VIFs are removed though the VIFs
are not detached from the ironic node. The instance gets in ERROR state and can
be deleted by re
Public bug reported:
'nova-manage cell_v2 discover_hosts' command discovers a host based on compute
node records.
When virt ironic driver is used, a compute node record is created after a node
is created in ironic. If a nova compute host is set up before a node is created
in ironic, discover_ho
Public bug reported:
Description
===
In an environment where there are multiple compute nodes with ironic driver,
when a compute node goes down, another compute node cannot take over ironic
nodes.
Steps to reproduce
==
1. Start multiple compute nodes with ironic driver.
Public bug reported:
For creating instance with booting from a volume, the volume is reserved
before scheduling[1]. When the scheduling is failed due to lack of valid
hosts, the instance gets in ERROR state and the volume is kept in
'attaching' state. The volume reservation is not removed even if
Public bug reported:
When starting an instance with Ironic virt driver, even if Ironic fails
to turn on a server, an instance vm state is set to ACTIVE.
The cause is that the driver doesn't check a 'last error' of the node
after the power action finishes. The error is set if the power action is
f
emented in Liberty, virt driver has a API
named "inject_nmi".
We should change the API name for abstracting an implementation based on the
spec approved in Mitaka.
[1] https://review.openstack.org/#/c/229255/
** Affects: nova
Importance: Undecided
Assignee: Hironori Shi
| Limit |
+-+---+
| instances | 40|
** Affects: nova
Importance: Undecided
Assignee: Hironori Shiina (shiina-hironori)
Status: New
** Changed in: nova
Assignee: (unassigned) => Hironori Shiina (shiina-hironori)
--
You received this bug
"10.1.1.250"} |
:
** Affects: neutron
Importance: Undecided
Assignee: Hironori Shiina (shiina-hironori)
Status: New
** Changed in: neutron
Assignee: (unassigned) => Hironori Shiina (shiina-hironori)
--
You received this bug notification because you are a m
11 matches
Mail list logo