-
Notifications
You must be signed in to change notification settings - Fork 56
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
Cloud Build module in bootstrap fails on CSR clone gcloud API auth during push-to-repo.sh for CB trigger creation on particular client - use ssh key and ssh-agent #431
Comments
retest main 20240509
|
|
raised #434 increasing quota |
rerun apply tomorrow
|
Did some testing last night on a clean main for my oldev org - as well as local CSR cloning - both good. From the script in https://github.com/GoogleCloudPlatform/pbmm-on-gcp-onboarding/blob/main/0-bootstrap/scripts/push-to-repo.sh#L32 details in local clone
module.bootstrap_csr_repo.null_resource.run_command[0] (local-exec): + '[' 3 -lt 3 ']'
|
Finish retest 0-bootstrap
ran on older bootstrap project - but all good |
addresses #434 |
An example of an attempted gcloud csr clone will kick in the authentication dialog
Client after re-authentication " from #429 close but not related (local sdk) https://groups.google.com/g/google-cloud-dev/c/fpaCcI6Bulg |
SSH workaround for CSR
Clone
|
Use the default id_rsa key name
register key with CSR
procedure on #440 |
gcloud api is the same as another working org also verify ssh-agent - working on my cloudshell
|
SSH main retrofit - option to cloud repos API authenticationusing ssh-agent
branch
edit tfvars
downgrade terraform
terraform init and plan
1036 expected eventually consistent error on group creation after 1 min
restarting 1042 plan and apply 2
raised #443 continuing
raised #444 |
getting expected cb worker pool quota error
switching region
cannot because of kms lifecycle
switch only on the pool in cb.tf
1102
72 add, 1 cb pool to destroy
replan/apply - to check that the older cb pool subnet is deleted - as creation/deletion was done in parallel
apply
I broke the triggers - they point to the older regions fix the trigger
will use us-east4 for now |
No time - delete both projects, tfstate and restart with us-east4 just in time - quota approved
revert to nane1 default region - plan / apply
no subnets replan Plan: 1 to add, 0 to change, 0 to destroy.
|
proceed 0-bootstrap
clone using ssh
2nd repo
I forgot to change the API in the script push-to-repo.sh - no SSH test done
|
continued
free some 5g space
switch region on cloud build |
retest using tef-oldev4 and us-east4
|
rerun as 5
terraform apply
edit push-to-repo-sh git clone ssh://michael@[email protected]:2022/p/prj-b-cicd-1oi4/r/gcp-bootstrap
expected errors on the not required credential helper - will fix later
1244 forgot to use the repo variable
adjusting script
dont need
working
remember #gcloud source repos clone gcp-policies --project=${cloudbuild_project_id} |
This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 7 days |
Pending to check
Todo
Status
https://github.com/GoogleCloudPlatform/pbmm-on-gcp-onboarding/wiki/DevOps#authenticate-a-local-cloud-shell
check a 2nd super admin account
Cloud shell optional workaround - use local shell (OSX, or google/cloud-sdk docker container on windows - see Windows amd64/ia64 local gcloud client support: terraform apply via ming64/git-bash tested - expected win32 issue running bootstrap module check_env.sh works only inside docker container (ubuntu or google/cloud-sdk) - or use cloud shell #429
Client Issue - Cloud Build module in bootstrap fails on CSR clone auth during push-to-repo.sh for CB trigger creation
Reproduction
triage reference - full run in 360 and 421
full run Canadian Public Sector Secure PBMM Landing Zone reference using Terraform 1.6 (for now 1.3.10) based on the PSO/TOC ready TEF V4 - Full clean organization deployment with mitigation/automation/parameterization modifications #360
last main ci/cid Replace/revert-back CB/CSR options as we add local terraform and ado (399) options - to be able to use CB/CSR as a current option while we retrofit #421
see normal session timeout for 360 run in Canadian Public Sector Secure PBMM Landing Zone reference using Terraform 1.6 (for now 1.3.10) based on the PSO/TOC ready TEF V4 - Full clean organization deployment with mitigation/automation/parameterization modifications #360 (comment)
triage separate system oldev
triage client
Workaround
Historical reference on region restriction:
The text was updated successfully, but these errors were encountered: