Release Reference Application modules for 2.4 release

Reference application 2.4 release is in the final stages before release to UAT.

The following modules need to be released

  1. referencemetadata
  2. referencedemodata
  3. coreapps
  4. referenceapplication and Reference Application 2.4 release issue updated. This thread can also be updated.

Note referencemetadata has a pull request with the final CIEL release which must be merged before release.

@burke and @darius are keen to see ref app 2.4 released to UAT shortly so this is of immediate need.

@maurya, can you note that this is a potential blocker on release of ref app 2.4 to UAT.

Hello @jdegraft,

As mentioned in the other talk post,[quote=“jdegraft, post:1, topic:6144”] Reference Application 2.4 release issue [/quote] should not be an issue.

Also, you should setup UAT with unreleased versions for the 4 modules you mentioned. If any issues are identified in UAT, they need to be handled before releasing the 4 modules (as releasing the 4 modules will make 2.4 released).

The pull request can be merged while UAT is ongoing.

FWIW i merged the pull request.

We should be able to release Core Apps, though, right? (I agree that referencemetadata, referencedemodata, and referenceapplication should wait.)

1 Like

Okay I will release coreapps and the ref app 2.4 to UAT. CI is already setup ready to go.

Correct. I have included them in the list by mistake.

Releasing coreapps sounds good.

In case of Ref App 2.4 to UAT, I Just want you to make sure referencemetadata, referencedemodata, and referenceapplication are not released as it might create issues with version numbering and we might have to release 2.4.1 at the time of final release. Otherwise, it sounds good to me.

@jdegraft, Thank you for leading us through the release process. I know it involved a lot of your hard work and effort in dealing with the issues that came up during the release process.

I’m not able to pull up nor SSH into that box. Are we waiting on help desk support? Or are is anyone else able to SSH into the machine?

This is the last error message that @jdegraft reported to me on IRC before i told him to try helpdesk:

Ah. Looks like the same problem I’m seeing: unable to SSH into that VM.

@dkayiwa, @jdegraft – please confirm that a help desk ticket has been created, they understand the priority, and check in on status daily. Thanks! If you have not heard anything from the help desk within 24 hours, then please let us know here.

A help desk ticket has been created last week. I am still waiting for the fix.

@jdegraft, please reply to that help desk ticket (CC’ing myself & @dkayiwa) stating this is a blocker for Reference Application 2.4 release, any help on restoring SSH access to uat02 would be appreciated (including completely resetting the VM). If the help desk is blocked – i.e., they are stuck waiting on the VM host to take action – then we can ask them to elevate that ticket and, in the meantime, look elsewhere for a temporary solution (e.g., I could pay for a digital ocean VM and have the help desk point to it until uat02 can be fixed).

Help desk says uat02 is not meant to support ssh.

It is not clear that uat02 can be setup for CI deployment. Some guidance on how to deploy ref app 2.4 to uat02 is needed.

This is still a blocker on ref app 2.4 release to UAT.

Hey there all – please keep in mind that the help desk is not paid and are entirely volunteer – so please keep in that in mind and set your expectations accordingly. You won’t get immediate action – sorry about that. Beyond this, I do not know. According to a document I found, I don’t know if resources have been assigned for uat02. This link requires that you use your OpenMRS email address.

@michael or @ryan can comment farther.

Thanks @r0bby. I was confused because we’ve had a uat02 in the past (must have been reclaimed) and both and respond to ping requests.

I’ve submitted a new help desk request (#27784) asking that devtest05 be reclaimed (re-assigned from @surangak to @maurya) to be used for uat.

What we need most is a target for UAT for the reference application. So, in decreasing order of importance:

  1. SSH + sudo access for @jdegraft and our CI server.
  2. Point to the machine.
  3. SSH + sudo access for others to help @jdegraft.
  4. Rename devtest05 → uat02.

#1 is the what we could use most.

I am not sure it will get done immediately. I have to pack for OSCON and would rather not be doing this while in Austin.

Ack! It looks like I’ve got two requests in to the help desk that conflict:

  • Need QA for platform [#27438] on May 2nd, asking to convert devtest05 to qa02 (aka qa-platform)

  • UAT for reference application [#27784] on May 12th, asking convert devtest05 to uat02 (aka uat-refapp)

@raff, per this page, you are using two devtest servers. Which of these would you like to give up to be recommissioned as qa-platform?

I’ll send you and @surangak my public key, so you can add an account for me as sudoer and we can move forward while the help desk volunteers are busy with other things.

We’ll use devtest05 as uat-refapp and whichever of these two you need least for qa-platform (I’ll update help desk ticket #27438 accordingly).

Actually, @helpdesk, can we please re-title some of the assignments listed here so they are easier to understand? (GW89) - Rafal Korytkowski (Metadata Sharing Builder)

Assuming this is the server, this should be assigned to “Reference Application Team” and its title should be “Metadata Builder for Reference Application” (GW152) - Maurya Kummamuru (OpenMRS Reference Application 2.2 Testing)

This should be unassigned. Reference Application 2.2 was released in April 2015 – this was the UAT server we used for the release candidate, and it hasn’t been used for this purpose since April 2015.

@burke, to be explicit, assuming that the helpdesk assignments article we’re referring to is up-to-date, (GW152) should be free to commandeer, and we don’t need to touch devtest00 or devtest04 (for this purpose).

I’m just going to be explicit – a large chunk of the infra team is going to be in Austin for OSCON, and I believe @ryan is away. @maany is busy and perhaps recovering from exams. So unless a server goes down, ro something like that, this is going to have to wait. Sorry. If you want this to not fall through the cracks, ping one of the open cases for this issue.

I confirm that I no longer need (GW152) to be assigned to me