Thanks for the feedback everyone. I'll give a chance to others to test
it over the weekend, if I get no negative feedback until Monday I'll be
uploading this fix to kinetic and SRU it to jammy.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Thank you very much, your help to fix the 5.5 agent package (we noticed the
symlink error, too) is really appreciated.
I was very happy that we can just use the puppet 5.5 agent package straight
from Ubuntu 22 to use our well established puppet 5.5 server so we do not have
to setup an all new
Thanks Lucas. LGTM. We tried the PPA. No errors during puppet apply.
File resources, both symlinks and regular files, are being created as
expected. Our full 5kloc puppet manifest applied without any puppet
errors, and we haven't noticed any other regressions. If you have any
specific
Hi all,
I prepared a patch myself to fix this. Could you please test the package
in this PPA?
https://launchpad.net/~lucaskanashiro/+archive/ubuntu/puppet/
This is a workaround and I'd like to make sure this is not impacting
anything else. Please, report back with your findings. Once we get
If I understand correctly (based on comment #24), does this mean that
the to_sym error seems to be a regression introduced by the patch
currently in jammy-proposed, right? In this case I think we need to
either switch this to verification-failed or at least to verification-
needed. Let me switch
Thanks for the reproducer Mat! I can reproduce it locally now, and this
is also impacting kinetic. I'll be working on it.
** Changed in: puppet (Ubuntu Kinetic)
Status: Fix Released => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
My test is also unnecessarily complex -- there's no needs for the class
+ include:
file { '/tmp/issue':
ensure => file,
source => '/etc/issue',
}
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi Lucas, the new to_sym error seems to be related to use of the File
resource with `ensure => file` instead of link. Unless there's another
change introduced in 5.5.22-4ubuntu0.1, it seems like it has to be
caused by your patch.
Here's my test scenario that you should be able to use to
As you can see in comment #17, I have not been able to reproduce the
error people are reporting, so I can't help with this analysis. From
what I understood, this is not crashing anything (like it is right now
when someone tries to create a symlink).
--
You received this bug notification because
Chris, I think the main functionality works OK (i.e. it creates a link),
but I'm confused what are those errors and what do they mean?
Also I'm going to continue with more configuration and see if we get any
more errors or all this is fine.
ср, 25 трав. 2022 р. о 06:16 Chris Halse Rogers
As an SRU team member, it's unclear to me whether the errors reported in
this verification are introduced by this update or are merely existing
problems that the code now hits because it's getting further.
It's also not clear to me what the effect of these errors is - if these
are just harmless
Since no one gave me a way yet to reproduce the mentioned errors
locally, and the originally reported bug (the symlink issue) is fixed, I
am marking the verification as done.
Please, file a new bug with reproduction steps for the error you all
mentioned, so I can investigate it further.
** Tags
Hi! I did several tests and looks like the symlink problem is resolved.
However still see those error messages listed above.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1969939
Title:
puppet 5
This bug was fixed in the package puppet - 5.5.22-4ubuntu1
---
puppet (5.5.22-4ubuntu1) kinetic; urgency=medium
* Backport upstream patches (LP: #1969939):
- d/p/0017-PUP-10537-keyword-param-as-last-arg.patch: Add patch to fix
ruby 3.0 incompatibilities.
-
To be honest, the bug initially reported here is fixed, I just tried
what is described in the Test Plan section and it works:
root@puppet-test:~# dpkg -l puppet
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/
I did some debugging, and the problem seems to appear in
/usr/lib/ruby/vendor_ruby/puppet/settings.rb
when interpolating $confdir in some internal config strings.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
According to the Gemfile, msgpack is not a mandatory dependency, so in
theory the lack of ruby-msgpack should not be a big deal. From Gemfile:
gem "msgpack", :require => false
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Naw, sorry, didn't fix the to_sym message, just fixed the missing
msgpack.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1969939
Title:
puppet 5 package incompatible with ruby 3 / ubuntu 22.04
To
Hi,
sorry, I'm currently beeing on a trip, sitting in a hotel with rather
limited technical equipment.
I also ran into this undefined method `to_sym' for nil:NilClass problem,
but I also found the error message
Failed to load library 'msgpack' for feature 'msgpack': cannot load such
file --
and this one:
Error: /Stage[main]/Linux::Common/File[/etc/apt/apt.conf.d]: Failed to generate
additional resources using 'eval_generate': undefined method `to_sym' for
nil:NilClass
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi! Just created a test VM with 22.04 (updated to latest), and I have
such code:
file { '/etc/localtime':
ensure => 'link',
target => $osfamily ? {
'Debian' =>
'/usr/share/zoneinfo/posix/America/Los_Angeles',
I apologize for not responding earlier to testing the solutiion for the
bug I've reported, but I'm currently on a trip, was busy the last days,
and don't have my ttesting environment with me. I'll test as soon as
poosible.
--
You received this bug notification because you are a member of Ubuntu
Hi Lucas! Here's the output of puppet agent --test --verbose --debug,
near the error messages. puppet agent does exit with 0 and otherwise
does the run properly (my test was to delete one of the symlinks I have
in my node specification and it is correctly recreated). I'll try to
build a new
Thanks for testing the proposed package Adrián. Unfortunately, the
output you presented does not help much in identifying the root cause of
the error you got. Could you please try to pass '--verbose' and '--
debug' to see if we get more useful information? Just to make sure, by
the end of the
Can confirm the package solves this issue. When running puppet agent
--test I now have other error messages like this:
Error: /File[/var/cache/puppet/facts.d]: Failed to generate additional
resources using 'eval_generate': undefined method `to_sym' for nil:NilClass
Error:
Hello Hadmut, or anyone else affected,
Accepted puppet into jammy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/puppet/5.5.22-4ubuntu0.1 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Merge proposal linked:
https://code.launchpad.net/~lucaskanashiro/ubuntu/+source/puppet/+git/puppet/+merge/421342
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1969939
Title:
puppet 5
** Description changed:
+ [Impact]
+
+ puppet crashes if one tries to create/ensure symlinks via a puppet
+ manifest. I believe this is an feature broadly used by our users.
+
+ [Test Plan]
+
+ $ lxc launch ubuntu-daily:jammy puppet-test
+ $ lxc shell puppet-test
+ # apt update && apt install
** Changed in: puppet (Debian)
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1969939
Title:
puppet 5 package incompatible with ruby 3 / ubuntu 22.04
To manage
** Bug watch added: Debian Bug tracker #1009643
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009643
** Also affects: puppet (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009643
Importance: Unknown
Status: Unknown
--
You received this bug notification
** Merge proposal linked:
https://code.launchpad.net/~lucaskanashiro/ubuntu/+source/puppet/+git/puppet/+merge/420947
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1969939
Title:
puppet 5
After a more in-deep analysis and trying to backport the patches
mentioned above I noticed some of them are not even applicable to the
version we have in the archive. The following patches will be added to
Kinectic, and later on backported to Jammy:
* PUP-10537
Thanks for the reply Hadmut. We should indeed try to fix the current
version we have in Ubuntu while Debian maintainers sort out the update
to a newer version.
What you described is indeed one of the issue we have with version
5.5.22-4, in Jammy and Kinetic. I did some investigation in the
At least as far as I have tested with my puppet installations, it is
just a single line of code that needs to be fixed:
Line 124 in /usr/lib/ruby/vendor_ruby/puppet/file_system/file_impl.rb
FileUtils.symlink(path, dest, options)
where ruby 3 accepts only two unnamed parameters here.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: puppet (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/1969939
Title:
** Tags added: server-todo
** Changed in: puppet (Ubuntu)
Assignee: (unassigned) => Lucas Kanashiro (lucaskanashiro)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1969939
Title:
puppet 5
36 matches
Mail list logo
