vmware / vmware/photon

2. Start the appropriate services on master: (systemctl instead of emctl)

Open
#1,315 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
C
Stars
3.2k
Forks
692
PR merge metrics
No merged PRs in 30d

Description

Describe the bug

Chapter:

https://vmware.github.io/photon/docs/user-guide/kubernetes-on-photon-os/running-kubernetes-on-photon-os/configure-kubernetes-on-master/

Photon OS Documentation / User Guide / Kubernetes on Photon OS / Running Kubernetes on Photon OS / Configure Kubernetes Services on the Master

for SERVICES in etcd kube-apiserver kube-controller-manager kube-scheduler; do
    emctl restart $SERVICES
    emctl enable $SERVICES
    emctl status $SERVICES
done
Reproduction steps
1. Run the code in the terminal
2.-bash: emctl: command not found
-bash: emctl: command not found
-bash: emctl: command not found
-bash: emctl: command not found
-bash: emctl: command not found
-bash: emctl: command not found
-bash: emctl: command not found
-bash: emctl: command not found
-bash: emctl: command not found
-bash: emctl: command not found
-bash: emctl: command not found
-bash: emctl: command not found
Expected behavior

The commands should be:

for SERVICES in etcd kube-apiserver kube-controller-manager kube-scheduler; do
    systemctl restart $SERVICES
    systemctl enable $SERVICES
    systemctl status $SERVICES
done
Additional context

No response

Contributor guide

Open the contributing guide

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

Open the linked Photon OS documentation page at the “Configure Kubernetes Services on the Master” section and review the service-management code block. Replace the unavailable emctl commands with systemctl as shown in the expected behavior, then verify that all restart, enable, and status commands use the corrected tool.

Written by the indexing model from the issue text.

Assessment

Tech stack
linux, shell
Domain
documentation
Issue type
Documentation
Difficulty
1/5
Estimated time
Under an hour
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.