-
Notifications
You must be signed in to change notification settings - Fork 926
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
6.52: Unable to run cf push
: "No API endpoint set. Use 'cf login' or 'cf api' to target an endpoint"
#2033
Comments
We have created an issue in Pivotal Tracker to manage this: https://www.pivotaltracker.com/story/show/174542102 The labels on this github issue will be updated when the story is started. |
@vpicone I wish I found this issue 5 hours ago (when you reported it), our team ran into this same issue and discovered that downgrading to |
This change locks down the CF CLI version to `6.51.0`, due to cloudfoundry/cli#2033. Adds support for the following options: * `cf-api` The CloudFoundry API entrypoint * `cf-group`: The resource group name
Hey there @vpicone - thanks for reporting this issue. As per the v6.52.0 release notes, CLI users that previously targeted and logged into their foundations before updating to the v6.52.0 CLI version may be required to to re-login & target in order to initialize the updated config. Is this happening outside of your ci pipelines as well - even after re-login & target? Please let us know once you've got more info. |
@heyjcollins Yes, the error described above happens even if I |
we had this issue when running builds in travis. We had to force 6.51 when installing as a plugin to the the |
Hello all, |
Thanks for the responses @marek5050 @damache @l2fprod @neumannrf @jeffchew @vpicone, Could you please provide us with the exact commands you're running which lead to this error? Also - in each of your cases, is there a wrapper on the cf CLI? |
In my case, I'm calling |
below is our Travis build script and the corresponding log. the travis_fail.txt Logging back in after every command keep it going until I executed an external script to run a blue green deploy to CF. Then it failed there for the same issue. Adding the restriction to the 6.51 install fixed the build. |
Hi IBM friends, we haven't been able to reproduce this with v6.52.0. It's worth noting though that we are using the cc @a-b |
The root cause is that staring in CF CLI |
Meanwhile, I suggest CF CLI should consider add a warning message when clearing the config, for user experience perspective. |
@archerzz This is really good feedback, I think whenever in the future we update the config between versions we'll try and make that a bit less painful, its also good to know that in the future this will break the ibmcloud CLI when we bump config versions, (we should capture that feedback @heyjcollins) For now I am closing this issue since it seems we have a resolution. Please feel free to re-open it if you feel that I've closed it in error. Thanks for reporting this y'all!! Jenna |
CF_TRACE=1
to help debug the issue.Describe the bug and the command you saw an issue with
Our CI deployment action suddenly started failing once
6.52
was released. Nothing else has changed with our deployment config in months. Pinning to6.51
fixed the issue for us: successful run after pinning CF to 6.51Expected behavior
Should be able to login with the same credentials as
6.51
The text was updated successfully, but these errors were encountered: