Bug 856670 - Aeolus-cleanup error:Must pass nfs_mount_point to Aeolus::Profiles::Rhevm::Disable[default] at /usr/share/aeolus-configure/modules/aeolus/manifests/profiles/rhevm/disable.pp:
Summary: Aeolus-cleanup error:Must pass nfs_mount_point to Aeolus::Profiles::Rhevm::Di...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: CloudForms Cloud Engine
Classification: Retired
Component: aeolus-configure
Version: 1.1.0
Hardware: Unspecified
OS: Unspecified
low
medium
Target Milestone: rc
Assignee: Mo Morsi
QA Contact: Rehana
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-09-12 14:35 UTC by Aziza Karol
Modified: 2013-08-14 19:04 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-08-14 19:04:56 UTC
Embargoed:
morazi: needinfo+


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 815257 0 unspecified CLOSED aeolus-cleanup for rhevm provider is not removing the rhevm_provider details from conductor 2021-02-22 00:41:40 UTC

Internal Links: 815257

Description Aziza Karol 2012-09-12 14:35:06 UTC
Description of problem:


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


How reproducible:


Steps to Reproduce:
1.Install aeolus and  run aeolus-configure.
2.Try aeolus-cleanup.

For rhevm-clean up i get:
#aeolus-cleanup -p rhevm
aeolus-cleanup will delete local aeolus installations.
Are you sure you wish to proceed? [y/N]: y
Must pass nfs_mount_point to Aeolus::Profiles::Rhevm::Disable[default] at /usr/share/aeolus-configure/modules/aeolus/manifests/profiles/rhevm/disable.pp:15 on node dell-pe1950-1.rhts.eng.rdu.redhat.com

#aeolus-cleanup -p vsphere,ec2,mock
aeolus-cleanup will delete local aeolus installations.
Are you sure you wish to proceed? [y/N]: y
File not found: /etc/aeolus-configure/nodes/vsphere_cleanup


Expected results:


Additional info:
rpm -qa | grep aeolus
aeolus-all-0.13.0-0.20120911080010git2f1db53.fc16.noarch
rubygem-aeolus-image-0.6.0-0.20120912040016git902c81c.fc16.noarch
aeolus-conductor-0.13.0-0.20120911080010git2f1db53.fc16.noarch
rubygem-aeolus-cli-0.7.0-0.20120912040013git8a46b3f.fc16.noarch
aeolus-conductor-doc-0.13.0-0.20120911080010git2f1db53.fc16.noarch
aeolus-conductor-daemons-0.13.0-0.20120911080010git2f1db53.fc16.noarch
aeolus-configure-2.8.0-0.20120912040010git0b3dad6.fc16.noarch

Comment 2 Mike Orazi 2012-09-12 21:02:32 UTC
This appears to be 2 issues:

1.  The first issue looks like you didn't edit /etc/aeolus-configure/nodes/rhevm_cleanup to telli t about nfs_mount_point (there is a section in there that needs to be uncommented out prior to running aeolus-cleanup)

2.  vsphere, ec2, mock don't have corresponding *_cleanup descriptions.  We limit cleanup pretty severely so we don't accidentally remove provider/provider account info.  rhevm has a cleanup to remove the nfs mount, but none of the other providers require a similar setup.  I'm not sure we want to dig too much deeper into removal of resources than that.

Thoughts?

Comment 3 Mike Orazi 2012-09-12 21:04:18 UTC
To be more explicit, if you go along with the explanation in 2 and agree, please CLOSE as not a bug.  If I'm missing something or there is disagreement on point 2, let's discuss.

Comment 4 Mo Morsi 2013-01-28 20:41:08 UTC
Pushed a patch addressing #1 so that the nfs unmount will be skipped over if mount point is not specified

https://github.com/aeolusproject/aeolus-configure/commit/601ee822a6559ba76abe9ad02e6cb5a2bc449609


And yes, as far as #2 that is the intended behaviour. We have a check that gets run as part of configure and cleanup that ensures the specified profile exists and outputs a "File not found" before exiting if it doesn't.

Comment 5 Mo Morsi 2013-08-14 19:04:56 UTC
aeolus is no longer being developed


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