aeolus-cleanup does clean them up. But if you upgraded to a version of aeolus-configure
that supported single deltacloud-core without running aeolus-cleanup, then these
init files will remain in /etc/init.d.
---
recipes/aeolus/manifests/deltacloud.pp | 7 +++++++
1 files changed, 7 insertions(+), 0 deletions(-)
diff --git a/recipes/aeolus/manifests/deltacloud.pp
b/recipes/aeolus/manifests/deltacloud.pp
index 87b5905..cb442d1 100644
--- a/recipes/aeolus/manifests/deltacloud.pp
+++ b/recipes/aeolus/manifests/deltacloud.pp
@@ -56,4 +56,11 @@ class aeolus::deltacloud::disabled {
ensure => 'stopped',
enable => false,
hasstatus => true}
+
+ # remove deprecated services
+ file { '/etc/init.d/deltacloud-ec2-us-east-1': ensure => 'absent'
}
+ file { '/etc/init.d/deltacloud-ec2-us-west-1': ensure => 'absent'
}
+ file { '/etc/init.d/deltacloud-mock': ensure => 'absent' }
+ file { '/etc/init.d/deltacloud-rhevm': ensure => 'absent' }
+ file { '/etc/init.d/deltacloud-vsphere': ensure => 'absent' }
}
--
1.7.6
Show replies by date
Please ignore. Subject line is not correct. Will repost.