This PR should correct the issue.

It should. This should really be a non-breaking change as it's a fallback for something else that already exists in /etc/hosts.

This also has a measurable impact on CPU. You can tell exactly when I applied the nsswitch.conf fix.

To add to this, this link pointed me at the correct solution:

Go for it. Just to confirm, this did work on the rolling from the 8th of this month, so it was something that got gobbled up in the rewrite.

Then I believe the best course of action is to restore that error condition, but have it reference the “alias” config then.

To add, maybe it's just the content of the error message that's misleading here if there other ways to do it. Or maybe the problem is that there are multiple ways to accomplish this

I guess there's two ways to approach it. This is the correct way:

This PR should correct.

Revising this since I nailed down the issue.

Can confirm. This bug is corrected in the the latest rollings (for at least a month or more)

This one works good too

Seems like this might be VRF related

Changed this around a bit to load the modules automatically if necessary. Only adds about half a second to initial execution

This PR419 should take care of this and the parent task

No worries. I think I've got a simple fix for this. Just needed to step away for a bit

This is related to this change:

PR416 should be the real fix here and PR413 should be reverted.

Yep. Confirmed, and that's the root issue here.

This PR should hopefully correct this.

@dmbaturin Maybe just anything that contains systemctl? Surely 100% of those will need it. But that also assumes anything called via /usr/lib/python3/dist-packages/vyos/util.py

PR510 should add the necessary sudo

This was a breaking change

PR405 corrects this

This PR should address this simple usability enhancement

This PR should built proper images

Looks good. I don't have merge access but this definitely is a fix to an oversight in the build.

Sure, go ahead. Thanks!

If this is a duplicate of something, go ahead and close it

PR283 should fix this.

PR262 should fix that last one @alien

PR260 should fix this

PR259 fixes this

Can confirm that this can be closed now.

Personally this is behavior I agree with.