Closed chilu49 closed 4 months ago
@chilu49 Is this issue still valid.
Hi This issue is now resolved. This was due to incorrect permission on PVC/PV which was a NFS storage underneath Thanks.
On Tue, Apr 2, 2024 at 7:57 AM Trinath Somanchi @.***> wrote:
@chilu49 https://github.com/chilu49 Is this issue still valid.
— Reply to this email directly, view it on GitHub https://github.com/F5Networks/f5-ipam-controller/issues/152#issuecomment-2032281566, or unsubscribe https://github.com/notifications/unsubscribe-auth/AE7BWHVDKV7IW65VA3LC6P3Y3LBMTAVCNFSM6AAAAABETSKC46VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMZSGI4DCNJWGY . You are receiving this because you were mentioned.Message ID: @.***>
Before you raise a new bug, please ensure you have visited the troubleshooting guide
Setup Details
FIC Version : 0.1.9 CIS Version : 2.15.0
FIC Build: f5networks/f5-ipam-controller:latest CIS Build: f5networks/k8s-bigip-ctlr:latest
BIGIP Version: Big IP x.x.x
AS3 Version: 3.x
Orchestration: K8S
Orchestration Version:
Additional Setup details: <Platform/CNI Plugins/ cluster nodes/ etc>
Description
IPAM controller pod is crashing with below message unable to establish connection to DB, database is locked
Also none of loadbalancer's are getting provisioned. They are struck in pending state and the f5-cis-ctlr logs show below "skipping service '{ servicename namespace}' as its not used by any CIS monitored resource
Steps To Reproduce
1) 2) 3)
Expected Result
successfully provisioned LB with an external IP from the range allocated IPAM
Actual Result
Service struck in pending state
Diagnostic Information
Observations (if any)