[Important] Bahmni Release repo migration

Hello All,

With JFrog Bintray services being deprecated from Today 1 May 2021, we have migrated our repos. Right now they are hosted at our AWS S3, and in a few days we will try to deliver through AWS CloudFront as well.

Bahmni. 0.93 is going to come bundled with the repo pointing to the new locations, but if you are trying to get any older version of Bahmni (e.g. 0.91 or 0.92), then please be advised that you need to follow the following steps.

  1. in /etc/bahmni-installer/setup.yml, update/add the following configuration

bahmni_repo_url: http://repo.mybahmni.org/releases/

2.While installing, you need to mention the ansible installer

bahmni -i local -aru http://repo.mybahmni.org/releases/ansible-2.4.6.0-1.el7.ans.noarch.rpm install

All other pre-requisites and instructions remain the same. e.g. zlib, epel-release, Click etc

6 Likes

attn: @arjun @mksrom @ramashish @shivarachakonda @binduak @swetha184 @laxman @sushilp @sushmit @vmalini @akhilmalhotra @dipakthapa @ramashish @pradipta @rrameshbtech @mddubey @iadksd @michaelbontyes @buvaneswariarun @praveenad @sanjayap @apaule @som.bhattacharyya @tejakancherla @rabbott @gsluthra @nidhro @rakib @mwelazek @mozzy @tapologo @mksd @apuda @tarunshettygari @praveenad

4 Likes

Thanks so much for this vital information @angshuonline

I tried installing 0.93-105 with above instruction

“No package matching ‘bahmni-emr-0.93-95’ found available”

@angshuonline I am not sure why, but the bahmni installer rpm downloaded from S3 cannot be installed.

$ wget http://repo.mybahmni.org.s3.amazonaws.com/releases/bahmni-installer-0.92-155.noarch.rpm
$ rpm -ivh bahmni-installer-0.92-155.noarch.rpm
error: bahmni-installer-0.92-155.noarch.rpm: tag[42]: BAD, tag 1096 type 5 offset 31312 count 500 len 2000
error: bahmni-installer-0.92-155.noarch.rpm cannot be installed
$ rpm --checksig bahmni-installer-0.92-155.noarch.rpm

bahmni-installer-0.92-155.noarch.rpm:error: bahmni-installer-0.92-155.noarch.rpm: tag[42]: BAD, tag 1096 type 5 offset 31312 count 500 len 2000

Just tried that @vinay Not getting the above error. Also many have been trying with the new repo. What OS version are you trying this on?

@angshuonline Thanks for the update. I was on Centos 8.x, thats probably why. I will downgrade OS and verify.

Btw, if you want to try out the 0.93-beta, then make sure your repo points to

bahmni_repo_url: http://repo.mybahmni.org/rpm/bahmni

@angshuonline @buvaneswariarun This wiki documentation needs updating, it still refers to the old repo

Done. Thanks for letting us know

I am trying to install 0.93-105 Beta, and my repo is pointing to http://repo.mybahmni.org/rpm/bahmni, I am getting “No package matching ‘bahmni-emr-0.93-95’ found available” error. Please verify this with 0.93-105

the package is available at the location. I installed 0.93 yesterday, so it should work. Try putting a trailing slash

bahmni_repo_url: http://repo.mybahmni.org/rpm/bahmni/

1 Like

No HTTPS repo available?

Hi all, @angshuonline

I am a bit surprised to see that in 2021, given the general availability of free and fully-automated CAs, we still put websites online without TLS. This is doubly worrying when said website is a repository for delivering code.

I would have a hard time explaining to anyone reviewing my deployment scripts, that I am downloading code that will be run in our production environments, and dealing with very sensitive medical data, over an unsecured connection.

Can this please be reconsidered ASAP?

Thanks for your consideration, Ramses

@ramses agree.

  1. we do have a TLS URL for the S3 repo but little convoluted
  2. to resolve the above, we had used route53, and used letsEncrypt. but we need to renew frequently.
  3. we are trying to make some changes like serving through cloudfont and leveraging the CDN to allow faster downloads. We have a https endpoint on cloudfront, but unfortunately we can’t retain the same repo.bahmni, and a random subdomain is given. There are some workarounds, and thats what we are trying to resolve.

Give us a few days, if we can’t configure cloudfront URL, we will just go ahead with the older approach.

@angshuonline great news, thanks!

Regarding LE, the renewal should happen automatically, if you use Route53, you should be able to use DNS challenges to have LE automatically validate your domain.

I have some experience with this, don’t hesitate contacting me directly if needed.

Cheers and thanks for your efforts! Ramses

@ramses sure thanks, will reach out if we need. My pref would be to use cloudfront, it can significantly bring down the download time.

Hi All, Bahmni repos are now available over HTTPS.

Please do as applicable in your cases.

  • update repo URL in “/etc/yum.repos.d/bahmni.repo” - update baseurl to https scheme

baseurl=https://repo.mybahmni.org/releases/

  • setup.yml - if you have overridden the repo URL, please change to HTTP in /etc/bahmni-installer/setup.yml file - “bahmni_repo_url” value
  • Ansible can be downloaded through the bahmni command itself, and If you are using 0.92, then please use as

bahmni -i local -aru https://repo.mybahmni.org/releases/ansible-2.4.6.0-1.el7.ans.noarch.rpm install

the repo is available over https://repo.mybahmni.org but it is not browse-able yet. So if you want to check what is available on the repo you can use the S3 static URL

1 Like

@angshuonline Bahmni 0.93-168 failing on Postgres

“Failure talking to yum: failure: repodata/repomd.xml from pgdg-common: [Errno 256] No more mirrors to try.\nhttps://download.postgresql.org/pub/repos/yum/common/redhat/rhel-7-x86_64/repodata/repomd.xml: [Errno -1] repomd.xml signature could not be verified for pgdg-common”}

bahmni_repo_url: http://repo.mybahmni.org/rpm/bahmni/ and running this command

bahmni -i local -aru http://repo.mybahmni.org/releases/ansible-2.4.6.0-1.el7.ans.noarch.rpm install

Even tried with changing the base_url.

hmmm … Its weird. Because on the lastest build it has been changed to the path as metioned in postgers install guide you can see here

And both our QA instances actually have the changes.

Did you change any files under " /opt/bahmni-installer/bahmni-playbooks/"? or override setup.yml with the below variables?

> postgres_repo_rpm_name: pgdg-redhat-repo-latest.noarch.rpm
> postgres_repo_download_url: https://download.postgresql.org/pub/repos/yum/reporpms/EL-7-x86_64/{{postgres_repo_rpm_name}}

We will take another deployment tonight on QA03 … will keep an eye.