Public bug reported:
The facter_1.5.6-2ubuntu2.2 is broken on Lucid. A timeout error is
thrown in the ec2 module:
# dpkg -i facter_1.5.6-2ubuntu2.2_all.deb
(Reading database ... 59502 files and directories currently installed.)
Preparing to replace facter 1.5.6-2ubuntu2.1 (using
facter_1.5.6-2ubuntu2.2_all.deb) ...
Unpacking replacement facter ...
Setting up facter (1.5.6-2ubuntu2.2) ...
Processing triggers for man-db ...
# facter
/usr/lib/ruby/1.8/timeout.rb:60:in `open': execution expired (Timeout::Error)
from /usr/lib/ruby/1.8/net/http.rb:560:in `connect'
from /usr/lib/ruby/1.8/timeout.rb:53:in `timeout'
from /usr/lib/ruby/1.8/timeout.rb:93:in `timeout'
from /usr/lib/ruby/1.8/net/http.rb:560:in `connect'
from /usr/lib/ruby/1.8/net/http.rb:553:in `do_start'
from /usr/lib/ruby/1.8/net/http.rb:542:in `start'
from /usr/lib/ruby/1.8/open-uri.rb:242:in `open_http'
from /usr/lib/ruby/1.8/open-uri.rb:616:in `buffer_open'
from /usr/lib/ruby/1.8/open-uri.rb:164:in `open_loop'
from /usr/lib/ruby/1.8/open-uri.rb:162:in `catch'
from /usr/lib/ruby/1.8/open-uri.rb:162:in `open_loop'
from /usr/lib/ruby/1.8/open-uri.rb:132:in `open_uri'
from /usr/lib/ruby/1.8/open-uri.rb:518:in `open'
from /usr/lib/ruby/1.8/open-uri.rb:30:in `open'
from /usr/lib/ruby/1.8/facter/ec2.rb:10:in `can_connect?'
from /usr/lib/ruby/1.8/facter/ec2.rb:10:in `can_connect?'
from /usr/lib/ruby/1.8/facter/ec2.rb:33
from /usr/lib/ruby/1.8/facter/util/loader.rb:72:in `load'
from /usr/lib/ruby/1.8/facter/util/loader.rb:72:in `load_file'
from /usr/lib/ruby/1.8/facter/util/loader.rb:38:in `load_all'
from /usr/lib/ruby/1.8/facter/util/loader.rb:33:in `each'
from /usr/lib/ruby/1.8/facter/util/loader.rb:33:in `load_all'
from /usr/lib/ruby/1.8/facter/util/loader.rb:30:in `each'
from /usr/lib/ruby/1.8/facter/util/loader.rb:30:in `load_all'
from /usr/lib/ruby/1.8/facter/util/collection.rb:94:in `load_all'
from /usr/lib/ruby/1.8/facter.rb:91:in `to_hash'
from /usr/bin/facter:138
If I reinstall facter_1.5.6-2ubuntu2.1_all.deb, it works fine:
# dpkg -i facter_1.5.6-2ubuntu2.1_all.deb
dpkg: warning: downgrading facter from 1.5.6-2ubuntu2.2 to 1.5.6-2ubuntu2.1.
(Reading database ... 59502 files and directories currently installed.)
Preparing to replace facter 1.5.6-2ubuntu2.2 (using
facter_1.5.6-2ubuntu2.1_all.deb) ...
Unpacking replacement facter ...
Setting up facter (1.5.6-2ubuntu2.1) ...
Processing triggers for man-db ...
# facter
architecture => x86_64
domain => something.org
facterversion => 1.5.6
fqdn => www-dev.something.org
hardwareisa => unknown
hardwaremodel => x86_64
hostname => www-dev
...
I reproduced this on two different machines. Why wasn't a simple run of
the facter command part of the automated tests after building this
package?
** Affects: facter (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to facter in Ubuntu.
https://bugs.launchpad.net/bugs/887361
Title:
facter facter_1.5.6-2ubuntu2.2: /usr/lib/ruby/1.8/timeout.rb:60:in
`open': execution expired (Timeout::Error)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/facter/+bug/887361/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
