GoogleCloudPlatform / GoogleCloudPlatform/database-migration-wave-orchestrator

BUG: Terraform apply in 1st time gives error

Open
#11 0 comments 0 reactions 1 assignee Claimed by @smpawar View on GitHub
bug
Dominant language
Python
Stars
13
Forks
8
PR merge metrics
No merged PRs in 30d

Description

### Description

Details of the bug:

pp_engine_service_iam_member.access_list["user:"]:
Creation complete after 5s [id=projects/[project_id]/iap_web/appengine-[project_id]/services/
default/roles/iap.httpsResourceAccessor/user:]

│ Error: Error creating Secret: Post "https://secretmanager.googleapis.com/v1/projects/[project_id]/secrets?alt=json&secretId=migsc-db-user-pass":
dial tcp [2607:f8b0:4001:c01::5f]:443: connect: cannot assign requested address

│ with module.gcp-foundation.google_secret_manager_secret.db_user_pass,
│ on modules/main.tf line 74, in resource "google_secret_manager_secret" "db_user_pass":
│ 74: resource "google_secret_manager_secret" "db_user_pass" {



│ Error: Error creating Secret: Post "https://secretmanager.googleapis.com/v1/projects/[project_id]/secrets?alt=json&secretId=migscaler-db-conn-string":
dial tcp [2607:f8b0:4001:c01::5f]:443: connect: cannot assign requested address

│ with module.gcp-foundation.google_secret_manager_secret.db_conn_string,
│ on modules/main.tf line 91, in resource "google_secret_manager_secret" "db_conn_string":
│ 91: resource "google_secret_manager_secret" "db_conn_string" {

### When do you see the bug

Issue is happening when : Executing terraform apply from the deploy/gcp-foundation throws this error.
Rerurning the apply goes fine without error.

So current workaround is to rerun it.

### Version

latest code

### Priority

priority:3

### What database engine are you seeing the problem on?

Oracle

### Relevant log output

_No response_

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.