This page lists defects we have found in the Relayer UI and gateway, what they do, and where each one stands. Entries stay here after they are fixed, with the fix recorded, so you can tell the difference between a problem we closed and a problem nobody has looked at.
Current as of 9 September 2026. Verified against current source and against a live gateway on a test install the same day.
Open
Nothing currently open. Every entry below has been resolved. When we find something new it appears here first, with its workaround, before it is fixed.
Resolved
Found during a full-UI walkthrough on 3 July 2026 against a beta install, and resolved since. Kept for anyone running an older build who hits one of them.
1. Create IAM User failed silently when the Cost Center field was blank — RESOLVED
- What happened: creating an IAM user with the Cost Center field empty did nothing. The dialog stayed open and showed no error.
- Why: two separate defects. The field was labeled optional but the build required it, and the resulting failure was swallowed instead of shown.
- How it was resolved: the cost-center picker was removed from Create User and Create Service Account entirely. Scope is now inherited from the account context rather than typed in, so the field that caused this no longer exists. Failures on these dialogs now surface a message.
- Verified: IAM user creation exercised against a live gateway on 9 September 2026.
2. IAM users were denied every S3 operation — RESOLVED
- What happened: an IAM user with a policy attached received
403 AccessDeniedon all operations, including ListBuckets. The install’s root credential was unaffected. - Why: credentials minted by older builds carried no account association. A later build added a check that fails closed when it cannot resolve a credential’s owner, and nothing backfilled the older credentials, so they were refused permanently.
- How it was resolved: the gateway now reconciles credentials at start-up, re-anchoring any credential left without an account association. It runs on every boot and is safe to repeat, so simply restarting a current build repairs affected credentials. The same reconcile carries sub-credentials along when an operator changes the account identity, which was the other way credentials could be stranded.
- Verified: IAM users created, authenticated and used against a live gateway on 9 September 2026, including a cross-user denial check confirming that refusals still happen when they should.
3. The Denied views excluded authentication failures — RESOLVED
- What happened: the IAM page reported “No recent denials — every request has been allowed” and the Audit Log’s Denied tab showed nothing, while All Events held authentication failures. During a credential problem — the moment an operator checks these panels — they said everything was fine.
- Why: the panels counted policy denials only, and treated an authentication failure as a different class of event.
- How it was resolved: both the IAM denials panel and the Audit Log’s Denied filter now include authentication failures alongside policy denials. The panel also distinguishes a failed load from a genuine absence of denials, so a fetch error can no longer read as “every request allowed.”
4. Attach Policy closed without attaching — RESOLVED
- What happened: pressing Attach while the placeholder option was still selected closed the dialog without attaching anything and without a message.
- How it was resolved: the Attach button is disabled until a policy is chosen, so the empty case cannot be submitted. A real attach now confirms success, and a failed one says so instead of closing quietly. Detaching behaves the same way.
- Verified: inline policies applied to a test user against a live gateway on 9 September 2026, confirmed denied before the policy and allowed after.
Reporting something
If you hit something that is not here, tell us — contact us. We would rather hear it from you than have it sit unreported, and a defect with a reproduction attached gets fixed considerably faster.
