F5 DSSM Upgrade (f5-dssm-upgrader) Log Message ListΒΆ
| ID Number | Description |
| 06200000 | Started log level watcher (PID: $LOGLEVEL_WATCHER_PID) monitoring $LOGLEVEL_FILE |
| 06200001 | master_ip is $master_ip |
| 06200002 | THIS IS THE MASTER NAME FUNC |
| 06200003 | executed kubectl command |
| 06200004 | THE VERSION USED BY $db_svc-$i is $(cat $dssm_version | head -n 1) |
| 06200005 | WAITING FOR $1 POD TO COME UP |
| 06200006 | Initiating failover... |
| 06200007 | Failover successful on attempt $attempt |
| 06200008 | Failover unsuccessful on attempt $attempt |
| 06200009 | UPGRADING SENTINELS |
| 0620000a | Namespace is $namespace |
| 0620000b | dssm-upgrade-hook IS RUNNING |
| 0620000c | $sentinel_svc-$i IS RUNNING |
| 0620000d | GETTING THE MASTER DB IP |
| 0620000e | THE MASTER IP IS $master_ip_old |
| 0620000f | GETTING THE REDIS IMAGE USED BY THE CURRENT DB PODS |
| 06200010 | dssm-db-$i ip: $dssm_db_ip, db_svc-$i: $db_svc-$i |
| 06200011 | DELETED THE NON MASTER DB POD $db_svc-$i |
| 06200012 | THE MASTER POD NAME BEFORE FAILOVER IS $master_pod_name |
| 06200013 | GETTING THE REDIS IMAGE VERSION IN THE UPGRADED DSSM PODS |
| 06200014 | GETTING THE NEW MASTER DB IP |
| 06200015 | New master IP: $master_ip_new, Old master IP: $master_ip_old |
| 06200016 | DELETING THE OLD REDIS MASTER DB POD $master_pod_name |
| 06200017 | THE DSSM VERSION OF $master_pod_name |
| 06200018 | DELETING THE SENTINEL POD $sentinel_svc-$i |
| 06200019 | DELETED THE SENTINEL POD $sentinel_svc-$i |
| 0620001a | DONE UPGRADING |
| 0620001b | Deleting upgrade hook pod |
Log Message Details
06200000 : Started log level watcher (PID: $LOGLEVEL_WATCHER_PID) monitoring $LOGLEVEL_FILE
sev:
Info
Type:
Application
args:
- LOGLEVEL_FILE
- LOGLEVEL_WATCHER_PID
cause:
Log level watcher started successfully
workaround:
Verify watcher process is running if logs are not filtered correctly
06200001 : master_ip is $master_ip
sev:
Info
Type:
Application
args:
- master_ip
cause:
Master IP address extracted from sentinel
workaround:
N/A
06200002 : THIS IS THE MASTER NAME FUNC
sev:
Debug
Type:
Application
args:
N/A
cause:
Identifying master database pod by IP address
workaround:
N/A
06200003 : executed kubectl command
sev:
Debug
Type:
Application
args:
N/A
cause:
Executed kubectl command to find master pod
workaround:
N/A
06200004 : THE VERSION USED BY $db_svc-$i is $(cat $dssm_version | head -n 1)
sev:
Info
Type:
Application
args:
- db_svc
- dssm_version
- i
cause:
Retrieved image version for database pod
workaround:
N/A
06200005 : WAITING FOR $1 POD TO COME UP
sev:
Info
Type:
Application
args:
N/A
cause:
Waiting for pod to reach running state
workaround:
N/A
06200006 : Initiating failover...
sev:
Info
Type:
Application
args:
N/A
cause:
Initiating Redis sentinel failover
workaround:
N/A
06200007 : Failover successful on attempt $attempt
sev:
Info
Type:
Application
args:
- attempt
cause:
Sentinel failover completed successfully
workaround:
N/A
06200008 : Failover unsuccessful on attempt $attempt
sev:
Warning
Type:
Application
args:
- attempt
cause:
Sentinel failover command did not return OK
workaround:
Check sentinel connectivity and cluster state, retry in progress
06200009 : UPGRADING SENTINELS
sev:
Info
Type:
Application
args:
N/A
cause:
WAIT TILL DSSM-HOOK AND ALL SENTINELS ARE DELETED AND UP AGAIN
workaround:
N/A
0620000a : Namespace is $namespace
sev:
Info
Type:
Application
args:
- namespace
cause:
Kubernetes namespace identified for upgrade
workaround:
N/A
0620000b : dssm-upgrade-hook IS RUNNING
sev:
Info
Type:
Application
args:
N/A
cause:
Upgrade hook pod is running and ready
workaround:
N/A
0620000c : $sentinel_svc-$i IS RUNNING
sev:
Info
Type:
Application
args:
- i
- sentinel_svc
cause:
Sentinel pod is running and ready
workaround:
N/A
0620000d : GETTING THE MASTER DB IP
sev:
Info
Type:
Application
args:
N/A
cause:
GET MASTER IP ADDRESS
workaround:
N/A
0620000e : THE MASTER IP IS $master_ip_old
sev:
Info
Type:
Application
args:
- master_ip_old
cause:
Current master database IP before upgrade
workaround:
N/A
0620000f : GETTING THE REDIS IMAGE USED BY THE CURRENT DB PODS
sev:
Info
Type:
Application
args:
N/A
cause:
Checking Redis image version on database pods
workaround:
N/A
06200010 : dssm-db-$i ip: $dssm_db_ip, db_svc-$i: $db_svc-$i
sev:
Debug
Type:
Application
args:
- db_svc
- dssm_db_ip
- i
cause:
Database pod IP address retrieved
workaround:
N/A
06200011 : DELETED THE NON MASTER DB POD $db_svc-$i
sev:
Info
Type:
Application
args:
- db_svc
- i
cause:
Deleted non-master database pod for upgrade
workaround:
N/A
06200012 : THE MASTER POD NAME BEFORE FAILOVER IS $master_pod_name
sev:
Info
Type:
Application
args:
- master_pod_name
cause:
Identified current master pod, will upgrade after failover
workaround:
N/A
06200013 : GETTING THE REDIS IMAGE VERSION IN THE UPGRADED DSSM PODS
sev:
Info
Type:
Application
args:
N/A
cause:
NOW SINCE NON MASTER DB PODS CAME UP WITH NEW F5-DSSM VERSION CHECK THE f5-dssm version on them
workaround:
N/A
06200014 : GETTING THE NEW MASTER DB IP
sev:
Info
Type:
Application
args:
N/A
cause:
AFTER FAILOVER GET THE NEW DSSM DB IP
workaround:
N/A
06200015 : New master IP: $master_ip_new, Old master IP: $master_ip_old
sev:
Info
Type:
Application
args:
- master_ip_new
- master_ip_old
cause:
Master IP changed after sentinel failover
workaround:
N/A
06200016 : DELETING THE OLD REDIS MASTER DB POD $master_pod_name
sev:
Info
Type:
Application
args:
- master_pod_name
cause:
AFTER FAILOVER DELETE THE OLD MASTER DB POD
workaround:
N/A
06200017 : THE DSSM VERSION OF $master_pod_name
sev:
Info
Type:
Application
args:
- master_pod_name
cause:
Upgraded former master pod is now running
workaround:
N/A
06200018 : DELETING THE SENTINEL POD $sentinel_svc-$i
sev:
Info
Type:
Application
args:
- i
- sentinel_svc
cause:
Deleting sentinel pod to upgrade to new version
workaround:
N/A
06200019 : DELETED THE SENTINEL POD $sentinel_svc-$i
sev:
Info
Type:
Application
args:
- i
- sentinel_svc
cause:
Sentinel pod deleted, waiting for restart
workaround:
N/A