CAIQUM-5673: Cluster addition or discovery fails in vApp due to netty version mismatch in AIQUM 9.14 RC intermittently with cloud agent enabled
- Views:
- 1,322
- Visibility:
- Public
- Votes:
- 3
- Category:
- active-iq-unified-manager
- Specialty:
- om
- Last Updated:
- 5/2/2025, 1:49:00 PM
Issue
- Acquisition fails on Active IQ Unified Manager (AIQUM) 9.14RC1
Cluster discovery failed. Rediscover the cluster after resolving the issue
au.log
indicates acquisition failure or baseline errorWARN [Thread-4] c.n.a.d.a.DataCollectorTrigger (DataCollectorTrigger.java:210) - Failed to connect to Broker, will retry shortly
INFO [Thread-3] c.o.c.u.CredentialStoreUtils (CredentialStoreUtils.java:86) - Successfully retrieved the decrypted value
ERROR [Thread-3] o.a.q.j.JmsConnection (JmsConnection.java:165) - Failed to connect to remote at: amqp://localhost:56072
WARN [Thread-3] c.n.a.d.a.DataCollectorListener (DataCollectorListener.java:186) - Failed to connect to Broker, will retry shortlyERROR [common-pool-569] c.o.s.a.f.d.BaseDataSource (DataSourceErrorException.java:244) - clustername [Error retrieving data] - Failed to send Baseline request to cluster! ([Device name General Device]: Failed to send Baseline request to cluster!)
2025-03-24 14:58:56,015 ERROR [common-pool-6244] c.o.s.a.f.d.BaseDataSource (DataSourceErrorException.java:246) - cluster-mgmt-ip [Internal error] - Failed in conversion ([Device name General Device]: Failed in conversion)
/jboss/server_acq.log
also indicates errorERROR [default task-XXXX] c.n.u.CloudAgentConnectionUtil (CloudAgentConnectionUtil.java:XXX) - Failed to establish connection for cloud agent instance "UnifiedManager_XXXXXX_XXXXXX_XXXXXXX_XXXXXXX".
- An event is seen in AIQUM's Event Management
Event: Cluster Monitoring Failed.
Monitoring failed for cluster cluster. Reason: Incorrect response from one or more Data ONTAP APIs. Contact technical support. Details: Failed to send Baseline request to cluster!