Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CASMTRIAGE-7169 - job memory size was not getting picked up correctly from ims configuration. #139

Merged
merged 1 commit into from
Aug 29, 2024

Conversation

dlaine-hpe
Copy link
Contributor

Summary and Scope

There was a bug where the default job size settings in the ims configuration were not getting picked up correctly. This meant that all values were defaulting to 1. This fixes it so the default is applied if the user does not supply a value.

Issues and Related PRs

Testing

Tested on:

  • Mug

Test description:

I loaded the new image and verified that the correct default value is getting loaded from the ims configuration and is flowing through to the job being created.

  • Were the install/upgrade-based validation checks/tests run (goss tests/install-validation doc)? N
  • Were continuous integration tests run? If not, why? N
  • Was upgrade tested? If not, why? N
  • Was downgrade tested? If not, why? N
  • Were new tests (or test issues/Jiras) created for this change? N

Risks and Mitigations

This is a low risk bug fix.

Pull Request Checklist

  • Version number(s) incremented, if applicable
  • Copyrights updated
  • License file intact
  • Target branch correct
  • CHANGELOG.md updated
  • Testing is appropriate and complete, if applicable

@dlaine-hpe dlaine-hpe requested a review from a team as a code owner August 29, 2024 01:14
@dlaine-hpe dlaine-hpe merged commit 69a3f2f into develop Aug 29, 2024
4 checks passed
@dlaine-hpe dlaine-hpe deleted the CASMTRIAGE-7169 branch August 29, 2024 14:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants