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

Issue while trying to install IOT using ibm.mas_devops.suite_app_install role #1468

Open
sonukumar0205 opened this issue Sep 13, 2024 · 1 comment
Labels
Bug Report Something isn't working Product Defect Defect with MAS (or it's dependencies) beyond the control of the Ansible collection itself Triage Issue was triaged and acknowledged

Comments

@sonukumar0205
Copy link

Collection version

ibm.mas_devops 22.3.2

Environment information

quay.io/ibmmas/cli 10.8.0

What happened?

We are trying to install IOT on AWS ROSA Classic (OpenShift v4.14.34) but when trying to run ibm.mas_devops.suite_app_install role always getting error: message: |-unknown playbook failure ServiceVerificationFailed: IoT Deployment auth-auth-store does not have minimum availability

Because of this error it is not proceeding further and at the end we get message that IoT operator is failed. We have checked the machines nodes (Master:3 and Worker: 10) and it is sufficient.
ibm-mas-iot-operator-5c4d646f76-77469-manager.log

Is there any changes we need to do while installing IOT on AWS ROSA environment?

Relevant log output

Few portion of IOT-Operator logs:
--------------------------- Ansible Task StdOut -------------------------------

 TASK [Debug required variables] ******************************** 
�[0;32mok: [localhost] => {�[0m
�[0;32m    "msg": [�[0m
�[0;32m        "instanceId ........... rosa",�[0m
�[0;32m        "coreNamespace ........ mas-rosa-core",�[0m
�[0;32m        "appNamespace ......... mas-rosa-iot",�[0m
�[0;32m        "clientCertFile ....... /tmp/mas/certs/client/tls.crt",�[0m
�[0;32m        "clientKeyFile ........ /tmp/mas/certs/client/tls.key",�[0m
�[0;32m        "serverCAFile ......... /tmp/mas/certs/ca.crt",�[0m
�[0;32m        "cr ................... {'apiVersion': 'iot.ibm.com/v1', 'kind': 'IoT', 'name': 'rosa', 'currentStatus': {'components': {'actions': {'podTemplates': []}, 'auth': {'podTemplates': []}, 'datapower': {'podTemplates': []}, 'devops': {'podTemplates': []}, 'dm': {'podTemplates': []}, 'dsc': {'podTemplates': []}, 'edgeconfig': {'podTemplates': []}, 'fpl': {'podTemplates': []}, 'guardian': {'podTemplates': []}, 'mbgx': {'podTemplates': []}, 'mfgx': {'podTemplates': []}, 'monitor': {'podTemplates': []}, 'orgmgmt': {'podTemplates': []}, 'provision': {'podTemplates': []}, 'registry': {'podTemplates': []}, 'state': {'podTemplates': []}, 'webui': {'podTemplates': []}}, 'conditions': [{'lastTransitionTime': '2024-09-13T11:12:11Z', 'message': 'IoT Deployment auth-auth-store does not have minimum availability', 'reason': 'ServiceVerificationFailed', 'status': 'False', 'type': 'Ready'}, {'ansibleResult': {'changed': 89, 'completion': '2024-09-13T11:12:11.345832', 'failures': 1, 'ok': 544, 'skipped': 275}, 'lastTransitionTime': '2024-09-13T11:12:11Z', 'message': 'unknown playbook failure\\nServiceVerificationFailed: IoT Deployment auth-auth-store does not have minimum availability', 'reason': 'Failed', 'status': 'True', 'type': 'Failure'}, {'lastTransitionTime': '2024-09-13T11:12:11Z', 'message': '', 'reason': '', 'status': 'False', 'type': 'Successful'}, {'lastTransitionTime': '2024-09-13T11:12:11Z', 'message': 'Running reconciliation', 'reason': 'Running', 'status': 'True', 'type': 'Running'}], 'milestones': {'installed': {'anonymousId': 'b4e6371c-d9a1-4d63-a217-5535d3ef6fe4', 'timestamp': '2024-09-13T10:43:43.995947+00:00', 'transactionId': 'TransactionID Not Applicable for DRO'}}, 'podTemplates': [], 'settings': {'manualCertMgmt': False}}}"
@sonukumar0205 sonukumar0205 added the Bug Report Something isn't working label Sep 13, 2024
@whitfiea whitfiea added the Product Defect Defect with MAS (or it's dependencies) beyond the control of the Ansible collection itself label Oct 31, 2024
@whitfiea
Copy link
Contributor

@sonukumar0205 This error would indicate that the auth-store pod can't be started. Can you see if that pods in the iot namespace to see if this pod exists and if it is has logs to show why it might not be fully starting? This pod uses db2 so it might be an issue there.

@whitfiea whitfiea added the Triage Issue was triaged and acknowledged label Oct 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Report Something isn't working Product Defect Defect with MAS (or it's dependencies) beyond the control of the Ansible collection itself Triage Issue was triaged and acknowledged
Projects
None yet
Development

No branches or pull requests

2 participants