Getting error when importing repo to GitHub

[Paul-Fazio-Imprivata]

I am using GEI to migrate a repository from an on-prem Bitbucket Server to GitHub. I'm seeing an error and I'm not sure if it's a user error or an actual error. I'm looking for some help/guidance.

Because our Bitbucket Server is behind a firewall I've set up an AWS S3 bucket per the GitHub migration instructions. I'm doing the migration in two steps - first calling gh bbs2gh migrate-repo with the --bbs-server-url, --bbs-project and --bbs-repo arguments. That is generating a .tar file which I manually copy to my local machine.

For the second step I call gh bbs2gh migrate-repo with the --archive-path, --github-org, --github-repo and --aws-bucket-name arguments. Below is the relevant command and its output

c:\Users\pfazio\Downloads>gh bbs2gh migrate-repo --archive-path C:\Users\pfazio\Downloads\Bitbucket_export_7.tar --github-org PatientSecure --github-repo CosmosMigrationTest4 --aws-bucket-name bitbucket-to-gh-migration
[2023-06-14 11:57:01] [INFO] You are running the latest version of the bbs2gh extension [v0.44]
[2023-06-14 11:57:01] [INFO] ARCHIVE PATH: C:\Users\pfazio\Downloads\Bitbucket_export_7.tar
[2023-06-14 11:57:01] [INFO] AWS BUCKET NAME: bitbucket-to-gh-migration
[2023-06-14 11:57:01] [INFO] GITHUB ORG: PatientSecure
[2023-06-14 11:57:01] [INFO] GITHUB REPO: CosmosMigrationTest4
[2023-06-14 11:57:01] [INFO] SSH PORT: 22
[2023-06-14 11:57:01] [WARNING] The default behavior has changed from only queueing the migration, to waiting for the migration to finish. If you ran this as part of a script to run multiple migrations in parallel, consider using the new --queue-only option to preserve the previous default behavior. This warning will be removed in a future version.
[2023-06-14 11:57:02] [INFO] Uploading Archive to AWS...
[2023-06-14 11:57:03] [INFO] Importing Archive...
[2023-06-14 11:57:04] [ERROR] Something went wrong while executing your query. Please include `29E0:5CBA:114FE7C:235D2BC:6489E350` when reporting this issue.

This is the contents of the verbose log:

[2023-06-14 11:57:00] [DEBUG] HTTP GET: https://www.githubstatus.com/api/v2/incidents/unresolved.json
[2023-06-14 11:57:01] [DEBUG] RESPONSE (OK): {"page":{"id":"kctbh9vrtdwd","name":"GitHub","url":"https://www.githubstatus.com","time_zone":"Etc/UTC","updated_at":"2023-06-14T07:48:48.442Z"},"incidents":[]}
[2023-06-14 11:57:01] [DEBUG] HTTP GET: https://raw.githubusercontent.com/github/gh-gei/main/LATEST-VERSION.txt
[2023-06-14 11:57:01] [DEBUG] RESPONSE (OK): v0.44

[2023-06-14 11:57:01] [INFO] You are running the latest version of the bbs2gh extension [v0.44]
[2023-06-14 11:57:01] [INFO] ARCHIVE PATH: C:\Users\pfazio\Downloads\Bitbucket_export_7.tar
[2023-06-14 11:57:01] [INFO] AWS BUCKET NAME: bitbucket-to-gh-migration
[2023-06-14 11:57:01] [INFO] GITHUB ORG: PatientSecure
[2023-06-14 11:57:01] [INFO] GITHUB REPO: CosmosMigrationTest4
[2023-06-14 11:57:01] [INFO] SSH PORT: 22
[2023-06-14 11:57:01] [WARNING] The default behavior has changed from only queueing the migration, to waiting for the migration to finish. If you ran this as part of a script to run multiple migrations in parallel, consider using the new --queue-only option to preserve the previous default behavior. This warning will be removed in a future version.
[2023-06-14 11:57:02] [INFO] Uploading Archive to AWS...
[2023-06-14 11:57:03] [INFO] Importing Archive...
[2023-06-14 11:57:03] [DEBUG] HTTP POST: https://api.github.com/graphql
[2023-06-14 11:57:04] [DEBUG] HTTP BODY: {"query":"query($login: String!) {organization(login: $login) { login, id, name } }","variables":{"login":"PatientSecure"}}
[2023-06-14 11:57:04] [DEBUG] GITHUB REQUEST ID: 29E0:5CBA:114FE3C:235D20B:6489E350
[2023-06-14 11:57:04] [DEBUG] RESPONSE (OK): {"data":{"organization":{"login":"PatientSecure","id":"MDEyOk9yZ2FuaXphdGlvbjg1OTYwMzc0","name":"PatientSecure"}}}
[2023-06-14 11:57:04] [DEBUG] HTTP POST: https://api.github.com/graphql
[2023-06-14 11:57:04] [DEBUG] HTTP BODY: {"query":"mutation createMigrationSource($name: String!, $url: String!, $ownerId: ID!, $type: MigrationSourceType!) { createMigrationSource(input: {name: $name, url: $url, ownerId: $ownerId, type: $type}) { migrationSource { id, name, url, type } } }","variables":{"name":"Bitbucket Server Source","url":"https://not-used","ownerId":"MDEyOk9yZ2FuaXphdGlvbjg1OTYwMzc0","type":"BITBUCKET_SERVER"},"operationName":"createMigrationSource"}
[2023-06-14 11:57:04] [DEBUG] GITHUB REQUEST ID: 29E0:5CBA:114FE7C:235D2BC:6489E350
[2023-06-14 11:57:04] [DEBUG] RESPONSE (OK): {"data":{"createMigrationSource":null},"errors":[{"type":"INTERNAL","path":["createMigrationSource"],"locations":[{"line":1,"column":109}],"message":"Something went wrong while executing your query. Please include `29E0:5CBA:114FE7C:235D2BC:6489E350` when reporting this issue."}],"extensions":{"warnings":[{"type":"DEPRECATION","message":"The id MDEyOk9yZ2FuaXphdGlvbjg1OTYwMzc0 is deprecated. Update your cache to use the next_global_id from the data payload.","data":{"legacy_global_id":"MDEyOk9yZ2FuaXphdGlvbjg1OTYwMzc0","next_global_id":"O_kgDOBR-mtg"},"link":"https://docs.github.com"}]}}
[2023-06-14 11:57:04] [ERROR] OctoshiftCLI.OctoshiftCliException: Something went wrong while executing your query. Please include `29E0:5CBA:114FE7C:235D2BC:6489E350` when reporting this issue.
   at OctoshiftCLI.Services.GithubClient.EnsureSuccessGraphQLResponse(JObject response)
   at OctoshiftCLI.Services.GithubClient.PostGraphQLAsync(String url, Object body, Dictionary`2 customHeaders)
   at OctoshiftCLI.Services.GithubApi.CreateBbsMigrationSource(String orgId)
   at OctoshiftCLI.BbsToGithub.Commands.MigrateRepo.MigrateRepoCommandHandler.ImportArchive(MigrateRepoCommandArgs args, String archiveUrl)
   at OctoshiftCLI.BbsToGithub.Commands.MigrateRepo.MigrateRepoCommandHandler.Handle(MigrateRepoCommandArgs args)
   at OctoshiftCLI.Extensions.CommandExtensions.RunHandler[TArgs,THandler](TArgs args, ServiceProvider sp, CommandBase`2 command)
   at OctoshiftCLI.Extensions.CommandExtensions.<>c__DisplayClass1_0`3.<<ConfigureCommand>b__0>d.MoveNext()
--- End of stack trace from previous location ---
   at System.CommandLine.Invocation.AnonymousCommandHandler.InvokeAsync(InvocationContext )
   at System.CommandLine.Invocation.InvocationPipeline.<>c__DisplayClass4_0.<<BuildInvocationChain>b__0>d.MoveNext()
--- End of stack trace from previous location ---
   at System.CommandLine.Builder.CommandLineBuilderExtensions.<>c__DisplayClass17_0.<<UseParseErrorReporting>b__0>d.MoveNext()
--- End of stack trace from previous location ---
   at System.CommandLine.Builder.CommandLineBuilderExtensions.<>c__DisplayClass12_0.<<UseHelp>b__0>d.MoveNext()
--- End of stack trace from previous location ---
   at System.CommandLine.Builder.CommandLineBuilderExtensions.<>c__DisplayClass22_0.<<UseVersionOption>b__0>d.MoveNext()
--- End of stack trace from previous location ---
   at System.CommandLine.Builder.CommandLineBuilderExtensions.<>c__DisplayClass19_0.<<UseTypoCorrections>b__0>d.MoveNext()
--- End of stack trace from previous location ---
   at System.CommandLine.Builder.CommandLineBuilderExtensions.<>c.<<UseSuggestDirective>b__18_0>d.MoveNext()
--- End of stack trace from previous location ---
   at System.CommandLine.Builder.CommandLineBuilderExtensions.<>c__DisplayClass16_0.<<UseParseDirective>b__0>d.MoveNext()
--- End of stack trace from previous location ---
   at System.CommandLine.Builder.CommandLineBuilderExtensions.<>c.<<RegisterWithDotnetSuggest>b__5_0>d.MoveNext()
--- End of stack trace from previous location ---
   at System.CommandLine.Builder.CommandLineBuilderExtensions.<>c__DisplayClass8_0.<<UseExceptionHandler>b__0>d.MoveNext()

Any advice would be greatly appreciated.

Thanks!

[dylan-smith]

Best way to get help for things like this is to open a support ticket. My first guess is you don't have the feature flag enabled to allow bitbucket migrations (bitbucket migrations are currently in private beta).

If that is the case we should have a better error message (cc @timrogers )

[Paul-Fazio-Imprivata]

Thanks for the quick response! Do I open that support ticket with you for your tool, or with GitHub? Where would I find this feature flag to enable it? Is it at the org or enterprise level? I’m an owner of the org I’m trying to migrate into, but not of the enterprise level, so I’d have to get one of the enterprise level owners to enable the flag if it’s at the enterprise level. Paul Fazio Principal Release Engineer www.imprivata.com The information transmitted, including attachments, is intended only for the person(s) or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and destroy any copies of this information. [ImprivataV12018] From: Dylan Smith ***@***.***> Sent: Wednesday, June 14, 2023 12:17 PM To: github/gh-gei ***@***.***> Cc: Paul Fazio ***@***.***>; Author ***@***.***> Subject: Re: [github/gh-gei] Getting error when importing repo to GitHub (Discussion #1025) Best way to get help for things like this is to open a support ticket. My first guess was you don't have the feature flag enabled to allow bitbucket migrations (bitbucket migrations are currently in private beta). If that is the case we should have a better error message (cc @timrogers<https://github.com/timrogers> ) — Reply to this email directly, view it on GitHub<#1025 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AUP2QS2GMT46GDIOGMY5YS3XLHPWHANCNFSM6AAAAAAZGTHHJA>. You are receiving this because you authored the thread.Message ID: ***@***.******@***.***>>

[dylan-smith]

You'd open a support ticket with github. Only github staff can turn the feature flag on for you, and there is a process to get your company nominated into the private beta. @timrogers can provide more detail.

[timrogers]

Feel free to drop me an email at [email protected] and we can look at adding you to the beta!