Skip to content
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

mojaloop/helm - HUB_PARTICIPANT.NAME in default.json is not consistent across services #2243

Closed
Tracked by #2151
shashi165 opened this issue Jun 2, 2021 · 2 comments
Assignees
Labels
bug Something isn't working or it has wrong behavior on a Mojaloop Core service infra-bug An infrastructure issue or bug such as in helm charts or documentation oss-core This is an issue - story or epic related to a feature on a Mojaloop core service or related to it
Milestone

Comments

@shashi165
Copy link

Summary:
In mojaloop/helm - at some places in default.json HUB_PARTICIPANT.NAME ='hub' is all lowercase, needs to be 'Hub'
Since in central-ledger it's 'Hub' and the participant is created with that value. Later on any service that tries to get details of Hub also needs to use 'Hub' as participant name.
Services like central-event-processor and email-notifier have 'hub' as participant name and hence they are failing with below error

2021-05-31T10:02:42.981Z - info: DfspNotificationEndpoints failed with error: StatusCodeError: 500 - {"errorInformation":{"errorCode":"2001","errorDescription":"Internal server error - Participant does not exist"}}

Severity:
Medium

Priority:
Critical - Reason - Mowali production emails are not being sent out since central-event-processor is failing

Expected Behavior
In all the default.json the HUB_PARTICIPANT.NAME should have a consistent value

Steps to Reproduce
1.
2.
3.

Specifications

  • Component (if known): mojaloop/helm
  • Version: latest
  • Platform: mojaloop
  • Subsystem:
  • Type of testing:
  • Bug found/raised by: @shashi165

Notes:

  • Severity when opened: Medium
  • Priority when opened: Critical
@shashi165 shashi165 added the bug Something isn't working or it has wrong behavior on a Mojaloop Core service label Jun 2, 2021
@elnyry-sam-k elnyry-sam-k added the oss-core This is an issue - story or epic related to a feature on a Mojaloop core service or related to it label Jun 2, 2021
@mdebarros
Copy link
Member

The issue is being addressed as part of Helm v12.1.0 release -> mojaloop/helm#436

@elnyry-sam-k elnyry-sam-k added this to the Sprint 14.3 milestone Jun 2, 2021
@elnyry-sam-k elnyry-sam-k added infra-bug An infrastructure issue or bug such as in helm charts or documentation bug Something isn't working or it has wrong behavior on a Mojaloop Core service and removed bug Something isn't working or it has wrong behavior on a Mojaloop Core service labels Jun 3, 2021
@elnyry-sam-k
Copy link
Member

@shashi165 should be fixed with https://github.com/mojaloop/helm/releases/tag/v13.0.0, please confirm when you get a chance.. (if there's an issue, please reopen)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working or it has wrong behavior on a Mojaloop Core service infra-bug An infrastructure issue or bug such as in helm charts or documentation oss-core This is an issue - story or epic related to a feature on a Mojaloop core service or related to it
Projects
None yet
Development

No branches or pull requests

3 participants