-
Notifications
You must be signed in to change notification settings - Fork 52
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
Application provision fails with E_INVALIDARG fabric error #107
Comments
Could anybody have any idea? |
@venkatnossam can you edit the title and body of your issue to include the debug logs, as it stands it's difficult to identify what your issue is. Can you please actually fill out the issue template? |
i ran the following command successfully: sfctl application upload --path ~\Application\pkg\Debug --show-progress Upload complete when i run the following command: sfctl application provision --no-wait --application-type-build-path Debug I am getting this error |
pip show sfctl |
@venkatnossam what is the runtime version of you Service Fabric cluster? |
This is what i see: 6.1.456.9494 7/15/2018 12:00:00 AM |
@venkatnossam it should be a property of the cluster, if you look at your Service Fabric cluster in the Azure Portal, it should have an entry for |
service fabric version: 6.2.283.9494 |
I suspect that this might be an issue with the way that we are serializing the body parameters. Would it be possible for you to provide a capture of the outgoing HTTP POST request from calling the sfctl command? Could you also share the version of msrest you have installed? In the meantime, to unblock you, you can provision with the REST API for provision application or if you have PowerShell installed, you can use the PowerShell command Register-ServiceFabricApplicationType Thank you! |
I have the same issue `sfctl application provision --application-type-build-path app (E_INVALIDARG) Invalid argument ` ` Name: sfctl Deploying ASP.NET Core 2.0 Application. |
Thank you for reporting this, @dnataraj , and apologies that you're running into this issue. Does the mitigation provided above work for you? (using REST or PowerShell) In the mean time, we would very much appreciate your help in getting to the bottom of this issue. Can you provide the output / version from Thank you! |
Hi @Christina-Kang, I'm on Ubuntu 16.04, and Powershell for Linux does not have the SF SDK, so I can't use that work around (or does it?). I haven't tried hitting the REST API, would you have an example of the provisioning payload at hand? Here is the output from msrest : ` ` Thanks. |
@dnataraj to make the REST call, I use either Postman or Advanced REST Client. The URL of the HTTPS POST request will look like this:
The body will look like:
For Advanced Rest Client (a Chrome extension), you can get XHR Extension for authenticating the request. It will allow you to use certs installed in Chrome. You will then have an option near the request URL in the UI to select "Use XHR extension". For Postman authentication, under "Settings" in the top bar, there is a tab "Certificates" with an option "Add Certificate". If you are using a .pem file, the host will be Please let me know if this workaround works for you. If not, I'd love to set up a call and see if we can fix the issue. We are working on making our error messages return more meaning error messages in the future. I am looking into the best way to get the request body, and will update later. Thanks again, |
@dnataraj I have attached a whl for sfctl which will create a file called There should be a portion which looks like If this doesn't turn anything up, we can take a look at your traces to find the issue, and fix it on our end to make the issue clearer in the future. Thanks! |
Hi @Christina-Kang In this URL there is a note saying "Standalone clusters aren't supported in Linux." Does this mean that provision will not work or merely Microsoft will not actively support Standalone Linux clusters. thanks |
@jeffj6123 Can you answer MyCADDev's question? Thanks! |
After running
sfctl application upload --path ~\Application\pkg\Debug --show-progress
The upload completes successfully, but then when running
sfctl application provision --no-wait --application-type-build-path Debug
I am getting this error
sfctl version 5.0.0
The text was updated successfully, but these errors were encountered: