Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fatal error on purging broken package. #82

Closed
dkinzer opened this issue Aug 9, 2014 · 3 comments
Closed

Fatal error on purging broken package. #82

dkinzer opened this issue Aug 9, 2014 · 3 comments

Comments

@dkinzer
Copy link
Contributor

dkinzer commented Aug 9, 2014

I tried purging a pear package that did not properly install because the wrong extension config directory was supplied.

php_pear 'oci8' do 
   action 'purge'
end  

The action failed with the following relevant stack trace:

[2014-08-09T18:58:37+00:00] FATAL: Stacktrace dumped to /var/chef/cache/chef-stacktrace.out      
[2014-08-09T18:58:37+00:00] DEBUG: ArgumentError: php_pear[oci8] (oracle-instantclient::php line 
ror: ArgumentError: wrong number of arguments (2 for 4)                                          
/tmp/vagrant-chef-3/chef-solo-1/cookbooks/php/providers/pear.rb:212:in `manage_pecl_ini'         
/tmp/vagrant-chef-3/chef-solo-1/cookbooks/php/providers/pear.rb:170:in `remove_package'          
/tmp/vagrant-chef-3/chef-solo-1/cookbooks/php/providers/pear.rb:181:in `purge_package'           
/tmp/vagrant-chef-3/chef-solo-1/cookbooks/php/providers/pear.rb:76:in `block (2 levels) in class_
@dkinzer
Copy link
Contributor Author

dkinzer commented Aug 9, 2014

If I run the remove action first, I do not get this FATAL error.

@tas50
Copy link
Contributor

tas50 commented Jun 27, 2017

So I tried to reproduce this one and I added additional testing to the cookbook in 4.3.0 to do a install/remove/purge so we cover it all. Purge and remove are actually just aliases in the code now so this shouldn't be a thing anymore. Obviously it's been a while since this was filed and it was potentially very different at the time, but I'm pretty confident we can close this out now.

@tas50 tas50 closed this as completed Jun 27, 2017
@lock
Copy link

lock bot commented Apr 25, 2020

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked as resolved and limited conversation to collaborators Apr 25, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants