fuel-dev team mailing list archive

Thread
Date

Re: deployment freeze with hp Proliant BL680c G5

To: Mike Scherbakov <mscherbakov@xxxxxxxxxxxx>, Vladimir Kuklin <vkuklin@xxxxxxxxxxxx>
From: <samuel.bartel@xxxxxxxxxx>
Date: Wed, 23 Apr 2014 15:31:56 +0200
Accept-language: fr-FR
Acceptlanguage: fr-FR
Cc: "fuel-dev@xxxxxxxxxxxxxxxxxxx" <fuel-dev@xxxxxxxxxxxxxxxxxxx>
In-reply-to: <CAKYN3rMGCc4BxjR_Pjtm20XjL0Hc3bjHMCdkE017s2Ex70DqGw@mail.gmail.com>
Thread-index: Ac9eVDctVCcnt5KkQkSzuHw2wqiCWAApC4e0
Thread-topic: [Fuel-dev] deployment freeze with hp Proliant BL680c G5

Hello and thanks for the how to,

We made some progress in our investigation. We manage to access to the ILO remote console of the HP servers during the installation. the problem in fact doesn't come from qla2xxx qlogic card. there are in fact two problems :
1/Sometimes, during the installation process the BL680C servers act as the were not able to reach the fuel master node. we have an error message saying that the mirror is not reacheable. If we choose retry (without modifying anythin on our network or harware configuration) the installation continu with no problem
2/After the installation of ubuntu during the initial reboot we got an error about the volume for glance which is not created.
with the remote console we can see that the server is blocked with the following messages :
fsck from util-linux 2.20.1
fsck from util-linux 2.20.1
/dev/cciss/c0D0p3: clean, 67430/1708784 files, 399493/684712 blocks
/dev/cciss/c0D0p2: clean, 236/48960 files, 62566/195312 blocks
The dis drive for /var/lib/nova is not ready yet or not present.
Continue to wai, or PressS to skip mounting or M for manual recovery.
It is then not possible to press any key as the keyboard seems to be ignored

We are going to create tickets on to the Mirantis support

regards

Samuel

________________________________
De : Mike Scherbakov [mscherbakov@xxxxxxxxxxxx]
Date d'envoi : mardi 22 avril 2014 19:56
À : Vladimir Kuklin
Cc : BARTEL Samuel NRS; fuel-dev@xxxxxxxxxxxxxxxxxxx
Objet : Re: [Fuel-dev] deployment freeze with hp Proliant BL680c G5

Hi Samuel,
please feel free to request more details here in this thread and ping folks in IRC #fuel-dev.

Vladimir is aglarendil there, and I'm mihgen. I won't be much helpful but I'll ping others to help :)

Thanks,

On Tue, Apr 22, 2014 at 9:45 PM, Vladimir Kuklin <vkuklin@xxxxxxxxxxxx<mailto:vkuklin@xxxxxxxxxxxx>> wrote:
Samuel, you can do the following thing:

firstly, repack bootstrap image and include blacklisting of qla2xxx modules there
then, you can alter kickstart/preseed for ubuntu/centos in /var/lib/kickstarts and add echoing of this blacklist string to corresponding files in /etc/
finally you will need to update initrd do include this blacklist.
For Ubuntu, you can simply rerun update-initramfs -u inside the target system chroot by adding something like
'in-target update-initramfs -u && \' (there is some magic with preseed line carriage - look into preseed for the correct example)
For RedHat-based distro you can use rd.blacklist kernel option. look here: http://people.redhat.com/harald/dracut-rhel6.html .

On Tue, Apr 22, 2014 at 1:31 PM, <samuel.bartel@xxxxxxxxxx<mailto:samuel.bartel@xxxxxxxxxx>> wrote:
Hello Vladimir,
Unfortunatly we are quiete sure that updating the bios won't solve our issue as THE QLA2XXX refered to Qlogic SAN card which are not present in our blade center. A work around could be to add qlaxxxx module on the blacklist file of linux but we can not modify the linux image installed

we tried several HA and non HA deployment for these servers and install always block at the end of the operating system installation

are the SAN cards mandatories for the installation?

Samuel

________________________________
De : Vladimir Kuklin [vkuklin@xxxxxxxxxxxx<mailto:vkuklin@xxxxxxxxxxxx>]
Date d'envoi : jeudi 17 avril 2014 13:04
À : BARTEL Samuel NRS
Cc : fuel-dev@xxxxxxxxxxxxxxxxxxx<mailto:fuel-dev@xxxxxxxxxxxxxxxxxxx>
Objet : Re: [Fuel-dev] deployment freeze with hp Proliant BL680c G5

Sam, you can try to fix this by updating your server's BIOS. Pretty much looks like hardware bug.

On Thu, Apr 17, 2014 at 12:44 PM, <samuel.bartel@xxxxxxxxxx<mailto:samuel.bartel@xxxxxxxxxx>> wrote:
Hello,

we are trying to deploy openstack on ubuntu 12.04 on Hp Proliant BL680c G5 using fuel 4.1
we are using 3 IBM X3550 as controller node and a Hp Proliant BL680c
unbuntu installation is over on IBM servers but seems to be freeze on HP Proliant

In the HP blade we have the folowwing error on the messages log

2014-04-11 09:36:27 ERR

kernel: qla2xxx [0000:14:00.1]-0034:1: MSI-X: Unsupported ISP 2432 SSVID/SSDID (0x103C,0x1705).

2014-04-11 09:36:27 ERR

kernel: qla2xxx [0000:14:00.0]-0034:0: MSI-X: Unsupported ISP 2432 SSVID/SSDID (0x103C,0x1705).

2014-04-11 09:36:26 ERR

kernel: [Firmware Bug]: the BIOS has corrupted hw-PMU resources (MSR 186 is 43003c)

2014-04-11 09:26:26 ERR

kernel: qla2xxx [0000:14:00.1]-0034:1: MSI-X: Unsupported ISP 2432 SSVID/SSDID (0x103C,0x1705).

2014-04-11 09:26:26 ERR

kernel: qla2xxx [0000:14:00.0]-0034:0: MSI-X: Unsupported ISP 2432 SSVID/SSDID (0x103C,0x1705).

2014-04-11 09:26:26 ERR

kernel: [Firmware Bug]: the BIOS has corrupted hw-PMU resources (MSR 186 is 43003c)

2014-04-11 09:21:38 ERR

kernel: qla2xxx [0000:14:00.1]-0034:1: MSI-X: Unsupported ISP 2432 SSVID/SSDID (0x103C,0x1705).

2014-04-11 09:21:38 ERR

kernel: qla2xxx [0000:14:00.0]-0034:0: MSI-X: Unsupported ISP 2432 SSVID/SSDID (0x103C,0x1705).

2014-04-11 09:21:38 ERR

kernel: [Firmware Bug]: the BIOS has corrupted hw-PMU resources (MSR 186 is 43003c)

can it exmplain the installation freeze? is it a known issue?

regards

Samuel

_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.

--
Mailing list: https://launchpad.net/~fuel-dev
Post to : fuel-dev@xxxxxxxxxxxxxxxxxxx<mailto:fuel-dev@xxxxxxxxxxxxxxxxxxx>
Unsubscribe : https://launchpad.net/~fuel-dev
More help : https://help.launchpad.net/ListHelp

--
Yours Faithfully,
Vladimir Kuklin,
Fuel Library Tech Lead,
Mirantis, Inc.
+7 (495) 640-49-04
+7 (926) 702-39-68
Skype kuklinvv
45bk3, Vorontsovskaya Str.
Moscow, Russia,
www.mirantis.com<http://www.mirantis.ru/>
www.mirantis.ru<http://www.mirantis.ru/>
vkuklin@xxxxxxxxxxxx<mailto:vkuklin@xxxxxxxxxxxx>

_________________________________________________________________________________________________________________________

--
Mike Scherbakov
#mihgen

_________________________________________________________________________________________________________________________

Follow ups

Re: deployment freeze with hp Proliant BL680c G5
From: Miroslav Anashkin, 2014-04-23

References

deployment freeze with hp Proliant BL680c G5
From: samuel.bartel, 2014-04-17
Re: deployment freeze with hp Proliant BL680c G5
From: Vladimir Kuklin, 2014-04-17
Re: deployment freeze with hp Proliant BL680c G5
From: samuel.bartel, 2014-04-22
Re: deployment freeze with hp Proliant BL680c G5
From: Vladimir Kuklin, 2014-04-22
Re: deployment freeze with hp Proliant BL680c G5
From: Mike Scherbakov, 2014-04-22