Message formatting issue when retries all fail (introspection)

Bug #1729835 reported by Julie Pichon
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tripleo
Incomplete
Medium
Unassigned

Bug Description

There's some issue with my environment (I guess!) and node introspection failed. However the final error message summarising the problems wasn't displayed correctly and only shows one letter per line, see below. This is running master.

- - -
$ openstack overcloud node import --introspect --provide instackenv.json
Started Mistral Workflow tripleo.baremetal.v1.register_or_update. Execution ID: 4f8f04e0-6432-477f-8f41-4b7ec000141d
Waiting for messages on queue '81daefb1-65e3-46df-95c5-85331f7c20fc' with no timeout.

Nodes set to managed.
Successfully registered node UUID f97347ea-3ec0-4951-8722-68e702cdd858
Successfully registered node UUID 34e1fbbd-e982-4d49-b994-3f0353951e84
Waiting for introspection to finish...
Started Mistral Workflow tripleo.baremetal.v1.introspect. Execution ID: 1ffc714c-9c05-4886-a55a-e4bfa32f3e8a
Waiting for messages on queue '81daefb1-65e3-46df-95c5-85331f7c20fc' with no timeout.
Introspection of node f97347ea-3ec0-4951-8722-68e702cdd858 timed out.
Introspection of node 34e1fbbd-e982-4d49-b994-3f0353951e84 timed out.
Retrying 2 nodes that failed introspection. Attempt 2 of 3
Introspection of node 34e1fbbd-e982-4d49-b994-3f0353951e84 timed out.
Introspection of node f97347ea-3ec0-4951-8722-68e702cdd858 timed out.
Retrying 2 nodes that failed introspection. Attempt 3 of 3
Introspection of node f97347ea-3ec0-4951-8722-68e702cdd858 timed out.
Introspection of node 34e1fbbd-e982-4d49-b994-3f0353951e84 timed out.
Retry limit reached with 2 nodes still failing introspection
Introspection completed with errors:
R
e
t
r
y

l
i
m
i
t

r
e
a
c
h
e
d

w
i
t
h

2

n
o
d
e
s

s
t
i
l
l

f
a
i
l
i
n
g

i
n
t
r
o
s
p
e
c
t
i
o
n

python-tripleoclient-8.0.1-0.20171031220828.557323d.el7.centos.noarch
openstack-tripleo-common-8.1.1-0.20171102011011.289a48a.el7.centos.noarch

Changed in tripleo:
milestone: queens-3 → queens-rc1
Changed in tripleo:
milestone: queens-rc1 → rocky-1
Changed in tripleo:
milestone: rocky-1 → rocky-2
Changed in tripleo:
milestone: rocky-2 → rocky-3
Changed in tripleo:
milestone: rocky-3 → rocky-rc1
Changed in tripleo:
milestone: rocky-rc1 → stein-1
Changed in tripleo:
milestone: stein-1 → stein-2
Changed in tripleo:
milestone: stein-2 → stein-3
Revision history for this message
Juan Antonio Osorio Robles (juan-osorio-robles) wrote :

Is this still an issue?

Changed in tripleo:
milestone: stein-3 → train-1
Changed in tripleo:
milestone: train-1 → train-2
Changed in tripleo:
milestone: train-2 → train-3
Changed in tripleo:
milestone: train-3 → ussuri-1
Changed in tripleo:
milestone: ussuri-1 → ussuri-2
wes hayutin (weshayutin)
Changed in tripleo:
milestone: ussuri-2 → ussuri-3
wes hayutin (weshayutin)
Changed in tripleo:
milestone: ussuri-3 → ussuri-rc3
wes hayutin (weshayutin)
Changed in tripleo:
status: Triaged → Incomplete
wes hayutin (weshayutin)
Changed in tripleo:
milestone: ussuri-rc3 → victoria-1
Changed in tripleo:
milestone: victoria-1 → victoria-3
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.