No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

HUAWEI CLOUD Stack 6.5.0 Alarm and Event Reference 04

Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
ALM-7 Failed to Update Cron Job

ALM-7 Failed to Update Cron Job

Description

This alarm is reported when a Cron job fails to be updated.

Attribute

Alarm ID

Alarm Severity

Alarm Type

7

Major

Environmental alarm

Parameters

Parameter Name

Parameter Description

kind

Resource type.

namespace

Name of the project to which the resource belongs.

name

Resource name.

uid

Unique ID of the resource.

OriginalEventTime

Event generation time.

EventSource

Name of the component that reports an event.

EventMessage

Supplementary information about an event.

Impact on the System

Related functions are unavailable.

System Actions

The system keeps updating the Cron job.

Possible Causes

After kube-controller-manager successfully obtains a Cron job using kube-apiserver, exceptions occur when kube-controller-manager access kube-apiserver during the update of the subjobs of the Cron job. As a result, the Cron job fails to be updated.

Procedure

  1. Obtain the name of the Cron job that fails to be updated.

    1. Use a browser to log in to the FusionStage OM zone console.
      1. Log in to ManageOne Maintenance Portal.
        • Login address: https://Address for accessing the homepage of ManageOne Maintenance Portal:31943, for example, https://oc.type.com:31943.
        • The default username is admin, and the default password is Huawei12#$.
      2. On the O&M Maps page, click the FusionStage link under Quick Links to go to the FusionStage OM zone console.
    2. Choose Application Operations > Application Operations from the main menu.
    3. In the navigation pane on the left, choose Alarm Center > Alarm List and query the alarm by setting query criteria.
    4. Click to expand the alarm information. Record the values of name and namespace in Location Info, that is, podname and namespace.

  2. Use PuTTY to log in to the manage_lb1_ip node.

    The default username is paas, and the default password is QAZ2wsx@123!.

  3. Run the following command and enter the password of the root user to switch to the root user:

    su - root

    Default password: QAZ2wsx@123!

  4. Check whether the status of the kube-apiserver service instance is normal.

    1. Run the kubectl get pod -n namespace | grep kube-apiserver command.

      In the preceding command, namespace is the namespace obtained in 1.

    2. Check whether the status of the kube-apiserver service instance is normal.

      Running indicates a normal status.

      hostname:~ # kubectl get pod -n kube-system | grep kube-apiserver
      kube-apiserver-1*            1/1       Running   1          21d
      kube-apiserver-2*            1/1       Running   0          21d

  5. Rectify the abnormal kube-apiserver service instance.

    1. Move kube-apiserver.manifest out of the /var/paas/kubernetes/manifests/ directory.
    2. Run the docker ps | grep kube-apiserver command. When no kube-apiserver container is running, move kube-apiserver.manifest back to /var/paas/kubernetes/manifests/.
    3. Run the docker ps | grep kube-apiserver command, wait until the kube-apiserver container is running properly, and then check whether the alarm is cleared.
      • If yes, no further action is required.
      • If no, go to 6.

  6. Contact technical support for assistance.

Alarm Clearing

This alarm is automatically cleared after the fault is rectified.

Related Information

None

Translation
Download
Updated: 2019-08-30

Document ID: EDOC1100062365

Views: 47397

Downloads: 33

Average rating:
This Document Applies to these Products
Related Version
Related Documents
Share
Previous Next