From ef1b0345535234bfa4adf149521a327c5b1500b2 Mon Sep 17 00:00:00 2001 From: Takashi Kajinami Date: Thu, 29 Oct 2020 23:45:10 +0900 Subject: [PATCH] Make sure octavia user belongs to octavia project For Octavia, we have OctaviaUserName and OctaviaProjectName to define user/project used for octavia service. Currently tripleo creates the service project and user according to these parameters, but the octavia user always belong to 'service' project, not to the project defined by OctaviaProjectName. This change ensures the octavia user belongs to the project defined by the OctaviaProjectName parameter. Change-Id: I32812b3cb1216c0617f3e9ccd498a2d53fec61a6 --- deployment/octavia/octavia-api-container-puppet.yaml | 1 + 1 file changed, 1 insertion(+) diff --git a/deployment/octavia/octavia-api-container-puppet.yaml b/deployment/octavia/octavia-api-container-puppet.yaml index 2a89b290c5..8ab146c722 100644 --- a/deployment/octavia/octavia-api-container-puppet.yaml +++ b/deployment/octavia/octavia-api-container-puppet.yaml @@ -156,6 +156,7 @@ outputs: octavia: name: {get_param: OctaviaUserName} password: {get_param: OctaviaPassword} + project: {get_param: OctaviaProjectName} region: {get_param: KeystoneRegion} service: 'load-balancer' monitoring_subscription: {get_param: MonitoringSubscriptionOctaviaApi}