Scott Yeager

That was on node 2098. Farmer noticed coincidentally while checking public ip config in the explorer. Possibly the change happened a while ago before seek time persistence was implemented.

Issue is a duplicate of #1713, which I'll close in favor of the more recent discussion here. In that case, the same node created violations for April and May. The...

Anecdotally, I see reports of this from time to time. They always clear with a reboot and don't seem to recur. I'll document further cases here if I see them.

Here's a new case, node id 3755 on mainnet. This one is not clearing with reboot. We can see the the farmer minted for last month with the properly detected...

We have an existential question to settle here: what is a node? Currently it's an arbitrary hardware configuration plus a given seed file. Defining a node as a specific hardware...

Another report here: https://github.com/threefoldtech/test_feedback/issues/296

Looks like an instance of this: https://bugs.launchpad.net/cloud-init/+bug/1979877 There's a fix included in cloud-init 22.3, but these Ubuntu images still ship with 22.2. Author of the issue above mentions a workaround:...

The release status for cloud-init in Ubuntu can be seen [here](https://launchpad.net/ubuntu/+source/cloud-init). Kinetic (22.10) is the only release to ship with cloud-init 22.3 currently. I tested the latest cloud image of...

Unifying around cloud-init configs is one option. Looks like some work was already done to support this in [cloud-container](https://github.com/threefoldtech/cloud-container). Specifying environment variables and entry point for containers isn't so clean...

@muhamadazmy, we already have a similar situation with divergence between the configuration of full vms and micro vms. That is, environment variables and entry point are already not supported by...