[jira] [Closed] (FINERACT-1300) Needs to add init-container to check MYSQL server is up and running for Fineract server
[ https://issues.apache.org/jira/browse/FINERACT-1300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benura Abeywardena closed FINERACT-1300. Merged to develop branch > Needs to add init-container to check MYSQL server is up and running for > Fineract server > --- > > Key: FINERACT-1300 > URL: https://issues.apache.org/jira/browse/FINERACT-1300 > Project: Apache Fineract > Issue Type: Improvement >Affects Versions: 1.4.0 >Reporter: Benura Abeywardena >Assignee: Benura Abeywardena >Priority: Minor > Labels: features > Fix For: 1.5.0 > > > As Fineract-cn server accesses MYSQL container for storing MYSQL related > data, it's better to add an init-container to check whether MYSQL server is > up and running. By doing this we can reduce (barely stop) the number of > restarts done by the Fineract container -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (FINERACT-1292) Needs to add ReadinessProbe for MySql pod
[ https://issues.apache.org/jira/browse/FINERACT-1292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benura Abeywardena resolved FINERACT-1292. -- Resolution: Fixed > Needs to add ReadinessProbe for MySql pod > - > > Key: FINERACT-1292 > URL: https://issues.apache.org/jira/browse/FINERACT-1292 > Project: Apache Fineract > Issue Type: Task >Affects Versions: 1.4.0 >Reporter: Benura Abeywardena >Assignee: Benura Abeywardena >Priority: Minor > Fix For: 1.5.0 > > > In mysql deployment it's better to add ReadinessProbe which tells when the > container will be available for accepting traffic. This can be achieved by > using a command like `mysqladmin ping -u -p` to check whether > a mysql user has been properly created. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (FINERACT-1292) Needs to add ReadinessProbe for MySql pod
[ https://issues.apache.org/jira/browse/FINERACT-1292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benura Abeywardena closed FINERACT-1292. Merged to develop branch > Needs to add ReadinessProbe for MySql pod > - > > Key: FINERACT-1292 > URL: https://issues.apache.org/jira/browse/FINERACT-1292 > Project: Apache Fineract > Issue Type: Task >Affects Versions: 1.4.0 >Reporter: Benura Abeywardena >Assignee: Benura Abeywardena >Priority: Minor > Fix For: 1.5.0 > > > In mysql deployment it's better to add ReadinessProbe which tells when the > container will be available for accepting traffic. This can be achieved by > using a command like `mysqladmin ping -u -p` to check whether > a mysql user has been properly created. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (FINERACT-1300) Needs to add init-container to check MYSQL server is up and running for Fineract server
[ https://issues.apache.org/jira/browse/FINERACT-1300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benura Abeywardena resolved FINERACT-1300. -- Resolution: Fixed > Needs to add init-container to check MYSQL server is up and running for > Fineract server > --- > > Key: FINERACT-1300 > URL: https://issues.apache.org/jira/browse/FINERACT-1300 > Project: Apache Fineract > Issue Type: Improvement >Affects Versions: 1.4.0 >Reporter: Benura Abeywardena >Assignee: Benura Abeywardena >Priority: Minor > Labels: features > Fix For: 1.5.0 > > > As Fineract-cn server accesses MYSQL container for storing MYSQL related > data, it's better to add an init-container to check whether MYSQL server is > up and running. By doing this we can reduce (barely stop) the number of > restarts done by the Fineract container -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (FINERACT-1301) Need to add resource limitations to fineract & mysql deployments
[ https://issues.apache.org/jira/browse/FINERACT-1301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benura Abeywardena resolved FINERACT-1301. -- Resolution: Fixed > Need to add resource limitations to fineract & mysql deployments > > > Key: FINERACT-1301 > URL: https://issues.apache.org/jira/browse/FINERACT-1301 > Project: Apache Fineract > Issue Type: Improvement >Affects Versions: 1.4.0 >Reporter: Benura Abeywardena >Assignee: Benura Abeywardena >Priority: Major > Labels: features > Fix For: 1.5.0 > > > It's better to add resource limitations for the deployments so it will > prevent over consumption of cluster resources -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FINERACT-1306) Reporting meta-data entry not found - All reports modules
[
https://issues.apache.org/jira/browse/FINERACT-1306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Francis Guchie updated FINERACT-1306:
-
Description:
[https://ipaddress/fineract-provider/api/v1/runreports/reportCategoryList?R_reportCategory=Fund=false=true|https://diprom.biz/fineract-provider/api/v1/runreports/reportCategoryList?R_reportCategory=Fund=false=true]
One gets the response payload below
{
"developerMessage": "The requested resource is not available.",
"httpStatusCode": "404",
"defaultUserMessage": "The requested resource is not available.",
"userMessageGlobalisationCode": "error.msg.resource.not.found",
"errors": [
{
"developerMessage": "Reporting meta-data entry not found.",
"defaultUserMessage": "Reporting meta-data entry not found.",
"userMessageGlobalisationCode": "error.msg.report.name.not.found",
"parameterName": "id",
"value": null,
"args": [
{ "value": "Report Name: reportCategoryList" }
]
}
]
}
was:
[https://diprom.biz/fineract-provider/api/v1/runreports/reportCategoryList?R_reportCategory=Fund=false=true]
One gets the response payload below
{
"developerMessage": "The requested resource is not available.",
"httpStatusCode": "404",
"defaultUserMessage": "The requested resource is not available.",
"userMessageGlobalisationCode": "error.msg.resource.not.found",
"errors": [
{
"developerMessage": "Reporting meta-data entry not found.",
"defaultUserMessage": "Reporting meta-data entry not found.",
"userMessageGlobalisationCode": "error.msg.report.name.not.found",
"parameterName": "id",
"value": null,
"args": [
{
"value": "Report Name: reportCategoryList"
}
]
}
]
}
> Reporting meta-data entry not found - All reports modules
> -
>
> Key: FINERACT-1306
> URL: https://issues.apache.org/jira/browse/FINERACT-1306
> Project: Apache Fineract
> Issue Type: Bug
> Components: Reports
>Affects Versions: 1.5.0
>Reporter: Francis Guchie
>Priority: Major
> Fix For: 1.5.0
>
> Attachments: image-2021-01-27-09-41-45-780.png
>
>
> [https://ipaddress/fineract-provider/api/v1/runreports/reportCategoryList?R_reportCategory=Fund=false=true|https://diprom.biz/fineract-provider/api/v1/runreports/reportCategoryList?R_reportCategory=Fund=false=true]
> One gets the response payload below
> {
> "developerMessage": "The requested resource is not available.",
> "httpStatusCode": "404",
> "defaultUserMessage": "The requested resource is not available.",
> "userMessageGlobalisationCode": "error.msg.resource.not.found",
> "errors": [
> {
> "developerMessage": "Reporting meta-data entry not found.",
> "defaultUserMessage": "Reporting meta-data entry not found.",
> "userMessageGlobalisationCode": "error.msg.report.name.not.found",
> "parameterName": "id",
> "value": null,
> "args": [
> { "value": "Report Name: reportCategoryList" }
> ]
> }
> ]
> }
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (FINERACT-1305) Release Apache Fineract v1.5.0
[ https://issues.apache.org/jira/browse/FINERACT-1305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17272933#comment-17272933 ] bharath gowda commented on FINERACT-1305: - Thank you, Now I am able to add :) > Release Apache Fineract v1.5.0 > -- > > Key: FINERACT-1305 > URL: https://issues.apache.org/jira/browse/FINERACT-1305 > Project: Apache Fineract > Issue Type: New Feature >Reporter: Aleksandar Vidakovic >Assignee: Aleksandar Vidakovic >Priority: Major > Fix For: 1.5.0 > > > Umbrella issue for tracking all activity for this Fineract release 1.5.0 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (FINERACT-1289) Tax component not working as expected
[ https://issues.apache.org/jira/browse/FINERACT-1289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benura Abeywardena reassigned FINERACT-1289: Assignee: Benura Abeywardena > Tax component not working as expected > - > > Key: FINERACT-1289 > URL: https://issues.apache.org/jira/browse/FINERACT-1289 > Project: Apache Fineract > Issue Type: Bug > Components: Accounting, Charges >Affects Versions: 1.4.0 >Reporter: bharath gowda >Assignee: Benura Abeywardena >Priority: Major > Fix For: 1.5.0 > > Attachments: loan charge config.png, loan charge split not > happening.png, loan product config -1.png, loan product config -2.png, tax > component config.jpeg, tax group config.png > > > tax attached to the loan charge is not getting affected at the > loan/accounting level > To reproduce > 1. Create a tax component-> create a tax group with the component created. > 2. Create loan charge(any parameter, refer to the attachment for the > parameters I used) and map the tax group created. > 3. Add the charge to the loan product (with periodic accrual accounting) > enabled > 4. create/approve/disburse a loan from that loan product. > 5. Ideally the charge with the tax attached should have JE splits for charge > amount and tax amount separated. > But the tax bifurcation is not happening > > Have attached > product config screenshot, charge config screenshot, tax config screenshot, > and loan issue screenshot for more understanding > Please add a comment if you need any help > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FINERACT-1306) Reporting meta-data entry not found - All reports modules
[
https://issues.apache.org/jira/browse/FINERACT-1306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Francis Guchie updated FINERACT-1306:
-
Attachment: image-2021-01-27-09-41-45-780.png
> Reporting meta-data entry not found - All reports modules
> -
>
> Key: FINERACT-1306
> URL: https://issues.apache.org/jira/browse/FINERACT-1306
> Project: Apache Fineract
> Issue Type: Bug
> Components: Reports
>Affects Versions: 1.5.0
>Reporter: Francis Guchie
>Priority: Major
> Fix For: 1.5.0
>
> Attachments: image-2021-01-27-09-41-45-780.png
>
>
> [https://diprom.biz/fineract-provider/api/v1/runreports/reportCategoryList?R_reportCategory=Fund=false=true]
> One gets the response payload below
> {
> "developerMessage": "The requested resource is not available.",
> "httpStatusCode": "404",
> "defaultUserMessage": "The requested resource is not available.",
> "userMessageGlobalisationCode": "error.msg.resource.not.found",
> "errors": [
> {
> "developerMessage": "Reporting meta-data entry not found.",
> "defaultUserMessage": "Reporting meta-data entry not found.",
> "userMessageGlobalisationCode": "error.msg.report.name.not.found",
> "parameterName": "id",
> "value": null,
> "args": [
> {
> "value": "Report Name: reportCategoryList"
> }
> ]
> }
> ]
> }
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (FINERACT-1306) Reporting meta-data entry not found - All reports modules
[
https://issues.apache.org/jira/browse/FINERACT-1306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17272714#comment-17272714
]
Francis Guchie commented on FINERACT-1306:
--
!image-2021-01-27-09-41-45-780.png!
> Reporting meta-data entry not found - All reports modules
> -
>
> Key: FINERACT-1306
> URL: https://issues.apache.org/jira/browse/FINERACT-1306
> Project: Apache Fineract
> Issue Type: Bug
> Components: Reports
>Affects Versions: 1.5.0
>Reporter: Francis Guchie
>Priority: Major
> Fix For: 1.5.0
>
> Attachments: image-2021-01-27-09-41-45-780.png
>
>
> [https://diprom.biz/fineract-provider/api/v1/runreports/reportCategoryList?R_reportCategory=Fund=false=true]
> One gets the response payload below
> {
> "developerMessage": "The requested resource is not available.",
> "httpStatusCode": "404",
> "defaultUserMessage": "The requested resource is not available.",
> "userMessageGlobalisationCode": "error.msg.resource.not.found",
> "errors": [
> {
> "developerMessage": "Reporting meta-data entry not found.",
> "defaultUserMessage": "Reporting meta-data entry not found.",
> "userMessageGlobalisationCode": "error.msg.report.name.not.found",
> "parameterName": "id",
> "value": null,
> "args": [
> {
> "value": "Report Name: reportCategoryList"
> }
> ]
> }
> ]
> }
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (FINERACT-1306) Reporting meta-data entry not found - All reports modules
Francis Guchie created FINERACT-1306:
Summary: Reporting meta-data entry not found - All reports modules
Key: FINERACT-1306
URL: https://issues.apache.org/jira/browse/FINERACT-1306
Project: Apache Fineract
Issue Type: Bug
Components: Reports
Affects Versions: 1.5.0
Reporter: Francis Guchie
Fix For: 1.5.0
[https://diprom.biz/fineract-provider/api/v1/runreports/reportCategoryList?R_reportCategory=Fund=false=true]
One gets the response payload below
{
"developerMessage": "The requested resource is not available.",
"httpStatusCode": "404",
"defaultUserMessage": "The requested resource is not available.",
"userMessageGlobalisationCode": "error.msg.resource.not.found",
"errors": [
{
"developerMessage": "Reporting meta-data entry not found.",
"defaultUserMessage": "Reporting meta-data entry not found.",
"userMessageGlobalisationCode": "error.msg.report.name.not.found",
"parameterName": "id",
"value": null,
"args": [
{
"value": "Report Name: reportCategoryList"
}
]
}
]
}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
