pivotal-cf / cf-redis-smoke-tests Goto Github PK

Currently getting the following error running the redis smoke tests

Creating space cf-redis-smoke-tests-1-SPACE-09f61cc0310c2175 in org system as admin...
OK
Assigning role SpaceManager to user admin in org system / space cf-redis-smoke-tests-1-SPACE-09f61cc0310c2175 as admin...
The user exists in multiple origins. Specify an origin for the requested user from: 'uaa', 'ldap'
FAILED

To resolve am trying to set the space name to be a specific space name. However recently it seems this option has been made non-configurable - https://github.com/pivotal-cf/cf-redis-release/blob/2ac76cb681c41c5dfb326e22e75df9cd14e9b684/jobs/smoke-tests/templates/config.json.erb#L16

Can this be updated back to
'use_existing_space' => p('cf.space_name') ?

Dependabot couldn't resolve your project's dependencies as it couldn't access v1.4.7.tar.gz.

You can provide additional git credentials in your Dependabot dashboard by clicking into the account menu (in the top right) and selecting 'Config variables'. If you use a custom token for the host github.com make sure it has read access to this repo, too.

You can mention @dependabot in the comments below to contact the Dependabot team.

Dependabot couldn't resolve your project's dependencies as it couldn't access v1.4.7.tar.gz.

You can provide additional git credentials in your Dependabot dashboard by clicking into the account menu (in the top right) and selecting 'Config variables'. If you use a custom token for the host github.com make sure it has read access to this repo, too.

You can mention @dependabot in the comments below to contact the Dependabot team.

Dependabot can't resolve your Go dependency files.

As a result, Dependabot couldn't update your dependencies.

The error Dependabot encountered was:

If you think the above is an error on Dependabot's side please don't hesitate to get in touch - we'll do whatever we can to fix it.

View the update logs.

Dependabot couldn't resolve your project's dependencies as it couldn't access v1.4.7.tar.gz.

You can provide additional git credentials in your Dependabot dashboard by clicking into the account menu (in the top right) and selecting 'Config variables'. If you use a custom token for the host github.com make sure it has read access to this repo, too.

You can mention @dependabot in the comments below to contact the Dependabot team.

Dependabot couldn't resolve your project's dependencies as it couldn't access v1.4.7.tar.gz.

You can provide additional git credentials in your Dependabot dashboard by clicking into the account menu (in the top right) and selecting 'Config variables'. If you use a custom token for the host github.com make sure it has read access to this repo, too.

You can mention @dependabot in the comments below to contact the Dependabot team.

Hello,

We discovered that when running the smoke tests, the created app route remains. This bumps up against quota over time and isn't clean.

[2016-08-24 22:16:17.88 (UTC)]> cf delete a3db1950-6350-4a66-9910-deb6816edc2b -f 
Deleting app a3db1950-6350-4a66-9910-deb6816edc2b in org system / space redis-smoke-test-space as redis-test-USER-1-2016_08_24-22h13m57.185s...
OK

$ cf routes
redis-smoke-test-space   a3db1950-6350-4a66-9910-deb6816edc2b   apps.example.com

We believe what is missing is a -r flag

➜  gap-cfsandbox-openstack git:(master) cf delete --help
NAME:
   delete - Delete an app

USAGE:
   cf delete APP_NAME [-f -r]

ALIAS:
   d

OPTIONS:
   -f      Force deletion without confirmation
   -r      Also delete any mapped routes

We run the smoke test frequently, as part of health checks into our systems.