Skip to content
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

sfdx force:org:list does not return active orgs #1641

Closed
james-hafer opened this issue Jul 25, 2022 · 11 comments
Closed

sfdx force:org:list does not return active orgs #1641

james-hafer opened this issue Jul 25, 2022 · 11 comments
Labels
bug Issue or pull request that identifies or fixes a bug investigating We're actively investigating this issue

Comments

@james-hafer
Copy link

Summary

When running sfdx force:org:list, sfdx force:org:list --all, sfdx force:org:list --verbose --json no active orgs are returned. I am still able to open the latest org but cannot open any other orgs if I do not know the username.

Steps To Reproduce:

Run sfdx force:org:list

Expected result

I have three active scratch orgs that should be displayed. If I switch to a previous version I am able to get the active orgs:

image

Actual result

No active scratch orgs found. Specify --all to see all scratch orgs:

image

System Information

{
"cliVersion": "sfdx-cli/7.160.0",
"architecture": "darwin-x64",
"nodeVersion": "node-v14.17.0",
"pluginVersions": [
"@oclif/plugin-autocomplete 0.3.0 (core)",
"@oclif/plugin-commands 1.3.0 (core)",
"@oclif/plugin-help 3.3.1 (core)",
"@oclif/plugin-not-found 1.2.6 (core)",
"@oclif/plugin-plugins 1.10.11 (core)",
"@oclif/plugin-update 1.5.0 (core)",
"@oclif/plugin-warn-if-update-available 1.7.3 (core)",
"@oclif/plugin-which 1.0.4 (core)",
"@salesforce/sfdx-plugin-lwc-test 1.0.0 (core)",
"alias 2.1.0 (core)",
"apex 1.1.0 (core)",
"auth 2.2.2 (core)",
"community 2.0.0 (core)",
"config 1.4.14 (core)",
"custom-metadata 2.0.0 (core)",
"data 2.0.4 (core)",
"generator 2.0.2 (core)",
"info 2.0.1 (core)",
"limits 2.0.1 (core)",
"org 2.0.3 (core)",
"salesforce-alm 54.6.2 (core)",
"schema 2.1.1 (core)",
"sfdx-cli 7.160.0 (core)",
"signups 1.2.0 (core)",
"source 2.0.7 (core)",
"telemetry 2.0.0 (core)",
"templates 55.0.0 (core)",
"trust 2.0.1 (core)",
"user 2.1.0 (core)"
],
"osVersion": "Darwin 21.1.0"
}

@james-hafer james-hafer added the investigating We're actively investigating this issue label Jul 25, 2022
@github-actions
Copy link

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.

@mshanemc
Copy link
Contributor

mshanemc commented Jul 25, 2022

whoa!

  1. Does the devhub that they're related to still show up in your org:list results with a good Connected status?
  2. if you open up one of the auth files for an org you're missing like cat ~/.sfdx/[email protected] what do you see? The tokens are encrypted, but feel free to omit them if you like.

you should see

{
  "instanceUrl": "https://ability-nosoftware-3674-dev-ed.my.salesforce.com",
  "orgId": "00D63000000fzG8EAI",
  "loginUrl": "https://CS43.salesforce.com",
  "clientId": "PlatformCLI",
  "isDevHub": false,
  "devHubUsername": "etc",
  "created": "1657219262000",
  "expirationDate": "2022-08-06",
  "createdOrgInstance": "CS43",
  "snapshot": null,
  "instanceApiVersion": "55.0",
  "instanceApiVersionLastRetrieved": "7/25/2022, 1:48:08 PM",
  "name": "portfolio-tracker",
  "instanceName": "CS43",
  "namespacePrefix": null,
  "isSandbox": false,
  "isScratch": true,
  "trailExpirationDate": "2022-08-07T18:41:27.000+0000",
  "tracksSource": true
}%                

@james-hafer
Copy link
Author

  1. Yes and it does still have a good Connected status
  2. {
    "instanceUrl": "https://page-data-8336-dev-ed.my.salesforce.com",
    "orgId": "00D1h000000OEIWEA4",
    "loginUrl": "https://CS79.salesforce.com",
    "clientId": "PlatformCLI",
    "isDevHub": false,
    "devHubUsername": "etc",
    "created": "1658776487000",
    "expirationDate": "2022-08-08",
    "createdOrgInstance": "CS79",
    "instanceApiVersion": "55.0",
    "instanceApiVersionLastRetrieved": "7/26/2022, 3:50:36 PM",
    "name": "Squivr Development",
    "instanceName": "CS79",
    "namespacePrefix": "squivr",
    "isSandbox": false,
    "isScratch": true,
    "trailExpirationDate": "2022-08-09T19:15:03.000+0000",
    "tracksSource": true,
    }%

@jstvz
Copy link

jstvz commented Jul 27, 2022

I also hit this issue. Steps to reproduce against dreamhouse-lwc (gist):

  1. sfdx force:org:create
  2. sfdx force:user:password:generate
  3. sfdx force:user:create

@peternhale
Copy link
Contributor

@jstvz thanks for your repo. I have been able to reproduce the issue. @james-hafer can you confirm that the orgs not appearing in the list also have additional users created for them?

@peternhale peternhale added the bug Issue or pull request that identifies or fixes a bug label Jul 28, 2022
@git2gus
Copy link

git2gus bot commented Jul 28, 2022

This issue has been linked to a new work item: W-11507149

@james-hafer
Copy link
Author

@peternhale Yes, the orgs have additional users created for them.

@peternhale
Copy link
Contributor

Thanks @james-hafer. I have identified the issue and a fix will be made soon.

@peternhale
Copy link
Contributor

fix in version 7.162.0 of sfdx-cli

@vernemi2
Copy link

vernemi2 commented Aug 5, 2022

Can confirm it's working as expected when updated the cli to 7.162.0. Thanks a lot for a quick turnaround!

@MikhailShumenko
Copy link

@peternhale This issue is still present in "sfdx-cli/7.188.1 darwin-x64 node-v18.13.0" for Mac OS Monterey 12.6

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Issue or pull request that identifies or fixes a bug investigating We're actively investigating this issue
Projects
None yet
Development

No branches or pull requests

6 participants