-
**Describe the bug**
During single record entry, entering a locality ID to pull/sync brings up the selection pane with the ID in the Locality Name field instead of the Locality ID field.
**To Re…
-
## Describe the bug
In Longhorn `v1.7.x`, a `Strict-Local` `v2` volume can be created with a Number of Replicas set to 3, which should not be allowed. According to the current design, when the `data …
-
## Type of issue
[x] Bug
[ ] Question (e.g. about handling/usage)
[ ] Request for new feature/improvement
## Expected Behavior
Locality, Postal Code and Region should be in the correct …
-
## Description
As users of the HDFS operator and a Stackable deployed HDFS we want it to ensure data locality by talking to a DataNode on the same Kubernetes node as the client first if one exists.
…
-
**Describe the bug**
Table format zero-to-one relationships do not allow specific fields to be selected **despite being supported**.
**To Reproduce**
Steps to reproduce the behavior:
1. Create…
-
**PROBLEM SUMMARY**
Terraform destroy will run and say it has completed and destroyed the Policy... but the policy will remain in TPP.
**STEPS TO REPRODUCE**
1. Create a policy in terraform
…
-
## Describe the bug
After I upgrade harvester 1.3.1 to 1.3.2 every thing works fine at first, but when I edit data locality "disabled to best effort" from longhorn UI of multiple volumes. One of them…
-
**Describe the bug**
The Specify 7 Geolocatre plugin is not entering Geocoordinate details into the form upon clicking the "Save to your application" button.
**To Reproduce**
Steps to reproduce t…
-
**Describe the bug**
It's hard to take items out of gravestones sometimes - probably because they don't transfer locality?
**To Reproduce**
Steps to reproduce the behavior:
1. Go to 'gravestone …
-
**Is your feature request related to a problem? Please describe.**
CRDB currently has a good way to check for critical localities: https://www.cockroachlabs.com/docs/stable/query-replication-report…