Unable to access an application using v2 cf ssh in VMware Tanzu Application Service (TAS) for VMs
search cancel

Unable to access an application using v2 cf ssh in VMware Tanzu Application Service (TAS) for VMs

book

Article ID: 298113

calendar_today

Updated On:

Products

VMware Tanzu Application Service for VMs

Issue/Introduction

When trying to run cf ssh <app_name>, it fails. However, if you run cf v3-ssh <app_name>, you are able to successfully access the application. 

When you run the CF_TRACE=true command, it returns an HTTP 302 error message. 

However, upon further inspection of the Cloud Controller logs, specifically the cloud_controller_ng.log, we can see that the reason for the application not being accessible by the v2 command is that it fails to find the application. 
 
{"timestamp":1614011473.4264953,"message":"Request failed: 404: {\"description\"=>\"The app could not be found: fddde807-2ddb-47bf-a8f0-ef258f4278d9\", \"error_code\"=>\"CF-AppNotFound\", \"code\"=>100004, \"test_mode_info\"=>{\"description\"=>\"The app could not be found: fddde807-2ddb-47bf-a8f0-ef258f4278d9\", \"error_code\"=>\"CF-AppNotFound\", \"backtrace\"=>[\"/var/vcap/data/packages/cloud_controller_ng/c9e98ad8e8110f214782574075a4c022d9994d6a/cloud_controller_ng/app/controllers/base/model_controller.rb:324:in `find_guid'\", \"/var/vcap/data/packages/cloud_controller_ng/c9e98ad8e8110f214782574075a4c022d9994d6a/cloud_controller_ng/app/controllers/base/model_controller.rb:317:in `find_guid_and_validate_access'\", \"/var/vcap/data/packages/cloud_controller_ng/c9e98ad8e8110f214782574075a4c022d9994d6a/cloud_controller_ng/app/controllers/runtime/apps_ssh_controller.rb:30:in `ssh_access_with_index

There can be a number of causes for this: 
  • The application was originally pushed using v3 endpoints.
  • Experimental plugins or commands were used to interact with the application.
  • The v7 CLI was used to interact with the application.


Environment

Product Version: 2.9

Resolution

Workaround

The workaround for this issue is to continue using the V3 ssh command to access the application. Once you move to use the v7 CLI, this will no longer be an issue as this version of the CLI will natively use the v3 endpoints when making requests.