search

bluemixgaragelondon / cf-blue-green-deploy

Cloud Foundry CLI plugin for zero downtime deploys
Apache License 2.0
139 stars 61 forks source link

Could not map route with context path #61

Open sot007 opened 6 years ago

sot007 commented 6 years ago

after upgrade bgd to 1.3, it can't map a route to new app. Error message is : Could not map route - Error resolving route: ENV cli version : cf version 6.35.0 bgd version : 1.3.0

my cloud foundry has 2 shared domains. np1.paas.com np.paas.com

manifest file : applications:

holly-cummins commented 6 years ago

Does the fix for #58 help here? It's not in a release, yet, but you can try the bleeding edge version with the following install steps: 

cf uninstall-plugin blue-green-deploy
cf add-plugin-repo bgd-staging https://garage-cf-plugins.eu-gb.mybluemix.net/
cf install-plugin blue-green-deploy -r bgd-staging
sot007 commented 6 years ago

@holly-cummins thanks for your reply, i also found the comments at #58 . but unfortunately it doesn't work.

sot007 commented 6 years ago

i encountered another problem in similar scenario. Error message is : ssh support is already enabled for 'api-service-new' Could not unmap route - Route api-service-new not found ENV cli version : cf version 6.35.0 bgd version : 1.3.0

my cloud foundry has 2 shared domains. np1.paas.com np.paas.com

manifest file : `applications:

staging app url is api-service-new.np1.paas.com/api does it cause only route not domain and host in manifest?

holly-cummins commented 6 years ago

... and for the second issue, installing from the staging-repo also doesn't help? Parsing those shared domains out of the route is exactly the issue #58 addresses ...

sot007 commented 6 years ago

it still doesn't work using staging BGD. the difference between my case and #58 is i used route and context path. i think the context path is the root cause of failure. if i only use the route without context path, the result is successful.