Red Hat Bugzilla – Bug 1227755
discoverd edeploy plugin puts too much data in Ironic extra column
Last modified: 2015-08-05 09:52:33 EDT
Description of problem: The edeploy plugin stores all of the facts it collects in the extra column of the Ironic db. When using real hardware, edeploy collects a large amount of facts and can lead to overflowing that column: "InternalServerError: Remote error: DBError (DataError) (1406, "Data too long for column 'extra' at row 1") 'UPDATE nodes SET updated_at=%s, properties=%s, extra=%s WHERE nodes.id = %s'" This causes the inspection ramdisk to fail and drop to an emergency shell. How reproducible: This was reported upstream, and I have not personally reproduced the issue. Running extended hardware benchmarks would help reproduce the issue, as that collects even more facts. Steps to Reproduce: 1. Follow the documentation 2. `openstack baremetal introspection bulk start` step will fail Actual results: This error appears on the console of the machine running the ramdisk: "InternalServerError: Remote error: DBError (DataError) (1406, "Data too long for column 'extra' at row 1") 'UPDATE nodes SET updated_at=%s, properties=%s, extra=%s WHERE nodes.id = %s'" Then the ramdisk fails and drops to an emergency shell. Expected results: The inspection ramdisk does not error and drop to an emergency shell. Additional info: Upstream, the idea is to resolve this by storing the edeploy facts in Swift and just putting a reference in the Ironic database.
Reproduced on my setup when I had 2 virtual hard drives configured for a host. Once the hard drives were removed - the discovery completed successfully.
Upstream patches to fix this are all merged: discoverd (renamed to inspector): https://review.openstack.org/#/c/189427/ instack-undercloud: https://review.gerrithub.io/#/c/236369/ ahc-tools: https://review.gerrithub.io/#/c/236579
*** Bug 1234232 has been marked as a duplicate of this bug. ***
*** Bug 1237058 has been marked as a duplicate of this bug. ***
Tested on OSP7 RC2 and Director Beta2 and problem no longer occurs
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2015:1549