Repository navigation
fix: clean install fixes and pin mc-iam-manager v0.6.4 / mc-web-console v0.6.6 - #212
Merged
Merged
Conversation
- 로그 모드가 각 Wave를 attached(compose up)로 실행해 Wave 1에서 멈추고 이후 Wave(web-console 등)가 영영 기동되지 않던 문제 - 모든 Wave를 detached로 실행하는 run_startup_waves()로 통합, 로그 모드는 전체 기동 후 마지막에만 로그에 attach - Wave 진입점에서 닿지 않는 서비스(cost-optimizer collector/rightsizer, cb-mapui 등)를 위해 Wave 후 전체 run -d 단계 추가
- update site 다운로드 실패(Connection reset/timeout)는 예외 없이 설치 작업만 Failure로 남아, 누락된 의존 플러그인(joda-time-api 등) 때문에 재시작 후 로드 실패와 재시작 루프가 반복됨 - 플러그인별 마지막 InstallationJob이 Failure면 최대 5회 재시도, 끝내 실패하면 명시적으로 예외 발생 - 클린 설치 초기화가 약 9.5분 소요되어 기존 start_period(6m)+재시도 3회를 넘겨 unhealthy 판정 → mc-workflow-manager depends_on 실패. start_period 15m로 확대
- 루트 .env.setup의 MC_IAM_MANAGER_AWS_IDENTITY_ROLE_ARN이 계정 ID 자리에 MC_IAM_MANAGER_KEYCLOAK_DOMAIN을 참조하던 오류 수정 - mc-iam-manager/.env.setup과 동일하게 MC_IAM_MANAGER_AWS_ACCOUNT_ID 사용
- docker-compose.yaml / docker-compose.mini.yaml: mc-iam-manager 0.6.3 → 0.6.4, mc-web-console-api·front 0.6.5 → 0.6.6 - docker-compose.mini.yaml의 web 이미지를 개인 레지스트리 csescsta/*:edge에서 릴리즈 태그 cloudbaristaorg/*:0.6.6으로 통일 - web 컨테이너에 마운트되는 conf/mc-web-console/api/conf/api.yaml과 conf/api.yaml, conf/docker/api.yaml의 mc-iam-manager·mc-web-console version을 0.6.4·0.6.6으로 갱신
fix: 클린 설치 시 installAll 로그 모드 중단·Jenkins 초기화 실패 수정
chore: mc-iam-manager 0.6.4, mc-web-console 0.6.6 이미지·버전으로 고정
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
installAll.shlog mode now starts every wave, Jenkins recovers from failed plugin downloads, andMC_IAM_MANAGER_AWS_IDENTITY_ROLE_ARNuses the account id.1. Clean install fixes
installAll.shlog mode stopped after Wave 1 (bin/installAll.sh)./mcc infra run -s ...), so it stayed on Wave 1 and Waves 2–4 (including mc-web-console) never started; the web console on 3001 returned 502.run_startup_waves(). Log mode attaches to the logs only after everything is started../mcc infra run -dstep starts services that no wave entry point reaches (10 mc-cost-optimizer collectors/rightsizers, cb-mapui).Jenkins restart loop after failed plugin downloads (
conf/docker/tool/init.groovy.d/basic-security.groovy,conf/docker/docker-compose.yaml)Connection reset/Connect timed out) left the install job as Failure without raising an error. The missing dependency plugin (e.g.joda-time-api) then failed to load after restart, and Jenkins kept restarting.start_period: 6mplus 3 retries, so Jenkins was marked unhealthy and Wave 4 stopped on themc-workflow-managerdependency.start_periodis now 15m; it only suppresses failures, so a ready Jenkins still turns healthy immediately.MC_IAM_MANAGER_AWS_IDENTITY_ROLE_ARNaccount id (conf/docker/.env.setup)MC_IAM_MANAGER_KEYCLOAK_DOMAIN. It now usesMC_IAM_MANAGER_AWS_ACCOUNT_ID, matchingconf/mc-iam-manager/.env.setup.2. Pin mc-iam-manager v0.6.4 and mc-web-console v0.6.6