Publishwait flag is being ignored from the new version of package:install. #1895
Comments
|
Thank you for filing this issue. We appreciate your feedback and will review the issue as soon as possible. Remember, however, that GitHub isn't a mechanism for receiving support under any agreement or SLA. If you require immediate assistance, contact Salesforce Customer Support. |
WillieRuemmele
added
the
bug
|
This issue has been linked to a new work item: W-12432030 |
|
Hi @alper-tovi-cko, I'm having a hard time creating a package that is in this uninstallable state for long enough to debug. Can you help by running the |
|
My experience is slightly different. Issue suddenly appeared today (26-Jan-2023) on one codebase, but strangely not on another. Switching to Original error running |
|
Here is output of |
|
@WillieRuemmele I was able to replicate the issue with a package this morning. here is the debug output: config reading core plugin /usr/local/lib/node_modules/sfdx-cli +0ms ErrorInvalidIdNoRecordFound: The subscriber package version 04t08000000cSP6AAM is invalid, no subscriber package version record found. sf:Install ERROR [ |
|
We've been seeing the The curious thing is we are able to successfully build and install new versions of the same package with a different code base and a higher version. Same build server using the same version of the CLI (that I provided in a previous comments). |
|
Fixed by reauthorizing sandbox. Also upgraded to the latest |
|
This should be fixed in the release candidate version of the CLI, 7.187.1. Feel free to try it out. |
|
@mshanemc The issue is not fixed, unfortunately. I switched from legacy install to the current install with version - sfdx-cli/7.187.1. Here is what I get: 10 minutes remaining until timeout. Publish status: Querying Status... |
|
Are you able to append
|
|
Here is the related part. It's Jenkins output so formatting might be a little off. I also removed unique ID, installkey or usernames. sfdx force:package:install --upgradetype DeprecateOnly -u USERNAME_GOES_HERE --package PACKAGE_ID_GOES_HERE --installationkey INSTALL_KEY_GOES_HERE --wait 60 --publishwait 10 --noprompt --dev-debug |
|
Thanks. You can actually delete most of that from the post if you want. I was hoping to get more info around this line: Is there a way I can repro this myself? If not, are you able to reproduce it manually (i.e., outside of Jenkins) and can try some modifications to CLI files? Also, you can run |
|
@alper-tovi-cko - Pretty sure I found the problem and the fix will be in next week's CLI release candidate. The query I mentioned above can throw when the subscriber package version ID is not there yet. The legacy command handled that case but the new command didn't. I added that error handling and some additional logging (viewable with |
|
This issue has been resolved with sfdx-cli/7.190.2. |
|
@gsbasso and @shetzel We are facing the similar issue with one of the packages. With all the versions of the same package the package install command return the below error: Facing this issue on previous(7.179) and latest(7.190) versions of CLI. But the same package is installed successfully when we use the package URL in the browser. Appreciate any help to resolve this. Thank you in advance. |
|
@ar-srinivas - this doesn't look like the same issue. I would make sure you're including the installation key with the command (if necessary) and ensure the target-org is the one you expect. You can also enable debugging ( |
|
This issue started again. This time we are getting this error: { |
|
@alper-tovi-cko - that error doesn't look like the same issue. Looks like you need to add |
|
All good @shetzel. You are right, this was because of the release. All handled. |
|
I have the same error "message": "The subscriber package version is not fully available.", Do I need to add I don't understand this. I believed this applies only to devhubs which have already switched to the new release but my client production org is not on new release |
|
I have the same error "message": "The subscriber package version is not fully available.", however, Why then do I have this error? |
|
Here are the docs on targeting specific releases. Without a complete picture of the problem and reproducer it's difficult to know. There are trailblazer communities specific to packaging that might help. |
Summary
In our CI/CD pipeline, as soon as we create a new package version, we distribute the package to various sandboxes. And because the new package version is not immediately available for installation, we use --publishwait flag with force:package:install command. Since the last release --publishwait flag seems to be broken. We had to switch to force:package:legacy:install to ensure our jobs can be completed.
Steps To Reproduce:
sfdx force:package:version:create --definitionfile config/developer-scratch-def.json --targetdevhubusername [email protected] -p PACKAGE-NAME --versionnumber 1.13.0.11840044 -k INSTALL_KEY --codecoverage --wait 60 --jsonresults in package version creation with SubscriberPackageVersionId 04txxxxxx. Once the package version is created, immediate execution of
sfdx force:package:install --upgradetype DeprecateOnly -u [email protected] --package 04txxxxxx --installationkey INSTALL_KEY --wait 60 --publishwait 10 --nopromptresults in
ERROR running force:package:install: The subscriber package version 04txxxxxx is invalid, no subscriber package version record found.The command completely ignores --publishwait or -b flags. On the other hand, when we reran the same job with immediate execution of the legacy command post package version creation
sfdx force:package:legacy:install --upgradetype DeprecateOnly -u [email protected] --package 04txxxxxx --installationkey INSTALL_KEY --wait 60 --publishwait 10 --nopromptresults in
Waiting for the Subscriber Package Version ID to be published to the target org.then
Waiting for the package install request to complete. Status = IN_PROGRESSExpected result
--publishwait parameter should not be ignored and cli should respond with
Waiting for the Subscriber Package Version ID to be published to the target org.thenWaiting for the package install request to complete. Status = IN_PROGRESSoutput.Actual result
ERROR running force:package:install: The subscriber package version 04txxxxxx is invalid, no subscriber package version record found.System Information
{ "cliVersion": "sfdx-cli/7.184.2", "architecture": "linux-x64", "nodeVersion": "node-v14.20.1", "pluginVersions": [ "@oclif/plugin-autocomplete 1.3.8 (core)", "@oclif/plugin-commands 2.2.2 (core)", "@oclif/plugin-help 5.1.20 (core)", "@oclif/plugin-not-found 2.3.13 (core)", "@oclif/plugin-plugins 2.1.8 (core)", "@oclif/plugin-search 0.0.6 (core)", "@oclif/plugin-update 3.0.9 (core)", "@oclif/plugin-version 1.1.4 (core)", "@oclif/plugin-warn-if-update-available 2.0.18 (core)", "@oclif/plugin-which 2.2.6 (core)", "alias 2.1.16 (core)", "apex 1.3.0 (core)", "auth 2.3.10 (core)", "community 2.1.3 (core)", "config 1.4.23 (core)", "custom-metadata 2.0.11 (core)", "data 2.1.22 (core)", "generator 2.0.15 (core)", "info 2.3.2 (core)", "limits 2.2.2 (core)", "org 2.2.22 (core)", "packaging 1.12.2 (core)", "schema 2.2.2 (core)", "signups 1.2.12 (core)", "source 2.3.12 (core)", "telemetry 2.0.5 (core)", "templates 55.1.0 (core)", "trust 2.2.6 (core)", "user 2.1.25 (core)", "@salesforce/sfdx-plugin-lwc-test 1.0.1 (core)", "salesforce-alm 54.8.5 (core)" ], "osVersion": "Linux 4.14.301-224.520.amzn2.x86_64", "shell": "unknown", "rootPath": "/usr/local/lib/node_modules/sfdx-cli" }The text was updated successfully, but these errors were encountered: