devstack

Didn't find service registered by hostname after 60 seconds

Bug #1806030 reported by Sorin Sbarnea on 2018-11-30

This bug report is a duplicate of: Bug #1806912: devstack timeout because g-api takes longer than 60 seconds to start. Edit Remove

6

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	devstack	New	Undecided	Unassigned

Bug Description

Tracing bug which is liklely to not to be caused by a specific change.

"message:"Didn't find service registered by hostname after 60 seconds" AND tags:devstacklog.txt

http://logstash.openstack.org/#dashboard/file/logstash.json?query=(message%3A%5C%22No%20matching%20distribution%20found%20for%5C%22%20OR%20message%3A%5C%22%5C%5CnNo%20matching%20distribution%20found%20for%5C%22)%20AND%20tags%3Aconsole%20AND%20voting%3A1%20AND%20build_queue%3Agate

One specific example at http://logs.openstack.org/57/620457/3/check/heat-functional-orig-mysql-lbaasv2/9ed4f0e/logs/devstacklog.txt.gz which failed unrelated to the patch.

See original description

Tags:

Sorin Sbarnea (ssbarnea) on 2018-11-30

description:	updated
description:	updated

Revision history for this message

Matt Riedemann (mriedem) wrote on 2018-12-05:

#1

This isn't really a devstack issue, it's slow ovh-bhs1 nodes, so a duplicate of bug 1806912.

Report a bug

This report contains Public information

Everyone can see this information.

Duplicate of bug #1806912 Remove

You are

Subscribing...

Edit bug mail

Other bug subscribers

Remote bug watches

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