Skip to content

Open the Choria broker port on the server - #184

Merged
silug merged 1 commit into
puppet-bootstrap:productionfrom
silug:open-choria-broker-port
Oct 24, 2026
Merged

silug merged 1 commit into
puppet-bootstrap:productionfrom
silug:open-choria-broker-port

Conversation

@silug

@silug silug commented Oct 23, 2026

Copy link
Copy Markdown
Contributor

The server's firewall only allows the puppetmaster service, so agents' choria-server can't reach the Choria broker on 4222/tcp. The agent logs this over and over:

Initial connection to the Broker failed on try 15: dial tcp 192.168.32.5:4222: connect: no route to host

choria ping from the server only ever sees puppet.vagrant. This isn't related to OpenVox 9. It happens on OpenVox 8 with current production as well.

This adds a firewalld::ports entry for 4222/tcp to data/nodes/puppet.vagrant.yaml. profile::server already includes the firewalld class when it manages the firewall.

Testing

On a running OPENVOX_RELEASE=8 Vagrant environment, I deployed this with r10k and ran the agent on puppet.vagrant:

  • Firewalld_port[choria-broker] was created. firewall-cmd --list-ports and --permanent --list-ports both show 4222/tcp.
  • choria ping now gets 2 replies (puppet.vagrant and agent.vagrant).
  • A second agent run exits 0 (no changes).

🤖 Generated with Claude Code

The server's firewall only allows the `puppetmaster` service, so
choria-server on other nodes can't reach the broker on 4222/tcp and
`choria ping` only ever sees the server itself.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@silug
silug merged commit c1b47ce into puppet-bootstrap:production Oct 24, 2026
8 checks passed
@silug
silug deleted the open-choria-broker-port branch October 24, 2026 18:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant