Marking as "High" as the work around for this bug, once a user is bit by
it, is to have someone in the datacenter physically power cycle a
machine.
** Changed in: ironic
Importance: Undecided => High
** Also affects: nova
Importance: Undecided
Status: New
** Tags added: baremetal
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1320513
Title:
IPMI commands are sent / queried too fast
Status in OpenStack Bare Metal Provisioning Service (Ironic):
In Progress
Status in OpenStack Compute (Nova):
New
Bug description:
http://www.intel.com/content/dam/www/public/us/en/documents/product-briefs/second-gen-interface-spec-v2.pdf
has this in it:
---
1.7.32
Configuration Interfaces
...
In some implementations, changes to configuration parameters may take
effect immediately. Thus, a remote application should be careful when setting
parameters that could cause the
application to become disconnected from the BMC.
For the purpose of conformance checking, up to 5 seconds will be allowed
between the time a parameter is
changed to when it must have taken effect.
----
We've seen repeated cases of BMCs locking up or getting confused with
high frequency polling - it might be an idea to wait 5 seconds - the
required max time between change and effect - rather than the polling
interval we use today.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ironic/+bug/1320513/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : [email protected]
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
