microsoft / microsoft/pai

openpai installed over, but displays not correctly: You can go to http:, "no ip display and master work real ip is not Available "

Open
#5,628 3 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

2021-10-11 09:35:40,888 [INFO] - deployment.paiLibrary.paiService.service_management_start : Begin to clean all service's generated template file
2021-10-11 09:35:40,889 [INFO] - deployment.paiLibrary.paiService.service_template_clean : Begin to delete the generated template of marketplace-webportal's service.
2021-10-11 09:35:40,889 [INFO] - deployment.paiLibrary.paiService.service_template_clean : The generated template files of marketplace-webportal's service have been cleaned up.
2021-10-11 09:35:40,889 [INFO] - deployment.paiLibrary.paiService.service_management_start : Successfully start marketplace-webportal
2021-10-11 09:35:40,889 [INFO] - deployment.paiLibrary.paiService.service_management_start : -----------------------------------------------------------
script/service-boot.sh: line 48: kubectl: command not found

OpenPAI is successfully deployed, please check the following information:
Kubernetes cluster config : ~/pai-deploy/kube/config
OpenPAI cluster config : ~/pai-deploy/cluster-cfg
OpenPAI cluster ID : pai
Default username : admin
Default password : admin-password

You can go to http:, then use the default username and password to log in.
root@amax:/opt/pai/contrib/kubespray#

my master work ip is 192.168.50.190, but install tips does not displayed.

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 script/service-boot.sh around line 48 and the deployment output showing “kubectl: command not found.” Check how the deployment constructs the displayed access URL and master IP from the cluster configuration; this is done when a reachable URL and the master IP are printed after installation.

Written by the indexing model from the issue text.

Assessment

Tech stack
kubernetes, shell
Domain
devops, infrastructure
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.