Swift: Do not enable the whole rsync::server class
In puppet run for swift, we enable the entire rsync::server class and this sometimes results in unexpected package installation inside the container-puppet-swift container. Because we only need file/concat resources defined in the class since we get rid of xinetd for CentOS 9 and these resources are enabled by default, this change removes that entire class from tags. Related-Bug: #1979204 Change-Id: I7e29a6e797155ca5c5aa27996a4e35e688061b6f
This commit is contained in:
parent
e1afca352e
commit
13e84c4f5c
@ -225,6 +225,7 @@ outputs:
|
||||
params:
|
||||
$NETWORK: {get_param: [ServiceNetMap, SwiftStorageNetwork]}
|
||||
rsync::server::pid_file: 'UNSET'
|
||||
rsync::server::use_xinetd: false
|
||||
swift::objectexpirer::cache_tls_enabled: {get_param: MemcachedTLS}
|
||||
swift::storage::all::account_server_workers:
|
||||
if:
|
||||
@ -253,7 +254,7 @@ outputs:
|
||||
# BEGIN DOCKER SETTINGS
|
||||
puppet_config:
|
||||
config_volume: swift
|
||||
puppet_tags: swift_config,swift_container_config,swift_container_sync_realms_config,swift_account_config,swift_object_config,swift_object_expirer_config,rsync::server
|
||||
puppet_tags: swift_config,swift_container_config,swift_container_sync_realms_config,swift_account_config,swift_object_config,swift_object_expirer_config
|
||||
step_config: |
|
||||
include tripleo::profile::base::swift::storage
|
||||
config_image: {get_attr: [RoleParametersValue, value, ContainerSwiftConfigImage]}
|
||||
|
Loading…
Reference in New Issue
Block a user