Illegal OpCode red window server HP DL380 G6/HP SmartArray P420/HP ProLiant DL360p Gen8

Bug #1271549 reported by Denis Ipatov
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Triaged
High
Vladimir Kozhukalov

Bug Description

We're now running Fuel with bare metal servers. The nodes for fuel are
detectable, and are able to boot into Fuel's bootstrap image. However, on
node deployment/OS installation, immediately after proxy-booting, our
nodes display a red 'Illegal OpCode' error.

From Centos bootstrap:
lrwxrwxrwx 1 root root 9 Jan 22 13:13 pci-0000:00:1f.2-scsi-0:0:0:0 -> ../../sr0
lrwxrwxrwx 1 root root 9 Jan 22 13:13 pci-0000:04:00.0-scsi-0:0:0:0 -> ../../sda
lrwxrwxrwx 1 root root 10 Jan 22 13:13 pci-0000:04:00.0-scsi-0:0:0:0-part1 -> ../../sda1
lrwxrwxrwx 1 root root 10 Jan 22 13:13 pci-0000:04:00.0-scsi-0:0:0:0-part2 -> ../../sda2
lrwxrwxrwx 1 root root 10 Jan 22 13:13 pci-0000:04:00.0-scsi-0:0:0:0-part3 -> ../../sda3
lrwxrwxrwx 1 root root 10 Jan 22 13:13 pci-0000:04:00.0-scsi-0:0:0:0-part4 -> ../../sda4

From Ubuntu on the same problematic node:
ls /target/dev/disk/by-path

pci-0000:00:1f.2-scsi-0:0:0:0 -> ../../sr0
pci-0000:04:00.0-scsi-0:0:0:0 -> ../../sda
pci-0000:04:00.0-scsi-0:0:0:0-part1 -> ../../sda1
pci-0000:04:00.0-scsi-0:0:0:0-part2 -> ../../sda2
pci-0000:04:00.0-scsi-0:0:0:0-part5 -> ../../sda5

Revision history for this message
Denis Ipatov (dipatov) wrote :
Revision history for this message
Miroslav Anashkin (manashkin) wrote :

Assigned to Vladimir Kozhukalov

Changed in fuel:
assignee: nobody → Vladimir Kozhukalov (kozhukalov)
importance: Undecided → High
milestone: none → 4.1
status: New → Confirmed
Revision history for this message
Vladimir Kuklin (vkuklin) wrote :
Changed in fuel:
status: Confirmed → Triaged
tags: added: customer-found
Revision history for this message
Gleb (gleb-q) wrote :

I have the same situation with HP ProLiant DL360p Gen8 and HP SmartArray P420 (installing ubuntu).

{"build_id": "2014-01-30_01-17-41", "ostf_sha": "338ddf840c229918d1df8c6597588b853d02de4c", "build_number": "68", "nailgun_sha": "6f9766853968f0bba68a0487b43fe67ba02a05f7", "fuelmain_sha": "7d8768f2ac7e1e54d16c135e4ebd64722e49179e", "astute_sha": "d002c3bf626cff96a1d4aec9eb92fc4d5f4542c4", "release": "4.1", "fuellib_sha": "6cb8a54d91bd552539970b01a80ba5635876bd2c"}

The issue reproduces only with Ubuntu (Centos installed successfuly) and with big disks. I tried to install Ubuntu on 10TB volume.
When I tried to install on 1TB volume it works fine.

See attached fuel-snapshot

Revision history for this message
Gleb (gleb-q) wrote :

I have the same situation with HP ProLiant DL360p Gen8 and HP SmartArray P420 (installing ubuntu).

{"build_id": "2014-01-30_01-17-41", "ostf_sha": "338ddf840c229918d1df8c6597588b853d02de4c", "build_number": "68", "nailgun_sha": "6f9766853968f0bba68a0487b43fe67ba02a05f7", "fuelmain_sha": "7d8768f2ac7e1e54d16c135e4ebd64722e49179e", "astute_sha": "d002c3bf626cff96a1d4aec9eb92fc4d5f4542c4", "release": "4.1", "fuellib_sha": "6cb8a54d91bd552539970b01a80ba5635876bd2c"}

The issue reproduces only with Ubuntu (Centos installed successfuly) and with big disks. I tried to install Ubuntu on 10TB volume.
When I tried to install on 1TB volume it works fine.

See attached fuel-snapshot

Revision history for this message
Mike Scherbakov (mihgen) wrote :
Revision history for this message
Vladimir Kuklin (vkuklin) wrote :

Gleb, could you please related change-request: https://review.openstack.org/#/c/70316 ? If it works, please add your +1 to the review.

Revision history for this message
Vladimir Kozhukalov (kozhukalov) wrote :

I believe those two patches solve this issue https://review.openstack.org/71885 https://review.openstack.org/71836

We still have some not critical issues which appear on Vbox and Qemu. One of those issues is exactly what Mike is talking about https://bugs.launchpad.net/fuel/+bug/1263648. Hope we will be able to fix it by making proprietary hard drive links (not by-path and not by-id).

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.