# 事件列表 CCI 2.0在多种资源操作过程中生成事件，包含Deployment、Replicaset、Service、HPA、Network、Pod几种资源，每种资源的事件分为以下几类，以type字段进行划分，每种资源分别对应着几种固定的操作类型和操作结果，附加信息为备注信息，仅在某些复杂场景中提供。 表1事件列表 | 资源对象 | 操作类型 | 操作结果 | 附加信息 | 描述信息 | 类比k8s事件reason举例 | |:---|:---|:---|:---|:---|:---| | Deployment | scale | succeeded | - | deployment扩缩容成功 | ScalingReplicaSet等 | | Deployment | scale | failed | - | deployment扩缩容失败 | ReplicaSetCreateError等 | | Deployment | delete | processing | - | deployment删除中 | DeleteDeployment等 | | Replicaset | scale | succeeded | - | replicaset扩缩容成功 | SuccessfulCreate、SuccessfulDelete等 | | Replicaset | scale | failed | - | replicaset扩缩容失败 | FailedCreate、FailedDelete等 | | Service | publish | failed | - | Service服务发现失败 | SyncLoadBalancerFailed等 | | Service | publish | succeeded | - | Service服务发现成功 | EnsuredLoadBalancer等 | | Service | publish | processing | - | Service服务发现中 | EnsuringLoadBalancer等 | | Service | delete | failed | - | Service服务删除失败 | DeleteLoadBalancerFailed等 | | Service | delete | succeeded | - | Service服务删除成功 | DeletedLoadBalancer等 | | Service | delete | processing | - | Service服务删除中 | DeletingLoadBalancer等 | | Horizontalpodautoscaler | rescale | failed | - | 重扩缩容失败 | FailedComputeMetricsReplicas、FailedRescale等 | | Horizontalpodautoscaler | rescale | failed | computemetricsfailed | 因metrics计算失败导致的重扩缩容失败 | FailedComputeMetricsReplicas等 | | Horizontalpodautoscaler | rescale | succeeded | - | 重扩缩容成功 | SuccessfulRescale等 | | Horizontalpodautoscaler | metricscrape | failed | - | 指标获取失败 | InvalidMetricSourceType、FailedGetResourceMetric等 | | Horizontalpodautoscaler | metricscrape | failed | invalidmetricsourcetype | 因非法metrics类型导致指标获取失败 | InvalidMetricSourceType等 | | Horizontalpodautoscaler | scaleobjectparse | failed | invalidscaleobject | 因非法对象导致扩缩容对象解析失败 | InvalidSelector、SelectorRequired等 | | Horizontalpodautoscaler | scaleobjectparse | failed | ambiguoushpa | 因HPA匹配混乱导致扩缩容对象解析失败 | AmbiguousSelector等 | | Network | networkprepare | failed | subneterror | 因子网同步异常导致网络准备失败 | FailedSyncNetwork等 | | Network | networkprepare | processing | - | 网络准备中 | ExternalDependenciesSyncd等 | | Network | networkassign | failed | noavailableip | 因无可用IP导致网络分配失败 | NetworkNoIPAvailable等 | | Network | networkrelease | failed | - | 网络释放失败 | NetworkFailed等 | | Pod | networkassign | failed | - | 网络分配失败 | FailedAssignENI、FailedAssignEIP等 | | Pod | networkrelease | failed | - | 网络释放失败 | FailedReleaseENI等 | | Pod | networkprobe | failed | - | 网络探测失败 | warningNetworkNotReady等 | | Pod | schedule | failed | - | 调度失败 | FailedScheduling等 | | Pod | schedule | succeeded | - | 调度成功 | Scheduled等 | | Pod | logsetup | failed | - | 日志配置失败 | SetupLogFailed等 | | Pod | imagepull | failed | - | 镜像拉取失败 | ImagePullSecretNotFound、FailedPullImage、BackOffPullImage等 | | Pod | imagepull | failed | imagepullsecretnotfound | 因imagepullsecret异常导致镜像拉取失败 | ImagePullSecretNotFound等 | | Pod | imagepull | processing | - | 镜像拉取中 | Pulling等 | | Pod | imagepull | succeeded | - | 镜像拉取成功 | Pulled等 | | Pod | containerlifecyclehook | failed | poststartfailed | poststart失败 | FailedPostStartHook等 | | Pod | containerlifecyclehook | failed | prestopfailed | prestop失败 | FailedPreStopHook等 | | Pod | containerlifecycleprobe | failed | - | 健康检查失败或者发生cgroup级别OOM | Unhealthy、OOMKillContainer等 | | Pod | containerlifecycleprobe | succeeded | - | 健康检查成功 | Healthy等 | | Pod | podcreate | failed | - | pod创建失败 | FailedCreate、FailedStart、BackOffStart等 | | Pod | podcreate | processing | - | pod创建中 | SandboxChanged等 | | Pod | podcreate | succeeded | - | pod创建成功或者pod资源规格被调整 | SuccessfulCreate、Started、ResourceAdjusted等 | | Pod | poddelete | failed | - | pod删除失败 | FailedKillPod、FailedDelete等 | | Pod | poddelete | processing | - | pod删除中 | Killing等 | | Pod | metricsetup | succeeded | - | 指标设置成功 | DefaultMetricsPort等 | | Pod | volumemount | failed | - | volume挂载失败 | FailedAttachVolume、FailedMount等 | | Pod | volumemount | succeeded | - | volume挂载成功 | SuccessfulAttachVolume、SuccessfulMountVolume等 | | Pod | ntpcheck | succeeded | - | NTP状态同步正常 | NTPSyncSuccess | | Pod | ntpcheck | failed | - | NTP状态同步异常 说明： 在 Pod 启动初期，时间同步服务（NTP）可能尚未完全就绪，因此触发 NTPSyncAbnormal 事件属正常现象，不代表 NTP 服务长期异常。若 NTPSyncAbnormal 事件持续存在且未自动恢复为 NTPSyncSuccess，建议排查以下可能原因： - NTP 服务器地址配置是否正确。 - 是否使用了不稳定的或配置错误的自定义 NTP 服务器。 - 节点网络是否允许 UDP 123 端口通信（NTP 协议依赖 UDP 123）。 | NTPSyncAbnormal | ![](https://support.huaweicloud.com/usermanual-cci2/public_sys-resources/caution_3.0-zh-cn.png) 事件源上报事件存在流控，上报事件速度过快，会触发流控，可能会引发事件丢失。默认每个事件源事件上报数量上限为25条，5分钟恢复上报一条。