Flashes (Alerts)
Abstract
Users can experience intermittent login failures on Linux based deployments. After entering valid credentials on the AIOps console login page, the page resets back to the login screen instead of navigating to the home page. Login will succeed after 1-2 retries.
This issue has been resolved in the latest aiopsctl v5.1.0 release, which was made available on 26th June.
Content
This issue may impact clients who upgraded to or installed aiopsctl version 5.1.0 prior to 26 June 2026. Clients who downloaded aiopsctl version 5.1.0 for offline installation, or performed an online installation on or after 26 June 2026, will not be affected.
Root Cause:
The root cause is due to Gateway API SessionPersistence is not being applied:
- The SessionPersistence configuration in HTTPRoutes issilently droppedduring resource creation
- Without session persistence, requests are randomly load-balanced across pods
- OIDC authentication flow breaks when login and callback requests hit different pods
Solution:
For any clients who upgraded to or installed aiopsctl version 5.1.0 prior to 26 June 2026, please perform the following steps to address the issue:
Prerequisites
- Access to the control plane node
- Cluster admin privileges
- Backup of current configuration (recommended)
Step 1: Update aiopsctl Binary
On all nodes (control plane + workers):
Download aiopsctl 5.1.0 (or later) for your architecture:
You'll find the latest aiopsctl v5.1.0 here: https://github.com/IBM/aiopsctl/releases/tag/v5.1.0
curl -LO "https://github.com/IBM/aiopsctl/releases/download/v5.1.0/aiopsctl-linux_amd64.tar.gz"- Extract and install
tar xf "aiopsctl-linux_amd64.tar.gz"
sudo mv aiopsctl /usr/local/bin/aiopsctl- Verify version
aiopsctl version
Step 2: Apply Updated CRDs
On control plane node only:
If you have a load balancer
aiopsctl server up --load-balancer-host="${LOAD_BALANCER_HOST}" --mode "${DEPLOY_TYPE}"OR If you don't have a load balancer
aiopsctl server up --mode "${DEPLOY_TYPE}"OR use existing configuration
aiopsctl server up
Step 3: Wait for Operator Update
The operator will automatically detect the updated CRDs and apply sessionPersistence configuration to HTTPRoutes in a future update. No manual intervention required.
Step 4: Verify Fix (After Operator Update)
Check HTTPRoutes have sessionPersistence configured:
kubectl get httproute -n aiops -o yaml | grep -A 10 sessionPersistenceExpected output:
sessionPersistence:
absoluteTimeout: 86400s
cookieConfig:
lifetimeType: Session
sessionName: cpaffinity
type: Cookie
status:
parents:
- conditions:
- lastTransitionTime: "2026-06-25T08:42:27Z"
message: Route is accepted
cookieConfig:
lifetimeType: Permanent
.....
Step 5: Perform Login to Concert Operate console:
Follow steps here:
https://www.ibm.com/docs/en/concert-operate/5.1.0?topic=linux-online-installation#console__title__1
The login should be successful in the first attempt without any retries.
Related Information
Historical Number
5.1.0
Product Synonym
Concert Operate/Cloud Pak for AIOps
Was this topic helpful?
Document Information
Modified date:
06 July 2026
UID
ibm17279025