Description of problem: Current Centos Mitaka CBS images and most of the delorean images do not have linux-firmware package installed, which breaks introspection and overcloud deployment on the baremetal hardware that requires firmware. Version-Release number of selected component (if applicable): http://buildlogs.centos.org/centos/7/cloud/x86_64/tripleo_images/mitaka/ Also images built by tripleo installed off master How reproducible: Steps to Reproduce: Use baremetal hardware with bnx2 NetExtreme II network interfaces 1. Upload any of the affected images to undercloud 2. Start introspection 3. Introspection never finishes and console of the baremetal node is full of Network is unreachable messages 1a. Start overcloud deployment of Mitaka CBS overcloud-full image on baremetal hardware with bnx2 network cards 2a. After the disk had been imaged and node reboots, installation doesn't proceed 3a. Reboot the box off USB drive, mount root partition and examine messages 4a. Errors similar to "bnx2: Can’t load firmware file “bnx2/bnx2-rv2p-09ax-6.0.17.fw" Actual results: Introspection doesn't work and times out Overcloud deployment doesn't work and times out Expected results: Introspection works Overcloud deployed successfully Additional info:
John, should this be moved to https://github.com/redhat-openstack/ansible-role-tripleo-image-build/issues ?
Alan, while it could be "fixed" there, I think we would actually want to fix this in TripleO. We would at least want to update the example image building YAML in tripleo-common[1], but if it is a universal requirement, we should add it to some DIB element. However, I am not totally sure which one. If we need it on both the IPA ramdisk and the overcloud-full image, then it probably would have to be added to the base elements. [1] https://github.com/openstack/tripleo-common/blob/master/image-yaml/overcloud-images.yaml
linux-firmware doesn't appear to be in the the delorean images or the yaml mentioned above still. Yet it appears to be in the Red Hat Director images. Happy to pick this one up and have a look if people still think this is required?
The reason for this package missing is because we use Centos cloud images as a base where there is no need to support any hardware that may require this package. The problem is with Ironic deployments, where there is a good chance that this package would be required, it is included in the Centos base packages, if installed from the minimal ISO. This particular issue is no longer relevant for us as we decided not to go ahead with production OpenStack cluster deployment, but I'm sure many would like this package to be present in both inspection and node images.
(In reply to Ilja Maslov from comment #4) > The reason for this package missing is because we use Centos cloud images as > a base where there is no need to support any hardware that may require this > package. > > The problem is with Ironic deployments, where there is a good chance that > this package would be required, it is included in the Centos base packages, > if installed from the minimal ISO. > > This particular issue is no longer relevant for us as we decided not to go > ahead with production OpenStack cluster deployment, but I'm sure many would > like this package to be present in both inspection and node images. Hello, Newbie here... As of this date Centos cloud image files still do not contain linux-firmware. I have 2 x Dell R710 with bnx2 nics that do not boot into introspection because the driver is missing from ipa ramdisk. Error: bnx2: Can't load firmware file "bnx2/bnx2-mips-09-6.2.1b.fw Is there a way to add the firmware directly to agent.ramdisk? What i have tried: virt-customize -a overcloud-full.qcow2 --install linux-firmware openstack overcloud image upload --update-existing Image "overcloud-full-vmlinuz" is up-to-date, skipping. Image "overcloud-full-initrd" is up-to-date, skipping. Image "overcloud-full" was uploaded. +--------------------------------------+----------------+-------------+------------+--------+ | ID | Name | Disk Format | Size | Status | +--------------------------------------+----------------+-------------+------------+--------+ | de601e9a-b738-43ad-9460-087813de67f0 | overcloud-full | qcow2 | 1285160960 | active | +--------------------------------------+----------------+-------------+------------+--------+ Image "bm-deploy-kernel" is up-to-date, skipping. Image "bm-deploy-ramdisk" is up-to-date, skipping. Image file "/httpboot/agent.kernel" is up-to-date, skipping. Image file "/httpboot/agent.ramdisk" is up-to-date, skipping.
Mitaka is EOL, so closing it as EOL, It seems to be fixed with https://review.opendev.org/c/openstack/ironic-python-agent-builder/+/726769, if it's still affecting any supported release feel free to open it for that release so it can be fixed, also for information Ussuri+ releases are CentOS8 only.