You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We decided to upgrade our infrastructure slowly from 1.9.1 to 1.11. Our servers reside on VMWare Infrastructure, based on RHEL servers.
Every time we tried migrating, the ACL system decided to crash, and the master token became invalid, while we can't view the status of our services and nodes. We also tried to reset the ACL System as showed in the outage troubleshooting, to no success.
We reproduced it by booting a new, seperate Consul cluster, and it showed the same result the moment we booted up the ACL System.
Reproduction Steps
Steps to reproduce this issue, eg:
Create a cluster, using Consul version 1.9.3 or above.
Use the following configuration files: config.acl:
The log shows either the error ACL not found or Permission denied while trying to connect with the master token. Access to services and nodes that registered with Consul is permitted if the anonymous token has read access over the services and nodes on the cluster, but the UI won't show them.
Operating system and Environment details
OS: Red Hat Enterprise Linux 7.4 (although the bug reproduced in 8.x as well)
The servers reside on an on-prem VMWare infrastructure.
The text was updated successfully, but these errors were encountered:
notBscalE
changed the title
ACL System crashes on VMWare/RHEL servers
ACL System crashes on RHEL on VMWare servers
Aug 10, 2022
Overview of the Issue
We decided to upgrade our infrastructure slowly from 1.9.1 to 1.11. Our servers reside on VMWare Infrastructure, based on RHEL servers.
Every time we tried migrating, the ACL system decided to crash, and the master token became invalid, while we can't view the status of our services and nodes. We also tried to reset the ACL System as showed in the outage troubleshooting, to no success.
We reproduced it by booting a new, seperate Consul cluster, and it showed the same result the moment we booted up the ACL System.
Reproduction Steps
Steps to reproduce this issue, eg:
config.acl
:config_acl.json
:ACL not found
orPermission denied
while trying to connect with the master token. Access to services and nodes that registered with Consul is permitted if the anonymous token has read access over the services and nodes on the cluster, but the UI won't show them.Operating system and Environment details
OS: Red Hat Enterprise Linux 7.4 (although the bug reproduced in 8.x as well)
The servers reside on an on-prem VMWare infrastructure.
The text was updated successfully, but these errors were encountered: