Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

missing numatopologies in yaml for arm64 #1836

Closed
SoaringAnecdotalBear opened this issue Nov 16, 2021 · 5 comments
Closed

missing numatopologies in yaml for arm64 #1836

SoaringAnecdotalBear opened this issue Nov 16, 2021 · 5 comments
Assignees
Labels
kind/bug Categorizes issue or PR as related to a bug. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@SoaringAnecdotalBear
Copy link

What happened:
After scheduler running, I noticed that it cannot find numatopologies in cluster. So the scheduler cannot run healthy

What you expected to happen:
The scheduler runs healthy

How to reproduce it (as minimally and precisely as possible):

Anything else we need to know?:

Environment:

  • Volcano Version: latest
  • Kubernetes version (use kubectl version): 1.17.3
  • Cloud provider or hardware configuration:
  • OS (e.g. from /etc/os-release): ubuntu 20.04.3 LTS
  • Kernel (e.g. uname -a): Linux ubuntu-k8s-master-1 5.4.0-1045-raspi Reclaim CI failed #49-Ubuntu SMP PREEMPT Wed Sep 29 17:49:16 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux
  • Install tools:
  • Others:

After all , I fix this bug with adding CustomResourceDefinition of "numatopologies.nodeinfo.volcano.sh" in volcano-development-arm64.yaml, and add resources numatopologies in ClusterRole volcano-scheduler.

@SoaringAnecdotalBear SoaringAnecdotalBear added the kind/bug Categorizes issue or PR as related to a bug. label Nov 16, 2021
@Thor-wl
Copy link
Contributor

Thor-wl commented Nov 17, 2021

/cc @huone1

@stale
Copy link

stale bot commented Feb 17, 2022

Hello 👋 Looks like there was no activity on this issue for last 90 days.
Do you mind updating us on the status? Is this still reproducible or needed? If yes, just comment on this PR or push a commit. Thanks! 🤗
If there will be no activity for 60 days, this issue will be closed (we can always reopen an issue if we need!).

@stale stale bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Feb 17, 2022
@stale
Copy link

stale bot commented Apr 24, 2022

Closing for now as there was no activity for last 60 days after marked as stale, let us know if you need this to be reopened! 🤗

@stale stale bot closed this as completed Apr 24, 2022
@Thor-wl Thor-wl removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 24, 2022
@Thor-wl Thor-wl reopened this Apr 24, 2022
@stale
Copy link

stale bot commented Jul 30, 2022

Hello 👋 Looks like there was no activity on this issue for last 90 days.
Do you mind updating us on the status? Is this still reproducible or needed? If yes, just comment on this PR or push a commit. Thanks! 🤗
If there will be no activity for 60 days, this issue will be closed (we can always reopen an issue if we need!).

@stale stale bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jul 30, 2022
@stale
Copy link

stale bot commented Oct 1, 2022

Closing for now as there was no activity for last 60 days after marked as stale, let us know if you need this to be reopened! 🤗

@stale stale bot closed this as completed Oct 1, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants