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

[patch] Fix default value for --manage-components #1072

Merged
merged 1 commit into from
Jun 28, 2024
Merged

[patch] Fix default value for --manage-components #1072

merged 1 commit into from
Jun 28, 2024

Conversation

durera
Copy link
Contributor

@durera durera commented Jun 28, 2024

The default value for --manage-components is set to base=latest;health=latest rather than base=latest,health=latest. This will manifest in an install failure if the user installs using the non-interactive mode and accepts the default:

TASK [ibm.mas_devops.suite_app_config : Configure application in workspace] ****
fatal: [localhost]: FAILED! => changed=false
error: 400
msg: 'ManageWorkspace djptest-ws1: Failed to create object: b''{"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"admission webhook \\"vmanage.ibm.com\\" denied the request: Maximo Manage version latest;health is not compatible with Manage version latest;health. Select a version that is compatible with Manage version latest;health. To learn more, review the Manage application compatibility report.","code":400}\n'''
reason: Bad Request
status: 400

@durera durera merged commit 8c4da94 into master Jun 28, 2024
2 checks passed
@durera durera deleted the mngfix branch June 28, 2024 16:39
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.

1 participant