Bug 1690591 - site-docker.yml.sample failure due to not noticing that firewalld is present
Summary: site-docker.yml.sample failure due to not noticing that firewalld is present
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Ceph Storage
Classification: Red Hat Storage
Component: Ceph-Ansible
Version: 3.2
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: z1
: 3.3
Assignee: Guillaume Abrioux
QA Contact: Vasishta
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-03-19 18:47 UTC by Ben England
Modified: 2019-10-22 13:29 UTC (History)
11 users (show)

Fixed In Version: RHEL: ceph-ansible-3.2.26-1.el7cp Ubuntu: ceph-ansible_3.2.26-2redhat1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-10-22 13:29:00 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github ceph ceph-ansible pull 4371 0 None None None 2019-08-22 14:46:05 UTC
Red Hat Product Errata RHBA-2019:3173 0 None None None 2019-10-22 13:29:14 UTC

Description Ben England 2019-03-19 18:47:26 UTC
Description of problem:

when running /usr/share/ceph-ansible/site-docker.yml.sample playbook to do containerized Ceph deployment, the deploy fails because none of the tasks to open up firewall ports are run.   This is because of a faulty when clause in my opinion.

Version-Release number of selected component (if applicable):

group_vars/all.yml:
containerized_deployment: True
ceph_docker_image: rhceph/rhceph-3-rhel7
ceph_docker_registry: registry.access.redhat.com
ceph_docker_image_tag: "3-23"  # ceph version 12.2.8-89.el7cp

How reproducible:

every time


Steps to Reproduce:
1.  run containerized ceph deploy using site-docker.yml.sample
2.  where firewalld is present on the target systems

Actual results:

No firewalld ports opened, OSDs can't come up cleanly


Expected results:

firewalld is configured such that ceph ports are open for business.


Additional info:

Here's the patch I did to the task named 

"check firewalld installation on redhat or suse"

So that it is not inhibited by a when clause from running in a containerized deployment - they too have firewalld to deal with.

[root@c07-h30-6018r ceph-ansible]# diff -u roles/ceph-infra/tasks/configure_firewall.ym{l.orig,l}
--- roles/ceph-infra/tasks/configure_firewall.yml.orig  2019-03-19 18:23:47.995250124 +0000
+++ roles/ceph-infra/tasks/configure_firewall.yml       2019-03-19 18:24:24.581323469 +0000      
@@ -9,8 +9,8 @@                                                                                  
   changed_when: false                                                                           
   tags:                                                                                         
     - firewall                                                                                  
-  when:                                                                                         
-    - not containerized_deployment

Comment 1 John Harrigan 2019-03-19 19:00:36 UTC
Observed with ceph-ansible.noarch 3.2.8-1.el7cp
and using 

group_vars/all.yml (containerized)
  containerized_deployment: True
  ceph_docker_image: rhceph/rhceph-3-rhel7
  # explicitly set the version (by default the 'latest' tag is used)
  ceph_docker_image_tag: “3-23”  (ceph version 12.2.8-89.el7cp)
  ceph_docker_registry: registry.access.redhat.com

Comment 3 Giridhar Ramaraju 2019-08-05 13:07:01 UTC
Updating the QA Contact to a Hemant. Hemant will be rerouting them to the appropriate QE Associate. 

Regards,
Giri

Comment 4 Giridhar Ramaraju 2019-08-05 13:09:35 UTC
Updating the QA Contact to a Hemant. Hemant will be rerouting them to the appropriate QE Associate. 

Regards,
Giri

Comment 11 errata-xmlrpc 2019-10-22 13:29:00 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2019:3173


Note You need to log in before you can comment on or make changes to this bug.