Kea issueshttps://gitlab.isc.org/isc-projects/kea/-/issues2023-07-31T14:08:52Zhttps://gitlab.isc.org/isc-projects/kea/-/issues/2666some lease commands don't leave a corresponding forensic log message2023-07-31T14:08:52ZAndrei Pavelandrei@isc.orgsome lease commands don't leave a corresponding forensic log message`lease-add`, `lease-update`, `lease-del` have corresponding forensic log messages:
```
Administrator added a lease of [...]
Administrator updated information on the lease of [...]
Administrator deleted the lease for [...]
```
`lease-wi...`lease-add`, `lease-update`, `lease-del` have corresponding forensic log messages:
```
Administrator added a lease of [...]
Administrator updated information on the lease of [...]
Administrator deleted the lease for [...]
```
`lease-wipe` and `lease6-bulk-apply` do not log anything.
If logging each deleted lease in the wipe command is considered too verbose, there could be a single line mentioning the wipe.
For the argument that `lease6-bulk-apply` command is only used by HA, it's worth mentioning that forensic logs appear for peer lease updates as well.next-stable-2.6https://gitlab.isc.org/isc-projects/kea/-/issues/1868forensic logging: renewals are logged as assignments2022-11-02T15:10:19ZAndrei Pavelandrei@isc.orgforensic logging: renewals are logged as assignmentsFor `n` subsequent DHCPREQUESTs or DHCPv6_REQUESTSs:
| v | v | log |
| ------ | -- | ------------------------------------------------------ |
| 1.9.7 | v4 | 1 * `has been assigne...For `n` subsequent DHCPREQUESTs or DHCPv6_REQUESTSs:
| v | v | log |
| ------ | -- | ------------------------------------------------------ |
| 1.9.7 | v4 | 1 * `has been assigned` + (n - 1) * `has been renewed` |
| 1.9.7 | v6 | 1 * `has been assigned` |
| 1.9.8+ | v4 | n * `has been assigned` |
| 1.9.8+ | v6 | n * `has been assigned` |
The inconsistency of `n - 1` missing renewal messages in v6 has been fixed in 1.9.8. But they are now shown as assignments instead of renewals. I think the behavior in 1.9.7 for v4 is what we need now for both v4 and v6.
DHCPV6_RENEWs and subsequent DHCPV6_REQUESTs are both logged as `has been assigned`. The message type should not make a difference. The behavior in 1.9.7 where only the state of the lease was being taken into account seems better to me, and so they should both say `has been renewed`.backlog