Renaming a server left its old node behind on the dashboard as "not
responding" for a day. The lease is keyed by hostname, and the installer
sets the container's hostname to the mail host, so a rename restarted the
server under a new lease while the old one sat there until it went
inactive 24 hours later. It can't be deleted from the console.
Each node now keeps the name it last leased under in node-hostname, next
to its local config (/etc/inbuxa, a volume in the installer's compose
file). When the name has changed, the per-minute lease renewal releases
the old name's lease once it has missed two renewals, before the
dashboard would call it stale. Only a lease last renewed before this node
started counts, so a host still running under that name (two nodes
sharing a config directory, say) keeps its lease and still shows up when
it stops. A read-only config directory just means the 24-hour expiry, as
before.
Leases left by a rename before this release still expire on their own.
Test: unit tests for the release rule, and two store-backed tests
(sqlite, test_mode): a rename drops the old lease after the grace
period, and a host renewing the old name after start is left alone.
Renaming a server left its old node behind on the dashboard as "not
responding" for a day. The lease is keyed by hostname, and the installer
sets the container's hostname to the mail host, so a rename restarted the
server under a new lease while the old one sat there until it went
inactive 24 hours later. It can't be deleted from the console.
Each node now keeps the name it last leased under in node-hostname, next
to its local config (/etc/inbuxa, a volume in the installer's compose
file). When the name has changed, the per-minute lease renewal releases
the old name's lease once it has missed two renewals, before the
dashboard would call it stale. Only a lease last renewed before this node
started counts, so a host still running under that name (two nodes
sharing a config directory, say) keeps its lease and still shows up when
it stops. A read-only config directory just means the 24-hour expiry, as
before.
Leases left by a rename before this release still expire on their own.
Test: unit tests for the release rule, and two store-backed tests
(sqlite, test_mode): a rename drops the old lease after the grace
period, and a host renewing the old name after start is left alone.
Fixes #458
jcoffey-dev
added this to the 27.1 milestone 2026-11-18 20:43:43 +00:00
jcoffey-dev
added the bug label 2026-11-18 20:43:43 +00:00
jcoffey-dev
self-assigned this 2026-11-18 20:43:43 +00:00
Renaming a server left its old node behind on the dashboard as "not
responding" for a day. The lease is keyed by hostname, and the installer
sets the container's hostname to the mail host, so a rename restarted the
server under a new lease while the old one sat there until it went
inactive 24 hours later. It can't be deleted from the console.
Each node now keeps the name it last leased under in node-hostname, next
to its local config (/etc/inbuxa, a volume in the installer's compose
file). When the name has changed, the per-minute lease renewal releases
the old name's lease once it has missed two renewals, before the
dashboard would call it stale. Only a lease last renewed before this node
started counts, so a host still running under that name (two nodes
sharing a config directory, say) keeps its lease and still shows up when
it stops. A read-only config directory just means the 24-hour expiry, as
before.
Leases left by a rename before this release still expire on their own.
Test: unit tests for the release rule, and two store-backed tests
(sqlite, test_mode): a rename drops the old lease after the grace
period, and a host renewing the old name after start is left alone.
Fixes#458
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Renaming a server left its old node behind on the dashboard as "not
responding" for a day. The lease is keyed by hostname, and the installer
sets the container's hostname to the mail host, so a rename restarted the
server under a new lease while the old one sat there until it went
inactive 24 hours later. It can't be deleted from the console.
Each node now keeps the name it last leased under in node-hostname, next
to its local config (/etc/inbuxa, a volume in the installer's compose
file). When the name has changed, the per-minute lease renewal releases
the old name's lease once it has missed two renewals, before the
dashboard would call it stale. Only a lease last renewed before this node
started counts, so a host still running under that name (two nodes
sharing a config directory, say) keeps its lease and still shows up when
it stops. A read-only config directory just means the 24-hour expiry, as
before.
Leases left by a rename before this release still expire on their own.
Test: unit tests for the release rule, and two store-backed tests
(sqlite, test_mode): a rename drops the old lease after the grace
period, and a host renewing the old name after start is left alone.
Fixes #458