SshFirewallAllowAll not taken into account anymore?

Bug #1859475 reported by Cédric Jeanneret
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tripleo
Invalid
High
Unassigned

Bug Description

Hello there,

Apparently, the move to the new firewall management thing (pure ansible) doesn't take into account the "SshFirewallAllowAll" param.
This param should inject an ip(6)tables rule opening Ssh service to the world.

As we can see here, it's set to "true" by default in t-h-t:
environments/standalone/standalone-tripleo.yaml: SshFirewallAllowAll: True
environments/undercloud.yaml: SshFirewallAllowAll: true

I need to investigate a bit more, but I'd say it's a regression.

Stay tuned!

C.

Revision history for this message
Rabi Mishra (rabi) wrote :

From heat parameter point of view true/True both should work.

https://github.com/openstack/heat/blob/master/heat/engine/parameters.py#L347

Revision history for this message
Cédric Jeanneret (cjeanner) wrote :

After some discussions, it's indeed OK - but "master" didn't get promotion in a while, meaning the following patch isn't available in "tripleo-current": https://review.opendev.org/#/c/700829/2/deployment/sshd/sshd-baremetal-puppet.yaml

Hence, if using "master", use tripleo-current-dev for now (matches CI anyway).

Revision history for this message
Cédric Jeanneret (cjeanner) wrote :

Already sorted out.

Changed in tripleo:
status: Triaged → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.