microsoft / microsoft/pai

Pai master Label is missing on single node deployment

Open
#5,416 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
2.7k
Forks
554
Avg merge
20h 42m
Merged PRs (30d)
14

Description

Organization Name:
Advantech

Short summary about the issue/question:
pai-master=true label is missing on single node deployment

Brief what process you are following:
We deployment one master and one worker on single node due to hardware resource limitation.
The deployment is OK when we comment some duplicate checking code. However, the deployment is pending upon openpai service deployment.
I check the node status and found that the pai-master is missing.
The deployment can be moved on when I restore the tag on demand( kubectl label nodes ${node} pai-master=true )
Where should I force the master label function upon single node deployment?

How to reproduce it:
1, Checkout openPAI v1.5.0, and set master and worker as same node on layout.yaml
2. Run quick-start-service.sh script

OpenPAI Environment:

  • OpenPAI version:
    V1.5.0
  • OS (e.g. from /etc/os-release):
    Ubuntu 18.04.3 LTS

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the v1.5.0 layout.yaml configuration and quick-start-service.sh reproduction steps, using a single node for both master and worker. Check where the deployment handles the pai-master label and compare it with the manual kubectl label command. Done means the label is applied automatically and the OpenPAI service deployment progresses without manual intervention.

Written by the indexing model from the issue text.

Assessment

Tech stack
kubernetes, shell
Domain
devops, infrastructure
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.