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.

Sign up for GitHub

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

Jump to bottom

type = "periodic" seems to trigger a segfault #7203

Closed
scalp42 opened this issue Feb 20, 2020 · 2 comments · Fixed by #7207
Closed

type = "periodic" seems to trigger a segfault #7203

scalp42 opened this issue Feb 20, 2020 · 2 comments · Fixed by #7207
Labels
theme/jobspec type/bug

Comments

@scalp42
Copy link
Contributor

scalp42 commented Feb 20, 2020 •
edited

Nomad version

Client: Nomad v0.10.3
Server: Nomad v0.10.1

Operating system and Environment details

Client: macOS 10.14.6
Server: Ubuntu 18.04.3 LTS

Issue

When running a job with a type non existing, it's triggering a segfault.

Reproduction steps

nomad job run -verbose --address='https://xxx.example.com' ops-reaper.hcl

Job file

https://gist.github.com/Y-Tian/a37959a21ac6134ab211d51f1b5d93ba

Nomad Client logs

Error submitting job: Unexpected response code: 502 (<html>
<head><title>502 Bad Gateway</title></head>
<body bgcolor="white">
<center><h1>502 Bad Gateway</h1></center>
</body>
</html>
)

Nomad Server logs

https://gist.github.com/scalp42/816cb82d2838e2edca6b0ee3966674a5
@jrasell jrasell mentioned this issue Feb 20, 2020
Merged
@jrasell
Copy link
Member

jrasell commented Feb 21, 2020

Hi @scalp42, thanks for the detailed bug report. I was able to reproduce this with the examples you provided and have submitted a PR which resolves the bug.

@github-actions
Copy link

I'm going to lock this issue because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Nov 12, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
theme/jobspec type/bug
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fix panic when canonicalizing a jobspec with incorrect job type. hashicorp/nomad
2 participants
@scalp42 @jrasell