Unable to migrate a specific standalone project to a new Org out of 20+ projects

This website uses Cookies. Click Accept to agree to our website's cookie use as described in our Privacy Policy. Click Preferences to customize your cookie settings.

Reject

Preferences

Google Cloud
Google Workspace
AppSheet
Looker & Looker Studio
Google Cloud Security

Google Cloud Home
Cloud Forums
Groups
- Cloud FinOps and Cost Optimization Community
Learning & Certification Hub
Articles & Information
Community Resources
Cloud Events

cancel

Turn on suggestions

Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.

Showing results for

Search instead for

Did you mean:

Get hands-on experience with 20+ free Google Cloud products and $300 in free credit for new customers.

Google Cloud
Cloud Forums
Infrastructure: Compute, Storage, Networking
Unable to migrate a specific standalone project to...

Topic Options

Subscribe to RSS Feed
Mark Topic as New
Mark Topic as Read
Float this Topic for Current User
Bookmark
Subscribe
Mute
Printer Friendly Page

Solved

Unable to migrate a specific standalone project to a new Org out of 20+ projects

Posted on 04-29-2024 12:21 AM

Share this topic

Twitter

dheerajpanyam

Silver 4

Post Options

Mark as New
Bookmark
Subscribe
Mute
Subscribe to RSS Feed
Permalink
Print
Report Inappropriate Content

Reply posted on --/--/---- --:-- AM

Post Options

Mark as New
Bookmark
Subscribe
Mute
Subscribe to RSS Feed
Permalink
Print
Report Inappropriate Content

We have a use case to migrate 20+ standalone GCP projects (with no special resources like shared VPC etc so very basic resources are present in the project ) to migrate to a new Org node. Interestingly 19 projects migrated without any error and 1 specific project failed with attached error although all projects have same permissions and migrated by same user.The user who is doing the migration has owner permissions and also predefined IAM project mover role. The permission "resourcemanager.projects.update" that is shown in error below is part of the Project Mover predefined IAM role as mentioned in this link.