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-25 Node Unschedulable

ALM-25 Node Unschedulable

Description

This alarm is reported when new pods cannot be scheduled onto a node.

The Scheduler is used for pod scheduling onto nodes. In Kubernetes, the Scheduler is used by the container cluster management system to collect and analyze resource usage of all nodes in the system, and schedule new pods onto the nodes in priority order based on node resource usage.

Attribute

Alarm ID

Alarm Severity

Alarm Type

25

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

New applications cannot be created on this node.

System Actions

The system prohibits other applications from being scheduled to this node.

Possible Causes

  • The disk space of the root directory used by the kubelet component is full.
  • The unschedulable attribute of the node is set to true.

Procedure

  1. Obtain the name of the instance that is abnormal.

    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. Check whether unschedulable is set to true.

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

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

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

      su - root

      Default password: QAZ2wsx@123!

    3. Run the following command to view the configuration items:

      kubectl edit node nodename -n namespace

      Nodename and namespace are the instance names and namespaces obtained in 1.

    4. Check whether unschedulable is set to true.
      • If yes, go to 3.
      • If no, go to 4.

  3. Set unschedulable to false. Then, check whether the alarm is cleared.

    • If yes, no further action is required.
    • If no, go to 4.

  4. Check whether the disk space where the /var/lib/kubelet directory is located is less than the threshold 256 MB.

    1. Log in to the target node and as the paas user.
    2. Run the following command to check whether the remaining disk space is insufficient.

      df -h /var/lib/kubelet

      Filesystem                  Size  Used Avail Use% Mounted on
      /dev/mapper/opt_vg-vol_opt   98G   21G   73G  23% /opt
      • If yes, go to 5.
      • If no, go to 6.

  5. Contact the IaaS administrator to expand the disk space or delete useless data from the disk. 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 will be automatically cleared after the fault is rectified.

Related Information

None

Translation
Download
Updated: 2019-08-30

Document ID: EDOC1100062365

Views: 44951

Downloads: 33

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