Skip to content

Releases: Cray-HPE/ims

v3.6.1 - CASMTRIAGE-4091 - add configurable application timeout value.

09 Sep 14:51
6dc0678
Compare
Choose a tag to compare
Merge pull request #39 from Cray-HPE/hotfix/CASMTRIAGE-4091

CASMTRIAGE-4091 - make gunicorn worker timeout configurable.

v3.6.0

03 Aug 13:38
cb9c69a
Compare
Choose a tag to compare

v3.5.0 - Add template arguments to recipe builds.

30 Jun 16:48
ffc3d22
Compare
Choose a tag to compare
Merge pull request #33 from Cray-HPE/release/3.5.0

v3.5.0 - publish release for ims recipe template arguments.

v3.4.11

01 Mar 16:30
75e59c0
Compare
Choose a tag to compare

Update base image to alpine v3.15

v3.4.9

17 Dec 22:25
442d54c
Compare
Choose a tag to compare

This release moves the IMS jobs off the customer-access subnet and onto the customer-management subnet.

v3.4.7

17 Dec 16:55
e18c496
Compare
Choose a tag to compare

Correct build issue with v3.4.5. No changes otherwise.

v3.4.5

16 Dec 17:07
e7667cb
Compare
Choose a tag to compare

Rollback changes that set the ownership of various mounts in IMS jobs. This release also picks up the v2.6.78 release of the ims-utils container.

v3.4.3

07 Dec 16:58
d156254
Compare
Choose a tag to compare

Refactor alpine image references

v3.4.1

19 Nov 21:45
84cef66
Compare
Choose a tag to compare

Update IMS Chart.yaml for CASM-2670 chart changes. Implement chart linting.

v3.3.69

08 Nov 21:04
d7f0bfc
Compare
Choose a tag to compare

This release of IMS fixes an issue that can lead to IMS corrupting its database. IMS previously made the assumption that each IMS recipe and image record had a unique link value. When deleting recipes and images using the IMS v3 api, IMS moves the recipe/image to the v3/deleted endpoint. If two records were deleted that had the same link value, a error condition was encountered which would cause IMS to corrupt its database.

This new version of IMS fixes this case in the following ways:

  1. If two records are deleted and each have the same link value, the deletion of the second record will no longer corrupt the IMS database.
  2. When POST-ing or PATCH-ing a recipe/image record, lMS will now perform a linear search of its database to determine if the link value being set matches an existing IMS record.