Bug 2236231

Summary: [OPS 17.1] ceph monitoring services such as grafana may not correctly bind to specific overcloud networks and conflict with haproxy port
Product: Red Hat OpenStack Reporter: Matt Flusche <mflusche>
Component: openstack-tripleoAssignee: Francesco Pantano <fpantano>
Status: CLOSED DUPLICATE QA Contact: Alfredo <alfrgarc>
Severity: high Docs Contact:
Priority: high    
Version: 17.1 (Wallaby)CC: eharney, fpantano, lmiccini, mburns
Target Milestone: ---Keywords: Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-10-16 06:51:28 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 2356550, 2356553, 2233659, 2246440, 2254553, 2350124, 2356355, 2356551    
Bug Blocks:    

Description Matt Flusche 2023-08-30 18:27:02 UTC
Description of problem:

It seems in some situations cephadm may not setup services such as grafana to bind correctly to a specific network interface. This can cause a deployment failure as it tries to bind to all interfaces and conflicts with the related haproxy config.

More details in this cephadm bz: https://bugzilla.redhat.com/show_bug.cgi?id=2233659

The goal here is to determine if tripleo can better handle this config until cephadm bug is resolved; perhaps different ports for haproxy and backend services.

This seems to impact ipv6 deployments and multi-segment overcloud storage networks; perhaps other scenarios.

The typical ipv4 single segment storage network is not impacted.

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

How reproducible:
See related bz and description above.