*Description of problem - connection is proper but still it is getting listed in invalid storages. i am not sure why it is invalid storages it should be invalid connections
*The OCP platform infrastructure and deployment type (AWS, Bare Metal, VMware, etc. Please clarify if it is platform agnostic deployment), (IPI/UPI): Bare metal
*The ODF deployment type (Internal, External, Internal-Attached (LSO), Multicluster, DR, Provider, etc):5.18.2
The version of all relevant components (OCP, ODF, RHCS, ACM whichever is applicable):
RHEL
Does this issue impact your ability to continue to work with the product?
Is there any workaround available to the best of your knowledge?
Can this issue be reproduced? If so, please provide the hit rate
Can this issue be reproduced from the UI?
If this is a regression, please provide more details to justify this:
Steps to Reproduce:
1. # /usr/local/bin/noobaa-cli diagnose health --all_connection_details 2>/dev/null
{
"response": {
"code": "HealthStatus",
"message": "Health status retrieved successfully",
"reply": {
"service_name": "noobaa",
"status": "OK",
"memory": "312.6M",
"checks": {
"services": [
],
"endpoint": {
"endpoint_state": {
"response":
,
"total_fork_count": 2,
"running_workers": [
2,
1
]
},
"error_type": "TEMPORARY"
},
"config_directory_status": {
"phase": "CONFIG_DIR_UNLOCKED",
"config_dir_version": "1.0.0",
"upgrade_package_version": "5.18.0",
"upgrade_status":
},
"connections_status": {
"invalid_storages": [
],
"valid_storages": [],
"error_type": "TEMPORARY"
}
}
}
}
}
2.
3.
The exact date and time when the issue was observed, including timezone details:
Actual results:
Expected results:
Logs collected and log location:
Additional info: