Normal |
1 |
Scheduled |
Successfully assigned onap/onap-awx-0 to compute04-onap-guilin |
Normal |
2 |
Pulling |
Pulling image "nexus3.onap.org:10001/onap/oom/readiness:3.0.1" |
Normal |
2 |
Pulled |
Successfully pulled image "nexus3.onap.org:10001/onap/oom/readiness:3.0.1" |
Normal |
2 |
Created |
Created container awx-init-readiness |
Normal |
2 |
Started |
Started container awx-init-readiness |
Normal |
2 |
TaintManagerEviction |
Cancelling deletion of Pod onap/onap-awx-0 |
Normal |
1 |
Pulling |
Pulling image "ansible/awx_web:9.0.1" |
Normal |
1 |
Pulled |
Successfully pulled image "ansible/awx_web:9.0.1" |
Normal |
1 |
Created |
Created container awx-web |
Normal |
1 |
Started |
Started container awx-web |
Normal |
1 |
Pulling |
Pulling image "ansible/awx_task:9.0.1" |
Normal |
1 |
Pulled |
Successfully pulled image "ansible/awx_task:9.0.1" |
Normal |
1 |
Created |
Created container awx-celery |
Normal |
1 |
Started |
Started container awx-celery |
Normal |
1 |
Pulling |
Pulling image "ansible/awx_rabbitmq:3.7.4" |
Normal |
1 |
Pulled |
Successfully pulled image "ansible/awx_rabbitmq:3.7.4" |
Normal |
1 |
Created |
Created container awx-rabbit |
Normal |
1 |
Started |
Started container awx-rabbit |
Normal |
1 |
Pulling |
Pulling image "memcached:1.5.20" |
Normal |
1 |
Pulled |
Successfully pulled image "memcached:1.5.20" |
Normal |
1 |
Created |
Created container awx-memcached |
Normal |
1 |
Started |
Started container awx-memcached |
Warning |
1 |
Unhealthy |
Liveness probe failed: Status of node rabbit@10.233.67.162 ...
Error: unable to perform an operation on node 'rabbit@10.233.67.162'. Please see diagnostics information and suggestions below.
Most common reasons for this are:
* Target node is unreachable (e.g. due to hostname resolution, TCP connection or firewall issues)
* CLI tool fails to authenticate with the server (e.g. due to CLI tool's Erlang cookie not matching that of the server)
* Target node is not running
In addition to the diagnostics info below:
* See the CLI, clustering and networking guides on http://rabbitmq.com/documentation.html to learn more
* Consult server logs on node rabbit@10.233.67.162
DIAGNOSTICS
===========
attempted to contact: ['rabbit@10.233.67.162']
rabbit@10.233.67.162:
* connected to epmd (port 4369) on 10.233.67.162
* node rabbit@10.233.67.162 up, 'rabbit' application running
Current node details:
* node name: 'rabbitmqcli80@onap-awx-0.onap-awx.onap.svc.cluster.local'
* effective user's home directory: /var/lib/rabbitmq
* Erlang cookie hash: fzkFV2J/Z5UOLdODv2NmbA==
|
Warning |
1 |
Unhealthy |
Liveness probe failed: Status of node rabbit@10.233.67.162 ...
Error: unable to perform an operation on node 'rabbit@10.233.67.162'. Please see diagnostics information and suggestions below.
Most common reasons for this are:
* Target node is unreachable (e.g. due to hostname resolution, TCP connection or firewall issues)
* CLI tool fails to authenticate with the server (e.g. due to CLI tool's Erlang cookie not matching that of the server)
* Target node is not running
In addition to the diagnostics info below:
* See the CLI, clustering and networking guides on http://rabbitmq.com/documentation.html to learn more
* Consult server logs on node rabbit@10.233.67.162
DIAGNOSTICS
===========
attempted to contact: ['rabbit@10.233.67.162']
rabbit@10.233.67.162:
* connected to epmd (port 4369) on 10.233.67.162
* node rabbit@10.233.67.162 up, 'rabbit' application running
Current node details:
* node name: 'rabbitmqcli42@onap-awx-0.onap-awx.onap.svc.cluster.local'
* effective user's home directory: /var/lib/rabbitmq
* Erlang cookie hash: fzkFV2J/Z5UOLdODv2NmbA==
|
Normal |
1 |
TaintManagerEviction |
Cancelling deletion of Pod onap/onap-awx-0 |