search

F5Networks / f5-ipam-controller

The F5 IPAM Controller runs in an orchestration environment like Kubernetes to allocate IP addresses from an IPAM system to BIG-IP Virtual Servers. The purpose is to abstract complexity related to setting up BIG-IP from a networking perspective
Apache License 2.0
9 stars 16 forks source link

FIC throws Errors after adding a new label #115

Closed subbuv26 closed 2 years ago

subbuv26 commented 2 years ago

Before you raise a new bug, please ensure you have visited the troubleshooting guide

Setup Details

FIC Version : 0.1.7
CIS Version: 2.8.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/OSCP
Orchestration Version:
Additional Setup details: <Platform/CNI Plugins/ cluster nodes/ etc>

Description

The FIC contains error log

2022/04/28 09:37:06 [ERROR] [STORE] Unable to Insert row in Table 'ipaddress_range': UNIQUE constraint failed: ipaddress_range.reference
2022/04/28 09:37:06 [ERROR] [STORE] Unable to Insert row in Table 'ipaddress_range': UNIQUE constraint failed: ipaddress_range.reference
2022/04/28 09:37:06 [ERROR] [STORE] Unable to Insert row in Table 'ipaddress_range': UNIQUE constraint failed: ipaddress_range.reference
2022/04/28 09:37:06 [ERROR] [STORE] Unable to Insert row in Table 'ipaddress_range': UNIQUE constraint failed: ipaddress_range.reference
2022/04/28 09:37:06 [ERROR] [STORE] Unable to Insert row in Table 'ipaddress_range': UNIQUE constraint failed: ipaddress_range.reference
2022/04/28 09:37:06 [ERROR] [STORE] Unable to Insert row in Table 'ipaddress_range': UNIQUE constraint failed: ipaddress_range.reference

but it works a expected, is this kinds of ERROR should be Warning level?

the fic deployment is

apiVersion: apps/v1
kind: Deployment
metadata:
  labels:
    name: f5-ipam-controller
  name: f5-ipam-controller
  namespace: bigip-ctlr
spec:
  replicas: 1
  selector:
    matchLabels:
      app: f5-ipam-controller
  template:
    metadata:
      labels:
        app: f5-ipam-controller
    spec:
      containers:
      - args:
        - --orchestration
        - kubernetes
        - --ip-range
        - '{"Dev":"172.16.3.21-172.16.3.30","Test":"172.16.3.31-172.16.3.40","Production":"172.16.3.41-172.16.3.50","Default":"172.16.3.51-172.16.3.60" } '
        - --log-level
        - INFO
        command:
        - /app/bin/f5-ipam-controller
        image: f5networks/f5-ipam-controller:0.1.7
        imagePullPolicy: IfNotPresent
        name: f5-ipam-controller
        terminationMessagePath: /dev/termination-log
        volumeMounts:
        - mountPath: /app/ipamdb
          name: samplevol
      securityContext:
        fsGroup: 1200
        runAsGroup: 1200
        runAsUser: 1200
      serviceAccount: ipam-ctlr
      volumes:
      - name: samplevol
        persistentVolumeClaim:
          claimName: pvc-local

Steps To Reproduce

1) Add a new label with a range of IP addresses in the FIC deployment 2) The controller would restart and log the above

Observations (if any)

subbuv26 commented 2 years ago

Addressed in the PR https://github.com/F5Networks/f5-ipam-controller/pull/114