Closed anoopcs9 closed 2 years ago
Guess what?
# kubectl logs cshare2-65ww65-0 -n samba-operator-system -c dns-register
2022-09-16 09:20:35,476: INFO: enabling ctdb support: will check for leadership
2022-09-16 09:20:35,476: INFO: will watch source
Unknown command 'recmaster'
2022-09-16 09:20:35,518: ERROR: command SambaCommand('ctdb', ['recmaster'], None) failed: CalledProcessError(1, ['ctdb', 'recmaster'])
2022-09-16 09:20:35,518: INFO: skipping dns update. node not leader
Since the switch to fedora36 base image we started consuming Samba v4.16 which renamed recmaster
ctdb sub-command to leader
and caused dns not to be updated.
# kubectl logs cshare2-65ww65-0 -n samba-operator-system -c dns-register 2022-09-16 09:20:35,476: INFO: enabling ctdb support: will check for leadership 2022-09-16 09:20:35,476: INFO: will watch source Unknown command 'recmaster' 2022-09-16 09:20:35,518: ERROR: command SambaCommand('ctdb', ['recmaster'], None) failed: CalledProcessError(1, ['ctdb', 'recmaster']) 2022-09-16 09:20:35,518: INFO: skipping dns update. node not leader
https://github.com/samba-in-kubernetes/sambacc/pull/50 is intended to fix the above error.
This was not the case till we switched to reserving nodes from new EC2 pool fro CentOS CI infra.