fuel-dev team mailing list archive

[David Easter <deaster@xxxxxxxxxxxx>]

For #2, there is a workaround in the release notes that may address the
issue:

http://docs.mirantis.com/openstack/fuel/fuel-5.0/release-notes.html
Bootstrap kernel issues on certain hardware
The bootstrap image shipped with Mirantis OpenStack is based on a 3.10
kernel with firmware built from the in-kernel tree. This can lead to issues
with some hardware configurations, (including some Dell R410/R610s servers).
See LP1323354 <https://bugs.launchpad.net/fuel/+bug/1323354>  for details.
As a workaround, use bootstrap image with 2.6 kernel
<http://9f2b43d3ab92f886c3f0-e8d43ffad23ec549234584e5c62a6e24.r60.cf1.rackcd
n.com/bootstrap-5.0-kernel-2.6.zip> . Copy the downloaded zip archive to the
Fuel master node
scp bootstrap-5.0-kernel-2.6.zip root@10.20.0.2:/root/
Log in to Fuel master node and run the following commands to install new
bootstrap:
cd /root/
yum -y install unzip
unzip bootstrap-5.0-kernel-2.6.zip
cp -b linux /var/www/nailgun/bootstrap/
chmod +x /var/www/nailgun/bootstrap/linux
chmod -w /var/www/nailgun/bootstrap/linux
cp -b initramfs.img /var/www/nailgun/bootstrap/
cobbler sync
Note
 
Existing bootstrap files will be renamed to linux~ and initramfs.img~.
To apply changes to already bootstrapped nodes, simply reboot the affected
nodes to boot with the 2.6 kernel.
Thanks,

- David J. Easter
  Director of Product Management, Mirantis

From:  "Gandhirajan Mariappan (CW)" <gmariapp@xxxxxxxxxxx>
Date:  Thursday, June 5, 2014 at 12:32 AM
To:  "Miroslav Anashkin (manashkin@xxxxxxxxxxxx)" <manashkin@xxxxxxxxxxxx>
Cc:  "fuel-dev@xxxxxxxxxxxxxxxxxxx" <fuel-dev@xxxxxxxxxxxxxxxxxxx>, Prakash
Kaligotla <pkaligot@xxxxxxxxxxx>, DL-GRP-ENG-SQA-Open Stack
<DL-GRP-ENG-SQA-OpenStack@xxxxxxxxxxx>
Subject:  [Fuel-dev] Slave nodes are not discovering in Fuel UI

Hi Miroslav,
 
We have installed Mirantis ISO5.0 in one of our server (master node) and can
able to launch Fuel UI using http://10.24.41.198:8000/#clusters.
 
 
But we are facing below issues over here -
 
1.        Other two servers (Slave1 and Slave2) have been configured to be
able to PXE boot from the master node, but the slave nodes are not getting
discovered in Fuel UI. Is it because of the below issue, or we are still
missing any configuration? Please confirm on the same.

 
2.       Current Fuel 5.0 release has the bootstrap OS that does not have
the NIC firmware require for the IBM M3 servers.  The error we received
while booting the bootstrap OS is "bnx2: Can't load firmware file
"bnx2/bnx2-mips-09-6.2.1b.fw".  It seems this is an known bug with Fuel 5.0.
Please refer to the link https://bugs.launchpad.net/fuel/+bug/1323354 for
the bug description.

Kindly confirm us whether is there any workaround for this bug or do we need
to wait till we get fix in 5.0.1?
 
Thanks and Regards,
Gandhi Rajan
-- Mailing list: https://launchpad.net/~fuel-dev Post to     :
fuel-dev@xxxxxxxxxxxxxxxxxxx Unsubscribe : https://launchpad.net/~fuel-dev
More help   : https://help.launchpad.net/ListHelp