hashicorp / hashicorp/nomad

Nomad UI - Cannot access allocation until allocation status changed

Open
#8,225 1 comment 0 reactions 0 assignees View on GitHub
stage/needs-investigation theme/ui type/bug
Dominant language
Go
Stars
17k
Forks
2.1k
Avg merge
1d 9h
Merged PRs (30d)
105

Description

### Nomad version
Nomad v0.11.3 (8918fc804a0c6758b6e3e9960e4eb2e605e38552)

### Operating system and Environment details

Ubuntu 18.04

### Issue
This had started with 0.11.x upgrade. When job is about to run (allocations are in pending state) I cannot click and view allocation for the first 5–10–15 sec. It may even fail and restart during this time but still its not accessible right away.

### Reproduction steps
Run any job.

### Job file (if appropriate)
I observer this behaviour with all jobs.

### Nomad Server logs (if appropriate)
```
Jun 19 21:26:21 hashistack-2 vault[6174]: 2020-06-19T21:26:21.205Z [INFO] expiration: revoked lease: lease_id=auth/token/create/nomad-cluster/h13b63fd895bd3ce3045c67cecb79f40995684fed41fde8885e8bb385710a4e60
(like 20–30 rows in the same second of job execution)
```
May it hang until vault issues new tokens? Most of my jobs have some secrets, so I'm using template stanza's.

Contributor guide

No contributing guide indexed for this repository

Research direction

No files, tests, or entry points are identified. Start by running any job and checking whether its allocation is inaccessible while pending, including jobs using the template stanza and Vault secrets; done means the allocation is viewable immediately and remains accessible through failures or restarts.

Written by the indexing model from the issue text.

Assessment

Domain
devops
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.