nodepool slaves failing to boot

Bug #1650503 reported by Derek Higgins
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tripleo
Fix Released
Critical
Unassigned

Bug Description

nodepool slaves are failing to boot with the following in their console log

[ 1.536434] hid-generic 0003:0627:0001.0001: input,hidraw0: USB HID v0.01 Pointer [QEMU QEMU USB Tablet] on usb-0000:00:01.2-1/input0
[ 1.915570] tsc: Refined TSC clocksource calibration: 2099.934 MHz
[ 124.086881] dracut-initqueue[131]: Warning: dracut-initqueue timeout - starting timeout scripts
[ 124.600457] dracut-initqueue[131]: Warning: dracut-initqueue timeout - starting timeout scripts
[ 125.108136] dracut-initqueue[131]: Warning: dracut-initqueue timeout - starting timeout scripts
....
[ 184.613191] dracut-initqueue[131]: Warning: dracut-initqueue timeout - starting timeout scripts
[[32m OK [0m] Started dracut initqueue hook.
[[32m OK [0m] Reached target Remote File Systems (Pre).
[[32m OK [0m] Reached target Remote File Systems.
[ [31m*[1;31m*[0m[31m* [0m] A start job is running for dev-disk...8c6a.device (3min 8s / no limit)[K[ [31m*[1;31m*[0m[31m* [0m] A start job is running for dev-disk...8c6a.device (3min 9s / no limit)[K[ [31m*[1;31m*[0m[31m*[0m] A start job is running for dev-disk...8c6a.device (3min 9s / no limit)[K[ [31m*[1;31m*[0m] A start job is running for dev-disk...c6a.device (3min 10s / no limit)[K[ [31m*[0m] A start job is running for dev-disk...c6a.device (3min 10s / no limit)[K[ [31m*[1;31m*[0m] A start job is running for dev-disk...c6a.device (3min 11s.......

infra have been debuging the problem on the other clouds and it looks like it related to the switch to Centos 7.3
https://bugzilla.redhat.com/show_bug.cgi?id=1405238

In the mean time nodepool is creating and destroying instances continuously so until its resolved I've blocked it from using rh1 with iptables

rh1 controller> iptables -I INPUT -s 23.253.73.160 -j DROP

Tags: ci
Changed in tripleo:
milestone: none → ocata-3
Revision history for this message
Emilien Macchi (emilienm) wrote :

problem is solved now, they updated the nodepool images on all cloud providers and jobs are now running well.

Changed in tripleo:
status: Triaged → Fix Released
tags: added: ci
removed: alert
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.