os_collect_config.ec2 [...] Max retries exceeded with url: /latest/meta-data/ [...] Network is unreachable
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Core Infrastructure |
Triaged
|
Medium
|
Unassigned |
Bug Description
Got build failure
2014-03-28 13:56:48.351 | ++ OS_NO_CACHE=True
2014-03-28 13:56:48.351 | ++ export OS_CLOUDNAME=seed
2014-03-28 13:56:48.351 | ++ OS_CLOUDNAME=seed
2014-03-28 13:56:48.352 | + nova list
2014-03-28 13:56:48.785 | +----+-
2014-03-28 13:56:48.785 | | ID | Name | Status | Task State | Power State | Networks |
2014-03-28 13:56:48.785 | +----+-
2014-03-28 13:56:48.822 | +----+-
2014-03-28 13:56:48.822 | ++ grep -oE '([0-9]
2014-03-28 13:56:48.823 | ++ nova list
2014-03-28 13:56:49.300 | ERROR: the main setup script run by this job failed - exit code: 1
2014-03-28 13:56:49.301 | please look at the relevant log files to determine the root cause
2014-03-28 13:56:49.301 | Cleaning up host
2014-03-28 13:56:49.301 | ... this takes 3 - 4 minutes (logs at logs/devstack-
2014-03-28 13:56:53.058 | Build step 'Execute shell' marked build as failure
seems not the same as 1298946 which has a specific ssl failure.
On failure I can see in the logs is :devstack-
2014-03-28 13:14:36.000 | + git fetch http://
2014-03-28 13:14:36.449 | fatal: Couldn't find remote ref refs/zuul/
2014-03-28 13:14:36.455 | Unexpected end of command stream
not clear if the above is expected
logs are here: http://
Changed in openstack-ci: | |
status: | New → Triaged |
importance: | Undecided → Medium |
summary: |
- ERROR: the main setup script run by this job + os_collect_config.ec2 [...] Max retries exceeded with url: /latest/meta- + data/ [...] Network is unreachable |
The "ERROR: the main setup script run by this job failed - exit code: 1" message is referring to a failure encountered in the toci_gate_test.sh script, which was actually reporting its progress to the console. I haven't looked too closely, but it appears nova list may have returned an empty list, failing to match the patterns for which a grep was looking.
Those "fatal: Couldn't find remote ref refs/zuul/ master/ Z.*" messages in the workspace setup job are normal, and simply indicate that for one or more projects there was no zuul ref needed (and thus non served) when the script tried retrieving them (Git lacks a sane look-before- you-leap capability to check for the existence of a remote ref without emitting an error message, and there's no good way to silence those without losing other important error messages at the same time).