Issues
- the restore script is not able to capture the error because the file ignores the errorBAH-1058mayur tekade
- Search box is blocked on switching among program queuesBAH-791Resolved issue: BAH-791Siva Rachakonda
- Change the java version from jre1.8.0_101 to jre1.8.0_131 in Bahmni-packageBAH-787Resolved issue: BAH-787Sravya Kanagarla
- Latest form-controls npm package changes are getting pulled into 0.91 and 0.92 artefactsBAH-785
- Patient document - Viewing patient images requires scrollingBAH-775Resolved issue: BAH-775Himabindu Akkinepalli
- Enhancement of Patient QueuesBAH-772Resolved issue: BAH-772Himabindu Thungathurty
- Appointment Times ProblemBAH-771Resolved issue: BAH-771
- bahmni-erp-connect application properties not getting overridden by system or env propertiesBAH-763Resolved issue: BAH-763Angshuman Sarkar
- Add missing privileges for Bed ManagementBAH-664Resolved issue: BAH-664Angshuman Sarkar
- Not possible to create Bed Layout without mentioning all bed detailsBAH-661Resolved issue: BAH-661Angshuman Sarkar
- Atomfeed Console api is compromisedBAH-648Resolved issue: BAH-648Himabindu Akkinepalli
- OT and Appointments module migrations are failing with base DatabaseBAH-639Resolved issue: BAH-639swathi varkala
- Ward Management Admin Console does not work if there are too many locations to loadBAH-626Resolved issue: BAH-626Angshuman Sarkar
- New BM module does not come included with a default SQL for listing patients for ward/admission locationBAH-621Resolved issue: BAH-621Angshuman Sarkar
- Append root cause to LIMS exception for better troubleshootingBAH-620Resolved issue: BAH-620Himabindu Akkinepalli
- Duplicate scheduler task configsBAH-617Resolved issue: BAH-617Himabindu Akkinepalli
- Beds are not showing up on UI if the assigned tag doesn't have a color specified in the configuration.BAH-615Resolved issue: BAH-615Himabindu Akkinepalli
- Remove ThoughtWorks name in Bahmni Atlassian WIKIBAH-614Resolved issue: BAH-614swathi varkala
- Remove ThoughtWorks name on Bahmni PagesBAH-612Resolved issue: BAH-612Shilpa Parab
- Introduce MartConcatenatedReport to support Concatenated Report for Bahmni MartBAH-608Resolved issue: BAH-608Suman Maity
- Clicking on Sync On Bahmni Connect gives an error saying "There was an unexpected issue on the server"BAH-605Resolved issue: BAH-605Angshuman Sarkar
- Not able to move lower OT Appointment to upBAH-599Resolved issue: BAH-599Saikumar Vantaku
- Create event records for Bed Tag changesBAH-598Resolved issue: BAH-598Saikumar Vantaku
- Unable to show multiple images in obsToObsFlowSheet display controlBAH-597Resolved issue: BAH-597Sudhamsh Kandukuri
- Observations display control in Visit view is taking longer time with more observationsBAH-594Resolved issue: BAH-594
- [.91 bug bash] Form import/export is failingBAH-577Resolved issue: BAH-577Himabindu Akkinepalli
- Add unique constraint for surgical appointment attribute types in OTBAH-574Resolved issue: BAH-574Saikumar Vantaku
- Inpatient report should not show inactive diagnosisBAH-571Resolved issue: BAH-571swathi varkala
- Cancel/Postpone Surgical Block functionality in OT app is not workingBAH-570Resolved issue: BAH-570Himabindu Akkinepalli
- Create events records for Bed tag map changes in BedManagementBAH-569Resolved issue: BAH-569Saikumar Vantaku
- Integrate Analytical database with Bahmni reportsBAH-567Resolved issue: BAH-567Suman Maity
- OpenMRS service startup taking lot of time in vagrant setupBAH-566Resolved issue: BAH-566swathi varkala
- default-config liquibase migrations are not appliedBAH-565Resolved issue: BAH-565Himabindu Akkinepalli
- Beds Count mismatch on new Bedmanagement appBAH-564Resolved issue: BAH-564
- Create event records for Appointment ModuleBAH-563Resolved issue: BAH-563Suman Maity
- Create event records for Operation Theater ModuleBAH-558Resolved issue: BAH-558Suman Maity
- Filter duplicate patient record from relationship searchBAH-550Resolved issue: BAH-550Suman Maity
- Add a config link to bedmanagement OWA app in Bahmni Admin moduleBAH-546Resolved issue: BAH-546Timothy Mercier
- Add dummy location in default-config to create surgical block in OT moduleBAH-540Resolved issue: BAH-540Himabindu Akkinepalli
- Form conditions are not working for inner sectionsBAH-537Resolved issue: BAH-537
- Upgrade QA instances to centos 6.9BAH-532Resolved issue: BAH-532
- bed_id in bed_location_map does not have a foreign key to table bedBAH-531Resolved issue: BAH-531Mahitha
- Not able to change the program state for some patientsBAH-529Resolved issue: BAH-529Maharjun M
- error throwing while deselecting concept in microbiology form in our implementationBAH-528Resolved issue: BAH-528
- Do not allow a bed to be deleted if it is occupiedBAH-527Resolved issue: BAH-527
- Duplicate appointments while editing an appointment in operation theatre moduleBAH-526Resolved issue: BAH-526
- BM Admin UI: Deleting a bed should not be allowed when bed is assigned to patientBAH-525Resolved issue: BAH-525
- [Audit log] Unable to view audit log messages even after giving required privilegesBAH-524Resolved issue: BAH-524
- [ELIS]The LoginList page shows the user's passwords in clear textBAH-523Resolved issue: BAH-523Dipak Thapa
- Admin Users have an ability to wipe out ELIS databaseBAH-522Resolved issue: BAH-522
50 of 107
the restore script is not able to capture the error because the file ignores the error
Description
Attachments
2
Pinned fields
Click on the next to a field label to start pinning.
Details
Assignee
mayur tekademayur tekadeReporter
mayur tekademayur tekadeLabels
Fix versions
Priority
Major
Details
Details
Assignee
mayur tekade
mayur tekadeReporter
mayur tekade
mayur tekadeLabels
Fix versions
Priority
Created July 1, 2020 at 11:23 AM
Updated May 9, 2022 at 8:49 AM
Activity
Show:
Ramashish JoshiJuly 17, 2020 at 6:35 PM
if pgrestore fails to start postgress, the restore script is not able to capture the error because the file (/opt/bahmni-installer/bahmni-playbooks/roles/pgbackrest-restore/tasks/main.yml) ignores the error. It should not ignore errors.
see below code ignore_errors is set true still it ignores errors
name: Start PostgreSQL
systemd:
name=postgresql-{{ postgres_version }}
state=started
ignore_errors: true