sf package version create report command fails with "sObject type 'Package2VersionCreateRequest' is not supported"

[pozil]

Summary

One of our CI workflow runs had a timeout failure while running the sf package version create command on an unlocked package. This resulted in the following output:

{ "name": "PollingClientTimeout", "message": "The client has timed out. Run 'sf package version create report -i 08cWx0000000MyDIAU' to check the status.", "exitCode": 1, "context": "PackageVersionCreateCommand", "data": { "VersionCreateRequestId": "08cWx0000000MyDIAU" }, "stack": "PollingClientTimeout: The client has timed out. Run 'sf package version create report -i 08cWx0000000MyDIAU' to check the status...

Trusting the recommendation from the above error message, I ran the suggested command:

sf package version create report -i 08cWx0000000MyDIAU

This errored out with the following message:

Error (1): 
Package2Version.ConvertedFromVersionId , AsyncValidation FROM Package2VersionCreateRequest WHERE
                                                              ^
ERROR at Row:1:Column:460
sObject type 'Package2VersionCreateRequest' is not supported. If you are attempting to use a custom object, be sure to append the '__c' after the entity name. Please reference your WSDL or the describe call for the appropriate names.

Steps To Reproduce

I do not know how to reproduce the issue but I guess that the sf package version create report doesn't behave as expected.

Expected result

I expect to see a report that mentions the original error or some success.

Actual result

Unexpected SOQL error as show above.

System Information

{
  "architecture": "darwin-arm64",
  "cliVersion": "@salesforce/cli/2.68.6",
  "nodeVersion": "node-v18.17.0",
  "osVersion": "Darwin 23.6.0",
  "rootPath": "/Users/pozil/.volta/tools/image/packages/@salesforce/cli/lib/node_modules/@salesforce/cli",
  "shell": "zsh",
  "pluginVersions": [
    "@oclif/plugin-autocomplete 3.2.10 (core)",
    "@oclif/plugin-commands 4.1.10 (core)",
    "@oclif/plugin-help 6.2.18 (core)",
    "@oclif/plugin-not-found 3.2.28 (core)",
    "@oclif/plugin-plugins 5.4.17 (core)",
    "@oclif/plugin-search 1.2.16 (core)",
    "@oclif/plugin-update 4.6.13 (core)",
    "@oclif/plugin-version 2.2.16 (core)",
    "@oclif/plugin-warn-if-update-available 3.1.23 (core)",
    "@oclif/plugin-which 3.2.19 (core)",
    "@salesforce/cli 2.68.6 (core)",
    "apex 3.6.3 (core)",
    "api 1.3.2 (core)",
    "auth 3.6.75 (core)",
    "community 3.3.2 (user) published 33 days ago (Sat Nov 02 2024) (latest is 3.3.6)",
    "data 3.11.4 (core)",
    "deploy-retrieve 3.15.13 (core)",
    "info 3.4.21 (core)",
    "lightning-dev 1.9.3 (user) published 30 days ago (Mon Nov 04 2024) (latest is 1.9.4)",
    "limits 3.3.40 (core)",
    "marketplace 1.3.6 (core)",
    "org 5.2.4 (core)",
    "packaging 2.9.3 (core)",
    "schema 3.3.42 (core)",
    "settings 2.4.6 (core)",
    "sobject 1.4.46 (core)",
    "telemetry 3.6.23 (core)",
    "templates 56.3.30 (core)",
    "trust 3.7.43 (core)",
    "user 3.6.3 (core)"
  ]
}

[github-actions]

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.

[mdonnalley]

@pozil Can you rerun the failing command with the --dev-debug flag? That will give us some debug logs to work with. Thanks!

[shetzel]

@pozil - I'm curious if setting the --api-version to something lower than the default API version changes anything. E.g., sf package version create report --api-version 61.0 or 60.0. That query uses the tooling API and we haven't changed that code in a long time so maybe something changed server side recently.

[pozil]

Hi both and thanks for the quick response.

Something happened on the server side because the command now works. I only realized this after trying both of your suggestions and retrying the original command so I don't think that they impacted the result. There must have been been an "unstable" state during the package creation process.

I now have the expected report followed by the list of packaging errors (as expected).

sf package version create report -i 08cWx0000000MyDIAU                   
Package Version Create Request
┌───────────────────────────────┬────────────────────┐
│ Name                          │ Value              │
├───────────────────────────────┼────────────────────┤
│ ID                            │ 08cWx0000000MyDIAU │
│ Status                        │ Error              │
│ Package Id                    │ 0HoWx00000000mPKAQ │
│ Package Version Id            │                    │
│ Subscriber Package Version Id │                    │
│ Tag                           │                    │
│ Branch                        │                    │
│ Created Date                  │ 2024-12-05 15:01   │
│ Installation URL              │                    │
│ Created By                    │ 005Wx000000RInFIAW │
│ Converted From Version Id     │ ID Unavailable     │
└───────────────────────────────┴────────────────────┘