Red Hat Bugzilla – Bug 1252437
[Discovery] Gathers wrong information about disks available
Last modified: 2016-04-06 08:41:22 EDT
Description of problem: Our storage node contains: 3x 800G SSD, 20x 1.2T SAS 1 SSD is for OS, 2 SSDs are for caching SAS disks Running Discovery against this setup, we've gathered info, that there is 1.2T disk available for installing OS. This data is populated in flavors and in ironic node-show: properties/local_gb and is causing later problems with deploying cloud. Workaround: Manually change flavor data and edit ironic node-show
Hi! What's the way to distinguish between "correct" and "incorrect" disks in your case? Currently discoverd just takes the 1st available disk, we need some hints if we have to change this.
We've talked on IRC a bit, and I think for RHOS 7 we should just sort disks list, so that /dev/sda goes first. For RHOS 8 we need to support ironic root device hints in inspector. Blueprint https://blueprints.launchpad.net/ironic-inspector/+spec/root-device-hints
In a virtual environment a node with 4 additional disks reports u'local_gb': u'9': [root@overcloud-controller-2 ~]# fdisk -l | grep Disk | grep sd.. Disk /dev/sda: 44.0 GB, 44023414784 bytes, 85983232 sectors Disk /dev/sdc: 21.5 GB, 21474836480 bytes, 41943040 sectors Disk /dev/sdb: 21.5 GB, 21474836480 bytes, 41943040 sectors Disk /dev/sdd: 10.7 GB, 10737418240 bytes, 20971520 sectors Disk /dev/sde: 10.7 GB, 10737418240 bytes, 20971520 sectors [stack@instack ~]$ ironic node-show 534f9bd7-3f4b-4838-934f-488bcd9cb6dc | grep local_gb | properties | {u'memory_mb': u'10240', u'cpu_arch': u'x86_64', u'local_gb': u'9', |
[root@overcloud-compute-0 heat-admin]# fdisk -l | grep Disk | grep sd.. Disk /dev/sdc: 10.7 GB, 10737418240 bytes, 20971520 sectors Disk /dev/sdb: 21.5 GB, 21474836480 bytes, 41943040 sectors Disk /dev/sda: 44.0 GB, 44023414784 bytes, 85983232 sectors [stack@instack ~]$ ironic node-show 5109dc04-4592-4248-8bf5-d585ec16e7f2 | grep local_gb | properties | {u'memory_mb': u'16384', u'cpu_arch': u'x86_64', u'local_gb': u'40', |
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/RHSA-2015:1862