Open dmclf opened 11 months ago
Thanks for the report @dmclf.
It seems like these errors are conditionally rendered using a few non-mutually exclusive flags, and, if they are not set properly, it can lead to the scenario you described. https://github.com/hashicorp/nomad/blob/5f98e6473ccf2c5dd643fa6d79c43d113c56519b/ui/app/templates/settings/tokens.hbs#L55-L77
And the only place where we set tokenNotFound
to true
is when trying to fetch the token:
https://github.com/hashicorp/nomad/blob/5f98e6473ccf2c5dd643fa6d79c43d113c56519b/ui/app/services/token.js#L43-L60
So I suspect we may be querying the wrong region for that, resulting in the ACL token not found
error.
I have placed this in our board for further roadmapping.
Thanks again for the report!
still valid with v1.8.3
Nomad version
Output from
nomad version
Operating system and Environment details
Issue
when logging in with OIDC on a federated multi-region nomad cluster. this is consistently happening, a popup in green and red.
Reproduction steps
Expected Result
clean login
Actual Result
messy output concerning token authentication and token not found. (see image)