search

vmware-archive / cf-redis-release

BOSH release for a Cloud Foundry Redis service broker that supports shared-vm plans
https://bosh.io/releases/github.com/pivotal-cf/cf-redis-release
Apache License 2.0
19 stars 35 forks source link

Colocated jobs creating package name conflicts #114

Open KeenanHoffman opened 5 years ago

KeenanHoffman commented 5 years ago

It looks like on July 4th the following changes were made: https://github.com/pivotal-cf/cf-redis-release/commit/e5a2eef7ab664618937202191c7e13696a3625e4

I believe this is the same issue descibed here: https://github.com/pivotal-cf/cf-redis-release/issues/84

Colocating these jobs causes our deployment to fail just like it did before we updated the include the fix for the above issue. Here is the error we see:

Error: Package name collision detected in instance group 'cf-redis-broker': job 'cf-cli/cf-cli-6-linux' depends on package 'cf-cli/cf-cli-6-linux' with fingerprint 'af6517f138b3ed0584b263f6273f30f22f6e5c9d', job 'cf-redis/broker-registrar' depends on package 'cf-redis/cf-cli-6-linux' with fingerprint '0971d73c486be23f7d87702ddc75f4d6565942f5'. BOSH cannot currently collocate two packages with identical names and different fingerprints or dependencies.

Just thought i would give a heads up since my team happened to notice this.

Keenan

cf-gitbot commented 5 years ago

We have created an issue in Pivotal Tracker to manage this. Unfortunately, the Pivotal Tracker project is private so you may be unable to view the contents of the story.

The labels on this github issue will be updated when the story is started.

MirahImage commented 5 years ago

Hi @KeenanHoffman, is this still an issue? We noticed similar behaviour and made a further change that should have corrected this.