IBM Support

LI81617: APIC V2018 MGMT NOT START PROPERLY

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • level=info msg="removing invite for member  www.com"
    
    level=debug msg="FQDN:\" www.com\" IP:\"169.192.xxx.xx\?
    IsOnline:true Meta:<Kind:MASTER > "
     level=info msg="hash
    mismatch, new file contents for /etc/haproxy/haproxy.cfg"
    
    level=info msg="writing file /etc/haproxy/haproxy.cfg"
    
    level=debug msg="restarting kubelet service"
    level=debug
    msg="addonsStage.Done err checking opt/cni/bin
    addonsStage.Upgrade#?checkCniBins existing(/usr/local/lib/applia
    nce-control-plane/1.16.0/opt/cni/bin/flannel) does not match
    new(/opt/cni/bin/flannel)"
    level=debug
    msg="addonsStage.Upgrade[false] "
    level=debug
    msg="upgradeManager.reconcile complete."
     {"level":"warn","ts?:?
    time?,?caller":"clientv3/retry_interceptor.go:61","msg":"retryin
    g of unary invoker failed","target":"endpoint://client-04ba922d-
    4d6e-4616-aed0-e9afaxxxxxxx/www.com:2379","attempt":0,"error":"r
    pc error: code = DeadlineExceeded desc = context deadline
    exceeded"}
    level=error msg="Error reconciling subsystem:
    context deadline exceeded"
     level=debug
    msg="upgradeManager.reconcile waiting for installation before
    starting upgrade manager"
    level=debug
    msg="upgradeManager.reconcile waiting for installation before
    starting upgrade manager"
    level=debug
    msg="upgradeManager.reconcile waiting for installation before
    starting upgrade manager"
     level=debug msg="unit
    kubelet.service not found"
     level=debug msg="systemd unit
    kubelet.service not found, searching for file to enable"
    
    level=info msg="waiting to be invited to cluster"
     level=error
    msg="Error reconciling subsystem: Cannot connect to the Docker
    daemon at unix:///var/run/docker.sock. Is the docker daemon
    running?"
    

Local fix

Problem summary

  • <span style="background-color:rgb(255, 255, 255)">If a node is
    unable to join the cluster at initial boot up and then it is
    restarted before it can join the cluster, then it will be stuck
    in an `UNKNOWN` state.</span>
    

Problem conclusion

  • This is resolved in v2018.4.1.13.
    

Temporary fix

Comments

APAR Information

  • APAR number

    LI81617

  • Reported component name

    API CONNECT ENT

  • Reported component ID

    5725Z2201

  • Reported release

    18X

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2020-07-16

  • Closed date

    2020-08-31

  • Last modified date

    2020-08-31

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    API CONNECT ENT

  • Fixed component ID

    5725Z2201

Applicable component levels

  • R18X PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSMNED","label":"IBM API Connect"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"18X","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
29 September 2021