Skip to content

GAZ-282 remove the bug in ph_value#125

Open
devarsh10 wants to merge 3 commits into
openMF:devfrom
devarsh10:fix/removeBugs
Open

GAZ-282 remove the bug in ph_value#125
devarsh10 wants to merge 3 commits into
openMF:devfrom
devarsh10:fix/removeBugs

Conversation

@devarsh10
Copy link
Copy Markdown
Contributor

Latest changes in mifos-gazelle were not deploying gazelle on the OCI instance. vNext deployed; Paymenthub didn't cause because Zeebe was in CrashLoopBackOff state.

Root Cause

When Phee first deployed, the cluster's network wasn't fully ready yet. The init container inside phee-zeebe-0 tried to wget the Kafka exporter JAR from mifos.jfrog.io and got "No route to host". But because the command was wget ...; ls ... (semicolon), the ls ran last and exited 0 — so Kubernetes thought the init container succeeded. The empty /exporters/ directory caused zeebe to crash on startup.

Fixes made:

  1. Changed ; to && in ph_values.yaml line 196, so a failed wget will now properly fail the init container instead of hiding silently.

Thanks!

…s_user function from phee and call wait_for_pods_ready in vnext
@devarsh10 devarsh10 changed the title fix: remove the bug in ph_value GAZ-282 remove the bug in ph_value Apr 29, 2026
@devarsh10 devarsh10 marked this pull request as ready for review May 5, 2026 19:40
@devarsh10 devarsh10 requested a review from a team May 5, 2026 19:40
@tdaly61
Copy link
Copy Markdown
Contributor

tdaly61 commented May 7, 2026

hi @devarsh10 , hey yeah I get what you are doing here now and that is a good pickup and I think we should incorporate it BUT can I get you to please update your base branch for the current dev branch which got updated yesterday. Be aware I made quite a lot of changes to the scripts as I was trying to get some coding standards because I was integrating macOS changes and the need to have this readable and maintainable increases as we increase the functionality. See PR #129 to get a feel for the changes. In fact what you might want to do because it might be easier is to close this PR then pull gazelle dev branch, make your change and then re-open a new PR with your change on top of that PR, I will merge it quickly as this is indeed needed , even though it does not always fail (for some reason).

Also please be aware this is not a full fix, you might give some thought to https://mifosforge.jira.com/browse/GAZ-184 because we actually want to get rid of the wget for the exporter.jar because it is unreliable in many ways at deploy time. cheers and thanks again

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants