OpenStack Core Infrastructure

run-pep8.sh usage now being output

Bug #1355167 reported by Joshua Harlow
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Core Infrastructure
In Progress
Critical
Jeremy Stanley
OpenStack Core Infrastructure juno

Bug Description

Seems like some new usage output from run-pep8.sh is causing gate commits to fail.

2014-08-11 03:39:57.287 | [gate-taskflow-pep8] $ /bin/bash -xe /tmp/hudson2668360155841633949.sh
2014-08-11 03:39:57.293 | + /usr/local/jenkins/slave_scripts/run-pep8.sh
2014-08-11 03:39:57.297 | + org=
2014-08-11 03:39:57.297 | + project=
2014-08-11 03:39:57.297 | + source /usr/local/jenkins/slave_scripts/functions.sh
2014-08-11 03:39:57.298 | + check_variable_org_project '' '' /usr/local/jenkins/slave_scripts/run-pep8.sh
2014-08-11 03:39:57.298 | + org=
2014-08-11 03:39:57.298 | + project=
2014-08-11 03:39:57.298 | + filename=/usr/local/jenkins/slave_scripts/run-pep8.sh
2014-08-11 03:39:57.298 | + [[ -z '' ]]
2014-08-11 03:39:57.298 | + echo 'Usage: /usr/local/jenkins/slave_scripts/run-pep8.sh ORG PROJECT'
2014-08-11 03:39:57.298 | Usage: /usr/local/jenkins/slave_scripts/run-pep8.sh ORG PROJECT
2014-08-11 03:39:57.298 | + echo
2014-08-11 03:39:57.299 |
2014-08-11 03:39:57.299 | + echo 'ORG: The project organization (eg '\''openstack'\'')'
2014-08-11 03:39:57.299 | ORG: The project organization (eg 'openstack')
2014-08-11 03:39:57.299 | + echo 'PROJECT: The project name (eg '\''nova'\'')'
2014-08-11 03:39:57.299 | PROJECT: The project name (eg 'nova')
2014-08-11 03:39:57.299 | + exit 1

See http://logs.openstack.org/79/101679/11/gate/gate-taskflow-pep8/bd22f99/console.html

This seems like a new change that wasn't occurring previously?

Revision history for this message
Jeremy Stanley (fungi) wrote :

This looks like a stale nodepool image somewhere which doesn't have the prerequisite slave script changes for the recent ORG parameter removal in our jobs. I'll figure out where it's cropping up and get it updated.

Changed in openstack-ci:
status: New → In Progress
importance: Undecided → Critical
assignee: nobody → Jeremy Stanley (fungi)
milestone: none → juno
Revision history for this message
Jeremy Stanley (fungi) wrote :

It seems this was hit four times in the past week on bare-precise and bare-trusty nodes, only in rax-dfw. It shouldn't be happening any longer in theory, since we've had successful image updates for those for at least the past two days... yet two of these were seen within the past 24 hours.

Revision history for this message
Jeremy Stanley (fungi) wrote :

http://logstash.openstack.org/#eyJzZWFyY2giOiJtZXNzYWdlOlwiVXNhZ2U6IC91c3IvbG9jYWwvamVua2lucy9zbGF2ZV9zY3JpcHRzL3J1bi1wZXA4LnNoIE9SRyBQUk9KRUNUXCIgQU5EIHRhZ3M6Y29uc29sZSIsImZpZWxkcyI6W10sIm9mZnNldCI6MCwidGltZWZyYW1lIjoiNjA0ODAwIiwiZ3JhcGhtb2RlIjoiY291bnQiLCJ0aW1lIjp7InVzZXJfaW50ZXJ2YWwiOjB9LCJzdGFtcCI6MTQwNzc3MTY5OTcwOX0=

Revision history for this message
Jeremy Stanley (fungi) wrote :

Looks like we hit another within the past hour... also a bare-trusty-rax-dfw. I logged into another in use there and it had the expected (newer) code in that slave script so it's definitely not an issue with the nodepool image.

Revision history for this message
Jeremy Stanley (fungi) wrote :

According to nodepool's log it was created mere minutes before the job ran...

2014-08-11 20:18:26,610 INFO nodepool.NodeLauncher: Creating server with hostname bare-trusty-rax-dfw-1405638.slave.openstack.org in rax-dfw from image bare-trusty for node id: 1405638

Revision history for this message
Andreas Jaeger (jaegerandi) wrote :

The query does not return anything for the last 7 days, I expect this is fixed.

Revision history for this message
Jeremy Stanley (fungi) wrote :

At this point I'm pretty sure this specific query should no longer return any hits, but the underlying cause in DFW is now suspected to be the same as for bug 1355907 and bug 1354829 and has yet to be identified (investigation within Rackspace is still underway).

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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