Centos bootstrap hangs. Last line is "Switching to clocksource tsc"

Bug #1485019 reported by Leontii Istomin
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Invalid
High
Fuel Library (Deprecated)

Bug Description

2 from 203 nodes was hanged during discovering with "Switching to clocksource tsc" (screenshot is attached)

[root@bootstrap ~]# uname -a
Linux bootstrap 3.10.55-1.el6.mos5.x86_64 #1 SMP Tue Jun 30 13:21:52 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
[root@bootstrap ~]# cat /etc/issue
CentOS release 6.5 (Final)
Kernel \r on an \m

configuration of nodes:
http://paste.openstack.org/show/414459/
http://paste.openstack.org/show/414460/

After restarting the nodes, it booted as usual, without the issue.

api: '1.0'
astute_sha: 34e0493afa22999c4a07d3198ceb945116ab7932
auth_required: true
build_id: 2015-07-27_09-24-22
build_number: '98'
feature_groups:
- mirantis
fuel-agent_sha: 2a65f11c10b0aeb5184247635a19740fc3edde21
fuel-library_sha: 39c3162ee2e2ff6e3af82f703998f95ff4cc2b7a
fuel-ostf_sha: 94a483c8aba639be3b96616c1396ef290dcc00cd
fuelmain_sha: 921918a3bd3d278431f35ad917989e46b0c24100
nailgun_sha: d5c19f6afc66b5efe3c61ecb49025c1002ccbdc6
openstack_version: 2015.1.0-7.0
production: docker
python-fuelclient_sha: 58c411d87a7eaf0fd6892eae2b5cb1eff4190c98
release: '7.0'

Tags: scale
Revision history for this message
Leontii Istomin (listomin) wrote :
Revision history for this message
Leontii Istomin (listomin) wrote :

Can be similar with this case https://bugs.launchpad.net/fuel/+bug/1312671

Changed in fuel:
milestone: none → 7.0
importance: Undecided → High
assignee: nobody → Fuel build team (fuel-build)
assignee: Fuel build team (fuel-build) → Fuel Library Team (fuel-library)
Revision history for this message
Sergii Golovatiuk (sgolovatiuk) wrote :

Mostly, it's related to hardware. Please check if BIOS if it contains "Intel Virtualization Technology" "enabled".

Changed in fuel:
status: New → Invalid
Revision history for this message
Sergii Golovatiuk (sgolovatiuk) wrote :

According to all related bugs, the problem is with these particalar 2 nodes. They are either misconfigured or have hardware defect. Logs doesn't contain any meaningful information.

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.