Asset tests broken - URI is not defined errors

[jwforres]

Getting errors like:

1)  unauthenticated user should be able to log in
  - UnknownError: unknown error: [$injector:modulerr] Failed to instantiate module openshiftConsole due to:
ReferenceError: URI is not defined

Seems to be on every test/merge that makes it to asset e2e tests

@liggitt @spadgett in case you can investigate before I can

[jwforres]

Last PR that merged had no ui changes, so I suspect it is some npm or bower dep that has been modified and wasn't version locked

[csrwng]

My PR has no UI changes and it's failing with the same error

[spadgett]

I can't reproduce locally clean installing assets.

[liggitt]

Yeah, the whole queue is affected. I'll look into it in a few minutes if no one else grabs it

[liggitt]

Maybe the cached installed assets in Jenkins bit us

[jwforres]

Yeah it has to be something specific in Jenkins env because I can't
reproduce it locally either

On Wed, Jan 13, 2016 at 7:52 PM, Jordan Liggitt [email protected]
wrote:

Maybe the cached compiled assets in Jenkins bit us

—
Reply to this email directly or view it on GitHub
#6651 (comment).

[jwforres]

Confirmed it was a bad base_ami, not sure what exactly caused the URI.js bower_component to only get partially extracted to the file system.

Latest base_ami and devenv_ami are fine so queue should be unblocked now.

[liggitt]

fixed in https://ci.openshift.redhat.com/jenkins/job/devenv_ami/3143/
tests in openshift/vagrant-openshift#382 should prevent it from happening again