** Changed in: puppet
Status: New => Fix Released
** Changed in: facter (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/885998
Title:
facter u
another confirmed fix in lucid (non-EC2) for 1.5.8-2ubuntu2.3, on a
system that had previously exhibited the issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/885998
Title:
facter upgrade crashes
Confirm 1.5.8-2ubuntu2.3 fixes the problem in facter and makes puppet
run again.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/885998
Title:
facter upgrade crashes puppet
To manage notifications ab
** Branch linked: lp:ubuntu/maverick-updates/facter
** Branch linked: lp:ubuntu/natty-updates/facter
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/885998
Title:
facter upgrade crashes puppet
To ma
This bug was fixed in the package facter - 1.5.8-2ubuntu2.2
---
facter (1.5.8-2ubuntu2.2) natty-proposed; urgency=low
* debian/patches/fix_ec2_metadata_facts.patch: Refreshed to rescue condition
in can_connect() when timeout() actually has a chance to timeout.
(LP: #885998)
This bug was fixed in the package facter - 1.5.7-1ubuntu1.3
---
facter (1.5.7-1ubuntu1.3) maverick-proposed; urgency=low
* lib/facter/ec2.rb: Rescue condition in can_connect() when timeout()
actually has a chance to timeout. (LP: #885998)
-- Adam GandelmanMon, 07 Nov 2011 1
The natty package fixes the problem too.
I don't have anywhere to test oneric unfortunately.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/885998
Title:
facter upgrade crashes puppet
To manage not
Just tested the maverick package. Again, it's fixed the problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/885998
Title:
facter upgrade crashes puppet
To manage notifications about this bug go
I tested the lucid proposed package. The regression is fixed (in my non
EC2 environment).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/885998
Title:
facter upgrade crashes puppet
To manage notific
** Branch linked: lp:ubuntu/lucid-updates/facter
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/885998
Title:
facter upgrade crashes puppet
To manage notifications about this bug go to:
https://bugs
Skipping the usual 7 day waiting period as this was a regression. I'll
release them as soon as testing reports come in.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/885998
Title:
facter upgrade cra
This bug was fixed in the package facter - 1.5.6-2ubuntu2.3
---
facter (1.5.6-2ubuntu2.3) lucid-proposed; urgency=low
* lib/facter/ec2.rb: Rescue condition in can_connect() when timeout()
actually has a chance to timeout. (LP: #885998)
-- Adam GandelmanMon, 07 Nov 2011 10:1
Hi, I tested the package on Lucid and confirm that it fixes the bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/885998
Title:
facter upgrade crashes puppet
To manage notifications about this bug
Hello majordom, or anyone else affected,
Accepted into lucid-proposed, the package will build now and be
available in a few hours. Please test and give feedback here. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed. Thank you in advance!
** Als
Adam Gandelman graciously pointed out that he already had branches to
fix this. Looking at the changes, they're the minimum to fix the
regression and are a better fix than the more invasive back-porting I
was looking at. I've also verified his changes on lucid running on EC2,
and in a VM.
--
Yo
I just checked the change that David posted and it breaks retrieval of
EC2 facts.
In the upstream repository (as of
d62e079489c07201cb343f2ca109fecd62d6e567, and later refactored in
cc67a0148b97e315572cdb905476df1224a78dd5) the can_connect? method
started only being called if a couple of additiona
I just ran into this issue this afternoon on my own servers. The issue
is definitely related to the ec2.rb changes in facter 1.5.6-2ubuntu2.2.
As a temporary hack/workaround I was able to get Puppet working again by
manually editing /usr/lib/ruby/1.8/facter/ec2.rb and reverting the
"can_connect?"
** Branch linked: lp:~gandelman-a/ubuntu/lucid/facter/732953_fixregress
** Branch linked: lp:~gandelman-a/ubuntu/natty/facter/732953_fixregress
** Branch linked:
lp:~gandelman-a/ubuntu/maverick/facter/732953_fixregress
--
You received this bug notification because you are a member of Ubuntu
Bug
I can confirm that rolling back to facter_1.5.6-2ubuntu2 resolves the
issue on 10.04 LTS.
I'm using puppet 2.6.1-0ubuntu2 from the lucid-backports repo.
In addition, I see the following traceback using facter_1.5.6-2ubuntu2.2
when running `facter --debug`:
# facter --debug
/usr/lib/ruby/1.8/tim
** Tags added: regression-update
** Changed in: facter (Ubuntu)
Importance: Undecided => Critical
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/885998
Title:
facter upgrade crashes puppet
To ma
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: facter (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/885998
Title:
fact
21 matches
Mail list logo
