hosts: Remove chromie.p.b from AD domain
Since it was updated to Fedora 42, Jenkins configuration management jobs have been failing to apply policy to _chromie.pyrocufflink.blue_. It claims "jenkins is not in the sudoers file," apparently because `winbind` keeps "forgetting" that _jenkins_ is a member of the _server admins_ group, which is listed in `sudoers` file. I'm getting tired of messing with `winbind` and its barrage of bugs and quirks. There's no particular reason for _chromie_ to be an AD domain member, so let's just remove it and manage its users statically.master
parent
423f28ea53
commit
8a93ef0fc1
8
hosts
8
hosts
|
@ -25,6 +25,9 @@ git0.pyrocufflink.blue
|
|||
|
||||
[certbot]
|
||||
|
||||
[chrony]
|
||||
chromie.pyrocufflink.blue
|
||||
|
||||
[chrony:children]
|
||||
kubelet
|
||||
pyrocufflink
|
||||
|
@ -34,6 +37,7 @@ node-6a3f87.k8s.pyrocufflink.black
|
|||
node-6ed191.k8s.pyrocufflink.black
|
||||
|
||||
[collectd]
|
||||
chromie.pyrocufflink.blue
|
||||
|
||||
[collectd:children]
|
||||
kubelet
|
||||
|
@ -176,7 +180,6 @@ web0.pyrocufflink.blue
|
|||
pxe0.pyrocufflink.blue
|
||||
|
||||
[pyrocufflink]
|
||||
chromie.pyrocufflink.blue
|
||||
cloud0.pyrocufflink.blue
|
||||
db0.pyrocufflink.blue
|
||||
dc-grumbly.pyrocufflink.blue
|
||||
|
@ -234,6 +237,9 @@ smtp1.pyrocufflink.blue
|
|||
|
||||
[squid]
|
||||
|
||||
[sudo]
|
||||
chromie.pyrocufflink.blue
|
||||
|
||||
[sudo:children]
|
||||
pyrocufflink
|
||||
vps
|
||||
|
|
Loading…
Reference in New Issue