Bug#984603: puppet-master-passenger crashes when ruby-scanf is not installed
Package: puppet
Version: 5.5.22-2
Followup-For: Bug #984603
X-Debbugs-Cc: kie...@koumbit.org
Dear Maintainer,
this issue also affects the puppet package. For example, it can be reproduced
using the
following command:
$ puppet apply -e '"42".scanf("%i") |$x| { notify {"x": message => $x,} }'
Error: Could not run: cannot load such file -- scanf
Installing ruby-scanf solves the issue.
$ apt install ruby-scanf
...
$ puppet apply -e '"42".scanf("%i") |$x| { notify {"x": message => $x,} }'
Notice: Compiled catalog for pc-bullseye.test in environment production in 0.02
seconds
Notice: 42
Notice: /Stage[main]/Main/Notify[x]/message: defined 'message' as 42
Notice: Applied catalog in 0.01 seconds
Considering that scanf is a core puppet DSL function, I would like to propose
that ruby-scanf
be added as a dependency of the puppet package.
The issue persists in 5.5.22-4 (unstable, at the time of this writing). I
expect but have not
confirmed that the version in experimental does not have this issue.
This issue is similar to the upstream issue:
https://tickets.puppetlabs.com/browse/PUP-10797
thanks,
kienan
-- System Information:
Debian Release: 11.3
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 5.10.0-14-amd64 (SMP w/2 CPU threads)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8) (ignored: LC_ALL
set to en_CA.UTF-8), LANGUAGE=en_CA.UTF-8
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages puppet depends on:
ii adduser 3.118
ii facter 3.14.12-1+b2
ii hiera3.2.0-2.1
ii init-system-helpers 1.60
ii lsb-base 11.1.0
ii ruby 1:2.7+2
ii ruby-augeas 1:0.5.0-3+b8
ii ruby-deep-merge 1.1.1-1
ii ruby-shadow 2.5.0-1+b4
Versions of packages puppet recommends:
ii debconf-utils 1.5.77
ii lsb-release11.1.0
ii ruby-selinux 3.1-3
Versions of packages puppet suggests:
pn ruby-hocon
pn ruby-rrd
-- Configuration Files:
/etc/puppet/auth.conf changed [not included]
/etc/puppet/puppet.conf changed [not included]
-- no debconf information
Bug#994843: puppetdb: Frequent command submissions failures with jetty 9.4.16-0+deb10u1
Package: puppetdb
Version: 6.2.0-3
Severity: important
X-Debbugs-Cc: kie...@koumbit.org
Dear Maintainer,
I'm not sure whether this bug applies more to puppetdb or libjetty9-java, but I
will start the report here.
After libjetty9-java upgraded from 9.4.15-1 to 9.4.16-0+deb10u1 frequent puppet
agent run errors started happening, with a vague error:
Error: Could not retrieve catalog from remote server: Error 500 on SERVER:
Server Error: Failed to execute
'/pdb/cmd/v1?checksum=9c18923b33f99552a5e49974ae5ff05be74fb672=9=xxx.example.com=replace_catalog=2021-09-20T20:13:16.121Z'
on at least 1 of the following 'server_urls': https://puppet:8081
The error didn't happen regularly for all nodes, but seemed to affect nodes
with larger catalogs more frequently.
While testing, I enabled to the debug logging in the puppetdb logback.xml.
During the runs that failed, I found a backtrace with the error:
2021-09-20T18:33:07.796-04:00 DEBUG [o.e.j.i.WriteFlusher] ignored:
WriteFlusher@23e9cdf8{IDLE}->null
javax.net.ssl.SSLHandshakeException: Encrypted buffer max length exceeded
A more complete version is towards the end of this report. There is a jetty
release that covered a possibly related issue:
https://github.com/eclipse/jetty.project/issues/6121
Verifying against our monitoring history, which contains information on the
puppet run failures, I noticed that the date corresponded with when the jetty
version changed. By downgrading, I was able to confirm that it fixed the
situation. As I said at the beginning I'm not sure if the fault here is in
puppetdb, or in libjetty9-java.
Please let me know if you need more information.
Debian release: buster
# apt policy
Package files:
100 /var/lib/dpkg/status
release a=now
500 http://deb.debian.org/debian buster/contrib amd64 Packages
release v=10.10,o=Debian,a=oldstable,n=buster,l=Debian,c=contrib,b=amd64
origin deb.debian.org
500 http://deb.debian.org/debian buster/main amd64 Packages
release v=10.10,o=Debian,a=oldstable,n=buster,l=Debian,c=main,b=amd64
origin deb.debian.org
500 http://deb.debian.org/debian buster-updates/main amd64 Packages
release
o=Debian,a=oldstable-updates,n=buster-updates,l=Debian,c=main,b=amd64
origin deb.debian.org
500 http://security.debian.org/debian-security buster/updates/main amd64
Packages
release v=10,o=Debian,a=oldstable,n=buster,l=Debian-Security,c=main,b=amd64
origin security.debian.org
2021-09-20T18:33:07.796-04:00 DEBUG [o.e.j.i.WriteFlusher] ignored:
WriteFlusher@23e9cdf8{IDLE}->null
javax.net.ssl.SSLHandshakeException: Encrypted buffer max length exceeded
at
org.eclipse.jetty.io.ssl.SslConnection$DecryptedEndPoint.fill(SslConnection.java:613)
at
org.eclipse.jetty.server.HttpConnection.fillRequestBuffer(HttpConnection.java:340)
at
org.eclipse.jetty.server.HttpConnection.fillAndParseForContent(HttpConnection.java:313)
at
org.eclipse.jetty.server.HttpInputOverHTTP.produceContent(HttpInputOverHTTP.java:33)
at org.eclipse.jetty.server.HttpInput.nextContent(HttpInput.java:369)
at org.eclipse.jetty.server.HttpInput.read(HttpInput.java:301)
at java.base/java.io.InputStream.transferTo(InputStream.java:704)
at java.base/java.nio.file.Files.copy(Files.java:3078)
at puppetlabs.stockpile.queue$write_stream.invokeStatic(queue.clj:102)
at puppetlabs.stockpile.queue$write_stream.invoke(queue.clj:100)
at puppetlabs.stockpile.queue$store$fn__6587.invoke(queue.clj:282)
at puppetlabs.stockpile.queue$store.invokeStatic(queue.clj:281)
at puppetlabs.stockpile.queue$store.invoke(queue.clj:228)
at
puppetlabs.puppetdb.queue$eval21400$store_in_stockpile__21405$fn__21406.invoke(queue.clj:288)
at
puppetlabs.puppetdb.queue$eval21400$store_in_stockpile__21405.invoke(queue.clj:283)
at
puppetlabs.puppetdb.queue$eval21432$store_command__21437$fn__21438.invoke(queue.clj:321)
at
puppetlabs.puppetdb.queue$eval21432$store_command__21437.invoke(queue.clj:317)
at
puppetlabs.puppetdb.command$eval37528$do_enqueue_command__37533$fn__37537$fn__37539.invoke(command.clj:253)
at
puppetlabs.puppetdb.command.proxy$java.lang.Object$Callable$7da976d4.call(Unknown
Source)
at com.codahale.metrics.Timer.time(Timer.java:101)
at
puppetlabs.puppetdb.command$eval37528$do_enqueue_command__37533$fn__37537.invoke(command.clj:252)
at
puppetlabs.puppetdb.command$eval37528$do_enqueue_command__37533.invoke(command.clj:244)
at
puppetlabs.puppetdb.command$reify__37765$service_fnk__23931__auto___positional$reify__37775.enqueue_command(command.clj:728)
at
puppetlabs.puppetdb.command$eval37650$fn__37651$G__37638__37667.invoke(command.clj:420)
at
puppetlabs.puppetdb.command$eval37650$fn__37651$G__37637__37684.invoke(command.clj:420)
at clojure.lang.AFn.applyToHelper(AFn.java:195)
at
Bug#993994: vulkan-validationlayers: Requesting VK_LAYER_KHRONOS_validation crash with undefined symbol: _Z14GetEnvironmentB5cxx11PKc
Package: vulkan-validationlayers Version: 1.2.189.0-1 Severity: grave Justification: renders package unusable X-Debbugs-Cc: kienan.stew...@burntworld.ca Dear Maintainer, I am developing an application that uses vulkan, and for debugging includes the validation layer. After a recent upgrade to 1.2.189.0-1, the application began crashing with the following error symbol lookup error: /lib/x86_64-linux-gnu/libVkLayer_khronos_validation.so: undefined symbol: _Z14GetEnvironmentB5cxx11PKc I think the previous working version I had installed was 1.2.162.0-1. I am able to run the application when not requesting the validation layer. I was also able to reproduce this issue by doing the following * Opening qrenderdoc * Selecting a vulkan-based application, eg. /usr/bin/vkcube (from vulkan-tools) * Running the application with the default settings (will work) * Now, check the "Enable API Validation" under the Launch Application capture options * Running the application will cause it to immediately crash /usr/bin/vkcube: symbol lookup error: /lib/x86_64-linux-gnu/libVkLayer_khronos_validation.so: undefined symbol: _Z14GetEnvironmentB5cxx11PKc This appears related to upstream issue https://github.com/KhronosGroup/Vulkan-ValidationLayers/issues/2941 where jengelh resolved it in OpenSuse by prefixing the GetEnvironment declaration in layers/vk_layer_config.h with VK_LAYER_EXPORT. Ref: https://build.opensuse.org/package/view_file/openSUSE:Factory/vulkan-validationlayers/ver.diff?expand=1 thanks, kienan -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-8-amd64 (SMP w/12 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages vulkan-validationlayers depends on: ii libc6 2.32-2 ii libgcc-s1 11.2.0-4 ii libstdc++6 11.2.0-4 vulkan-validationlayers recommends no packages. vulkan-validationlayers suggests no packages. -- no debconf information
Bug#960472: ITP: python-readchar -- Python library to portable read single characters and key-strokes
Package: wnpp Severity: wishlist Owner: Kienan Stewart * Package name: python-readchar Version : 2.0.0 Upstream Author : Miguel Ángel García * URL : https://github.com/magmax/python-readchar * License : MIT Programming Lang: Python Description : Python library to portable read single characters and key-strokes The library provides a small class which sets up the key id for various platforms to provide a unified interface for developers to use when reading keystrokes in Python. This package is a dependency of python-inquirer. I will need to find a sponsor for the upload of this package.
Bug#960470: ITP: python-inquirer -- Collection of common interactive command line user interfaces in python
Package: wnpp Severity: wishlist Owner: Kienan Stewart * Package name: python-inquirer Version : 2.6.3 Upstream Author : Miguel Ángel García * URL : https://github.com/magmax/python-inquirer * License : MIT Programming Lang: Python Description : Collection of common interactive command line user interfaces in python This package provides a library of common interactive CLI interfaces based on Inquirer.js. This library should ease the process of asking end user questions, parsing, validating answers, managing hierarchical prompts and providing error feedback. I will need to find a sponsor to upload this package.
Bug#930562: Not migrated to testing yet
Hi, I see that a source upload was done and the updated version of the package (1.7.0-4) has passed into testing - thanks! Is there something that needs to be done to get the process started for inclusion in the buster repo? PuppetDB doesn't really work properly without the fixed version (we're running 1.7.0-4) installed manually in production. Without it, puppet runs from nodes will not work after PuppetDB restarts. Thanks, Kienan signature.asc Description: PGP signature
Bug#923976: [Pkg-puppet-devel] Bug#923976: Bug#923976: puppet: Reports submitte
On Tue, Mar 12, 2019 at 10:22:52AM +0200, Apollon Oikonomopoulos wrote: > Control: tags -1 - moreinfo + patch pending > Control: severity -1 serious > > OK, thanks for confirming this and thanks for the detailed report, it's > very helpful! > > I'm bumping this bug to RC, as I don't think Puppet report storage > should break merely by installing an unrelated Ruby package. > Additionally this is a regression from Puppet 4.x. > > So, here's what's happening: > > - Puppet 5 switched from a custom wire format (PSON) to JSON for >transmitting facts and reports. > - There is no issue when using the ruby-json JSON library to parse >reports. > - Some JSON libraries (Oj and JrJackson) de-serialize floats with many >decimal digits - such as the timing metrics found in a Puppet agent >report - as BigDecimal. > - When BigDecimal's are serialized again to JSON, they are serialized >as Strings (and not floats), causing PuppetDB's schema validation to >fail. > - This path is only triggered when ruby-oj and ruby-multi-json are >installed, enabling Puppet to use Oj via multi-json. (JrJackson is >Jruby-only, and there are provisions upstream handling BigDecimal >conversion in this case). > > Your patch fixes the issue, but it does so right before the report is > transmitted to PuppetDB. I think it's best to instruct Oj to never > deserialize floats as BigDecimals and avoid having to do any conversions > in the first place. Additionally, this will guard all other report > processors (e.g. store) which might want to handle metrics against > similar issues. > > Can you test the attached patch and confirm that it works? > Hi, I applied the patch (reloaded apache2 afterwards) and runs are able to store reports now. (I did confirm before the patch was applied that the reports were not being stored). Thanks for the great explanation, your effort and time, and the patch! Thanks, Kienan > Regards, > Apollon signature.asc Description: PGP signature
Bug#923976: [Pkg-puppet-devel] Bug#923976: Bug#923976: puppet: Reports submitte
Hi Apollon, On Sat, Mar 09, 2019 at 11:24:27PM +0200, Apollon Oikonomopoulos wrote: > Control: tags -1 - unreproducible > > Hi, > > > Thanks for the patch, it should do the trick. However, before applying > it I want to be 100% sure that we know what's happening and why. > > So, I managed to reproduce this by simply installing ruby-multi-json, > which allows Puppet to use different json backends. Can you verify that > ruby-multi-json is installed, presumably on the master? > ruby-multi-json (1.12.1-1) is installed. Checking with 'apt-cache policy rdepends ruby-multi-json', it's like because we use r10k > Thanks, > Apollon Thanks, Kienan signature.asc Description: PGP signature
Bug#923976: [Pkg-puppet-devel] Bug#923976: Bug#923976: puppet: Reports submitte
Hi,
I have made a patch which seems to resolve the issue. I'm not at all confident
it's in the right place. The patch applies to the PuppetDB source which is used
to make the puppet-terminus-puppetdb package.
diff --git a/puppet/lib/puppet/reports/puppetdb.rb
b/puppet/lib/puppet/reports/puppetdb.rb
index d3f0c07..b78f02c 100644
--- a/puppet/lib/puppet/reports/puppetdb.rb
+++ b/puppet/lib/puppet/reports/puppetdb.rb
@@ -129,7 +129,7 @@ Puppet::Reports.register_report(:puppetdb) do
[:puppetdb, :metrics_list, :build]) do
metrics_list = []
metrics.each do |name, data|
-metric_hashes = data.values.map {|x| {"category" => data.name, "name"
=> x.first, "value" => x.last}}
+metric_hashes = data.values.map {|x| {"category" => data.name, "name"
=> x.first, "value" => x.last.to_f}}
metrics_list.concat(metric_hashes)
end
metrics_list
I'm not aware if there will be consequences to forcing all the metrics values to
floats.
Thanks,
Kienan
signature.asc
Description: PGP signature
Bug#923976: [Pkg-puppet-devel] Bug#923976: Bug#923976: puppet: Reports submitte
Hi,
I've been digging around a bit more and I think I have an idea to help narrow
the conditions in which I'm seeing this error.
I re-configured a test box to output the report to disk and to PuppetDB so I
was able to compare the data sent.
I see a correlation between time metrics stored a Ruby.BigNumber and all the
failed metrics when trying store the report in PuppetDB. Since the metrics
values with differ from run to run, it could be possible to have runs which
are able to be stored without this specific error.
A summary comparison table is available in the attachment
reports-errors-summary.tsv.
To produce this I took the error line from the PuppetDB log
(report-puppetdb_error.log)
where traceback lists details of "value does not match schema"
:cause "Value does not match schema: {:metrics [nil nil nil nil nil nil nil
nil nil nil nil nil {:value (not (instance? java.lang.Number
a-java.lang.String))} nil {:value (not (instance? java.lang.Number
a-java.lang.String))} {:value (not (instance? java.lang.Number
a-java.lang.String))} nil nil nil {:value (not (instance? java.lang.Number
a-java.lang.String))} nil {:value (not (instance? java.lang.Number
a-java.lang.String))} nil nil {:value (not (instance? java.lang.Number
a-java.lang.String))} nil {:value (not (instance? java.lang.Number
a-java.lang.String))} nil {:value (not (instance? java.lang.Number
a-java.lang.String))} {:value (not (instance? java.lang.Number
a-java.lang.String))} nil nil nil nil {:value (not (instance? java.lang.Number
a-java.lang.String))} nil nil nil nil {:value (not (instance? java.lang.Number
a-java.lang.String))} nil nil nil nil nil]}"
Each nil value I assumed to be not an error. I lined these values up in
appearance
order with the metrics data from the same log. (I won't paste the entire line
here
since it's quite long).
I then got the corresponding value from the report stored on disk (attached
as report-stored.yaml).
Note: for these reports I was using our puppetmaster manifest, so there are more
resource metrics than on an example with an empty manifest.
Thanks,
Kienan
resourceschanged1nil
resourcescorrective_change1nil
resourcesfailed0nil
resourcesfailed_to_restart0nil
resourcesout_of_sync1nil
resourcesrestarted0nil
resourcesscheduled0nil
resourcesskipped0nil
resourcestotal715nil
timealternatives0.023357004nil
timeanchor8.95E-04nil
timeaugeas0.089786623nil
timecatalog_application4.96E+00{:value (not (instance? java.lang.Number a-java.lang.String))}ruby/object:BigDecimal27:0.49594088389994795e1
timeconcat_file0.001357939nil
timeconcat_fragment5.54E-03{:value (not (instance? java.lang.Number a-java.lang.String))} ruby/object:BigDecimal36:0.553882705e2
timeconfig_retrieval7.15E+00{:value (not (instance? java.lang.Number a-java.lang.String))} ruby/object:BigDecimal27:0.7151159435435e1
timeconvert_catalog0.544536797000546nil
timecron0.014934991nil
timeexec0.020149716nil
timefact_generation2.20E+00{:value (not (instance? java.lang.Number a-java.lang.String))} ruby/object:BigDecimal27:0.21955279620005967e1
timefile1.173581222nil
timefile_line2.55E-02{:value (not (instance? java.lang.Number a-java.lang.String))} ruby/object:BigDecimal36:0.255076198e1
timefilebucket1.11E-04nil
timegroup7.41E-04nil
timeini_setting1.27E-02{:value (not (instance? java.lang.Number a-java.lang.String))} ruby/object:BigDecimal36:0.126739428e1
timemailalias5.89E-04nil
timenode_retrieval6.56E+00{:value (not (instance? java.lang.Number a-java.lang.String))} ruby/object:BigDecimal27:0.6560879654185e1
timepackage0.009044969nil
timeplugin_sync1.49E+00{:value (not (instance? java.lang.Number a-java.lang.String))} ruby/object:BigDecimal27:0.1485196431767e1
timepostgresql_conf3.16E-04{:value (not (instance? java.lang.Number a-java.lang.String))} ruby/object:BigDecimal36:0.315886003e3
timepostgresql_conn_validator0.054996048nil
timepostgresql_psql1.220987548nil
timepuppetdb_conn_validator0.033792702nil
timeresources6.83E-05nil
timeservice2.94E-01{:value (not (instance? java.lang.Number a-java.lang.String))} ruby/object:BigDecimal27:0.2937224029997e0
timessh_authorized_key0.0013181nil
timesshkey8.07E-04nil
timetotal22.909333186nil
timetransaction_evaluation4.70985980499972nil
timeuser3.47E-02{:value (not (instance? java.lang.Number a-java.lang.String))} ruby/object:BigDecimal36:0.346835945e1
timevcsrepo0.055521215nil
changestotal1nil
eventsfailure0nil
eventssuccess1nil
eventstotal1nil
2019-03-08T11:03:59.479-05:00 INFO [p.p.command] [16-1552061039324] [86 ms]
'replace facts' command processed for pm-buster.test
2019-03-08T11:04:05.158-05:00 INFO [p.p.command] [17-1552061044601] [178 ms]
'replace catalog' command processed for pm-buster.test
2019-03-08T11:04:12.519-05:00 ERROR [p.p.command] [18] [store report] Fatal
error on attempt 0 for pm-buster.test
clojure.lang.ExceptionInfo: throw+: {:fatal true, :cause #error {
:cause "Value does not
Bug#923976: [Pkg-puppet-devel] Bug#923976: Bug#923976: puppet: Reports submitte
On Fri, Mar 08, 2019 at 04:34:39PM +0200, Apollon Oikonomopoulos wrote: > Control: tags -1 unreproducible moreinfo > > > Turns out this is already enabled and running in our tests without > issues. I'm unable to trivially reproduce this, which makes me wonder if > it's a matter of the terminus version. Which version of the > puppet-terminus-puppetdb package are you using on the master? puppet-terminus-puppetdb is currently 6.2.0-3 > > Regards, > Apollon signature.asc Description: PGP signature
Bug#923976: [Pkg-puppet-devel] Bug#923976: puppet: Reports submitte
Hi,
On Fri, Mar 08, 2019 at 03:47:02PM +0200, Apollon Oikonomopoulos wrote:
> Hi,
>
> Thanks for the report!
>
> On 14:54 Thu 07 Mar , Kienan wrote:
> > When running puppet 5.x with reports enabled and sent to PuppetDB 6.x,
> > PuppetDB fails to store the report with the following error:
> >
> > 2019-03-01T17:06:01.396-05:00 ERROR [p.p.command] [100] [store report]
> > Fatal error on attempt 0 for pm-buster.test
> > clojure.lang.ExceptionInfo: throw+: {:fatal true, :cause #error {
> > :cause "Value does not match schema: {:metrics [nil nil nil nil nil nil
> > nil nil nil nil nil nil {:value (not (instance? java.lang.Number
> > a-java.lang.String))} {:value (not (instance? java.lang.Number
> > a-java.lang.String))} nil {:value (not (instance? java.lang.Number
> > a-java.lang.String))} nil {:value (not (instance? java.lang.Number
> > a-java.lang.String))} nil {:value (not (instance? java.lang.Number
> > a-java.lang.String))} {:value (not (instance? java.lang.Number
> > a-java.lang.String))} {:value (not (instance? java.lang.Number
> > a-java.lang.String))} nil nil {:value (not (instance? java.lang.Number
> > a-java.lang.String))} nil {:value (not (instance? java.lang.Number
> > a-java.lang.String))} nil {:value (not (instance? java.lang.Number
> > a-java.lang.String))} nil nil nil nil nil nil nil nil nil {:value (not
> > (instance? java.lang.Number a-java.lang.String))} nil nil nil nil nil
> > nil]}"
> >
> > A copy of the Puppet DB log file is attached with the complete
> > backtrace.
> >
> > I'm filing this bug against the puppet package for the following reasons
> >
> > * hosts running puppet 4.x (stretch) are able to submit reports to same
> > version of Puppet DB.
>
> So, this sounds like a regression. I would not be surprised if Puppet 4
> nodes failed to work with PuppetDB 6, but this is clearly a bug.
>
> > * I am able to "solve" the problem by modifying a number of places in
> > the puppet agent files where report information is returned and calling
> > "to_i" or "to_f" to force casting into a numeric value instead of a
> > string.
> >
> > The metrics keys affected include: convert_catalog and
> > transaction_evaluation. The keys affected may change depending on the
> > manifest used for the node.
> >
> > This being said, it may be appropriate to move this bug to the PuppetDB
> > package. I haven't been able to find any upstream bugs regarding this
> > behaviour.
> >
> > To reproduce:
> >
> > 1. Install puppet, puppet-master-passenger, and puppetdb on the same
> > host.
> > 2. Configure the puppet master to storeconfigs with the PuppetDB and the
> > agent to submit reports:
> >
> > (snippet from /etc/puppet.conf)
> >
> > [main]
> > reports = puppetdb
>
> Note to self: let's add report storage to the puppet/puppetdb
> autopkgtests.
>
> > [master]
> > storeconfigs = true
> > storeconfig_backend = true
> > [agent]
> > report = true
> >
> > 3. Run puppet using a minimal node manifest:
> >
> > node 'pm-buster.test' {
> >
> > }
> >
> > 4. The puppet run should complete successfully with no additional
> > output.
> > 5. Check the PuppetDB log at /var/log/puppetdb/puppetdb.log there should
> > be an error submitting the report present.
> >
> > Note: this affects hosts running puppet 5.x which submit their reports
> > to the puppet master as well.
>
> Does this mean that storing reports on the Puppet master is also broken?
>
Do you mean storing reports as a file in addition to sending them to PuppetDB,
or something else? I can do a test with storing reports as files as well if
that would be useful.
What I meant here is that: with the configuration I'm using all reports for
nodes are stored in PuppetDB and a 5.x client connected to the puppet master
will have the reports fail to be stored in the same way. So this affects more
than just a node running the puppet master itself.
> >
> > I would expect normally that reports are able to be stored without
> > error.
>
> Agreed. This is definitely worth fixing for Buster, I'll look into it.
>
> Thanks,
> Apollon
Thanks for taking to time to look into it!
Kienan
signature.asc
Description: PGP signature
Bug#919737: underscore: FTBFS (ERROR: `underscore.min.map` is not a supported option)
user debian-rele...@lists.debian.org usertag 919737 + bsp-2019-01-ca-montreal tags 919737 + unreproducible moreinfo thank you Hi, I tried building this package (underscore-1.8.3~dfsg) in a clean buster chroot (with sbuild) and a clean unstable chroot (also with sbuild), and it worked in both cases. Thanks, Kienan signature.asc Description: PGP signature
Bug#904657: update
user debian-rele...@lists.debian.org usertags 904657 + bsp-2019-01-ca-montreal tags 904657 + patch thank you Hi, I tested a proposed patch from the upstream github repository which allows the package to build and run : https://github.com/snare/voltron/pull/243 I'm not sure if there are other side-effects to the patch, since the async (now asynchronous) variable is not directly used but could be referred to elsewhere. Thanks, Kienan
Bug#890689: ruby-rgen FTBFS with ruby 2.5
Hi,
These errors happen in ruby >= 2.4 since Fixnum and Bignum were merged into
Integer.
The following upstream commit fixes the issue:
https://github.com/mthiede/rgen/commit/1124f4303db52973967e78d93512a1c1b64f23cf
Attached is a patch to the debian source from
https://salsa.debian.org/ruby-team/ruby-rgen which applies the above commit.
Thanks,
Kienan
diff --git a/debian/patches/fix-test-for-ruby-2.4 b/debian/patches/fix-test-for-ruby-2.4
new file mode 100644
index 000..bb94b79
--- /dev/null
+++ b/debian/patches/fix-test-for-ruby-2.4
@@ -0,0 +1,52 @@
+Description: Fix tests for ruby 2.4
+ This applies commit 1124f4303db52973967e78d93512a1c1b64f23cf which
+ lets the tests pass. In ruby 2.4 Fixnum and Bignum were merged into
+ Integer
+ .
+ ruby-rgen (0.8.0-1) unstable; urgency=medium
+ .
+ [ Cédric Boutillier ]
+ * Bump debhelper compatibility level to 9
+ * Remove version in the gem2deb build-dependency
+ * Use https:// in Vcs-* fields
+ * Bump Standards-Version to 3.9.7 (no changes needed)
+ * Run wrap-and-sort on packaging files
+ .
+ [ Stig Sandbeck Mathisen ]
+ * Declare compliance with Debian policy 3.9.8
+ * Imported upstream release 0.8.0
+Author: Stig Sandbeck Mathisen
+
+Origin: https://github.com/mthiede/rgen/commit/1124f4303db52973967e78d93512a1c1b64f23cf
+Bug-Debian: https://bugs.debian.org/890689
+Last-Update: 2019-01-19
+
+--- ruby-rgen-0.8.0.orig/test/metamodel_builder_test.rb
ruby-rgen-0.8.0/test/metamodel_builder_test.rb
+@@ -186,7 +186,7 @@ class MetamodelBuilderTest < Test::Unit:
+ err = assert_raise StandardError do
+ sc.name = 5
+ end
+-assert_match /In (\w+::)+SimpleClass : Can not use a Fixnum where a String is expected/, err.message
++assert_match /In (\w+::)+SimpleClass : Can not use a (Integer|Fixnum) where a String is expected/, err.message
+ assert_equal "EString", mm::SimpleClass.ecore.eAttributes.find{|a| a.name=="name"}.eType.name
+
+ assert_equal "xtest", sc.stringWithDefault
+@@ -288,7 +288,7 @@ class MetamodelBuilderTest < Test::Unit:
+ err = assert_raise(StandardError) do
+ o.addLiterals(1)
+ end
+-assert_match /In (\w+::)+ManyAttrClass : Can not use a Fixnum where a String is expected/, err.message
++assert_match /In (\w+::)+ManyAttrClass : Can not use a (Integer|Fixnum) where a String is expected/, err.message
+
+ assert_equal [], o.literals
+ o.addLiterals("a")
+@@ -323,7 +323,7 @@ class MetamodelBuilderTest < Test::Unit:
+ err = assert_raise(StandardError) do
+ o.literals = 1
+ end
+-assert_match /In (\w+::)+ManyAttrClass : Can not use a Fixnum where a Enumerable is expected/, err.message
++assert_match /In (\w+::)+ManyAttrClass : Can not use a (Integer|Fixnum) where a Enumerable is expected/, err.message
+
+ o.bools = [true, false, true, false]
+ assert_equal [true, false, true, false], o.bools
diff --git a/debian/patches/series b/debian/patches/series
new file mode 100644
index 000..ae45377
--- /dev/null
+++ b/debian/patches/series
@@ -0,0 +1 @@
+fix-test-for-ruby-2.4
diff --git a/test/metamodel_builder_test.rb b/test/metamodel_builder_test.rb
index 4567a86..2ce7d2f 100644
--- a/test/metamodel_builder_test.rb
+++ b/test/metamodel_builder_test.rb
@@ -186,7 +186,7 @@ class MetamodelBuilderTest < Test::Unit::TestCase
err = assert_raise StandardError do
sc.name = 5
end
-assert_match /In (\w+::)+SimpleClass : Can not use a Fixnum where a String is expected/, err.message
+assert_match /In (\w+::)+SimpleClass : Can not use a (Integer|Fixnum) where a String is expected/, err.message
assert_equal "EString", mm::SimpleClass.ecore.eAttributes.find{|a| a.name=="name"}.eType.name
assert_equal "xtest", sc.stringWithDefault
@@ -288,7 +288,7 @@ class MetamodelBuilderTest < Test::Unit::TestCase
err = assert_raise(StandardError) do
o.addLiterals(1)
end
-assert_match /In (\w+::)+ManyAttrClass : Can not use a Fixnum where a String is expected/, err.message
+assert_match /In (\w+::)+ManyAttrClass : Can not use a (Integer|Fixnum) where a String is expected/, err.message
assert_equal [], o.literals
o.addLiterals("a")
@@ -323,7 +323,7 @@ class MetamodelBuilderTest < Test::Unit::TestCase
err = assert_raise(StandardError) do
o.literals = 1
end
-assert_match /In (\w+::)+ManyAttrClass : Can not use a Fixnum where a Enumerable is expected/, err.message
+assert_match /In (\w+::)+ManyAttrClass : Can not use a (Integer|Fixnum) where a Enumerable is expected/, err.message
o.bools = [true, false, true, false]
assert_equal [true, false, true, false], o.bools
Bug#918243: icinga2.6: Deadlocks when icinga2 is reloaded
Package: icinga2 Version: 2.6.0-2 Source: icinga2 Severity: important Dear Maintainer, We are encountering frequent deadlocks when icinga2 on master nodes is reloaded. I believe this is related to the upstream issue https://github.com/Icinga/icinga2/issues/5007. It's not entirely clear to me which PRs are linked, but it's noted the fix is 2.9. Is it possible to backport the fix from 2.9 into the 2.6 package or provide a 2.10 version in jessie-backports-sloppy? Unfortunately for now I cannot presently use the stretch-backports version as I have jessie icinga clients to support for some time and 2.10 package is not available in jessie-backports-sloppy. Thanks, Kienan signature.asc Description: PGP signature
Bug#916332: tiled: Error when starting tiled: undefined symbol: _ZTIN5Tiled20ObjectTemplateFormatE".
Package: tiled Version: 1.2.1+dfsg.1-1 Severity: important Dear Maintainer, I started tiled on the command line. When starting tiled from gnome (either the application menu or the quick command bar), there is no output. Thanks, Kienan -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (100, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.18.0-3-amd64 (SMP w/8 CPU cores) Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), LANGUAGE=en_CA.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages tiled depends on: ii libc6 2.28-2 ii libgcc1 1:8.2.0-12 ii libgl1 1.1.0-1 ii libqt5core5a5.11.2+dfsg-7 ii libqt5gui5 5.11.2+dfsg-7 ii libqt5network5 5.11.2+dfsg-7 ii libqt5widgets5 5.11.2+dfsg-7 ii libstdc++6 8.2.0-12 ii libtiled1 1.2.1+dfsg.1-1 tiled recommends no packages. tiled suggests no packages. -- no debconf information
Bug#915359: ITP: puppet-strings -- Puppet String generates documentation for Puppet code and extensions
Package: wnpp Severity: wishlist Owner: Kienan Stewart * Package name: puppet-strings Version : 2.1.0-1 Upstream Author : Puppet Labs Inc. * URL : https://github.com/puppetlabs/puppet-strings * License : Apache-2.0 Programming Lang: Ruby Description : Puppet String generates documentation for Puppet code and extensions Puppet Strings generates documentation for Puppet code and extensions written in Puppet and Ruby. Strings processes code and YARD-style code comments to create documentation in HTML, Markdown, or JSON formats. This package can be useful for people using Puppet in order to generate readable HTML documentation for a modules or entire control repositories. I will need a sponsor.
Bug#899193: RFS: vagrant-hostmanager/1.8.8-1 [ITP #898996]
Package: sponsorship-requests Severity: wishlist Dear menotrs, I am looking for a sponsor for my package "vagrant-hostmanager": * Package name: vagrant-hostmanager * Version : 1.8.8-1 * Upstream AUthor : Shawn Dahlen, Seth Reeser * URL : https://github.com/devopsgroup-io/vagrant-hostmanager * License : MPL-2.0 * Section : ruby To access further information about this package, please visit the following URL: https://mentors.debian.net/package/vagrant-hostmanager Thanks, Kienan
Bug#784764: RFP: cataclysm-dda -- post-apocalyptic roguelike game
Hi Reiner, were you still planning on packaging this software? I saw in #788254 you had uploaded a package to mentors some time ago. Thanks, Kienan signature.asc Description: PGP signature
Bug#898996: ITP: vagrant-hostmanager -- A plugin for Vagrant which manages entries in the hosts file for guests and, optionally, the host system
I've uploaded a first pass at creating a package on mentors.debian.net: https://mentors.debian.net/package/vagrant-hostmanager Please let me know if you have any feedback. Thanks, Kienan signature.asc Description: PGP signature
Bug#898996: ITP: vagrant-hostmanager -- A plugin for Vagrant which manages entries in the hosts file for guests and, optionally, the host system
Package: wnpp Severity: wishlist Owner: Kienan Stewart <kie...@koumbit.org> * Package name: vagrant-hostmanager Version : 1.8.8 Upstream Author : Shawn Dalen, Paulo Bittencourt, Seth Reeser, and contributors * URL : https://github.com/devopsgroup-io/vagrant-hostmanager/graphs/contributors * License : MPL-2.0 Programming Lang: Ruby Description : A plugin for Vagrant which manages entries in the hosts file for guests and, optionally, the host system >From the project description: vagrant-hostmanager is a Vagrant plugin that >manages the hosts file on guest machines (and optionally the host). Its goal >is to enable resolution of multi-machine environments deployed with a cloud >provider where IP addresses are not known in advance. Without using a plugin like this, host entries must be managed manually - especially when using dynamic IP allocation. Host entries in guests could be managed by provisioners in Vagrant files, or possibly some type of dnsmasq configurations. These options are either labour-intensive or complex. There are some other vagrant plugins that provide similar functionality, such as vagrant-hosts (https://github.com/oscar-stack/vagrant-hosts) which is limited to static IPs. From what I've seen, there are no packages presently in debian that offer similar I don't know ruby particularly well, nor the internals of vagrant plugins. I plan to maintain the package by following upstream releases. I will need a sponsor for the package. Thanks, Kienan
Bug#878193: fails to start with minimal dependencies from testing
Hi, I ran into the same issue. After a bit more debugging, I couldn't find precisely the set of dependencies which were required to be from testing or unstable. Using the following steps I could reliably install and puppetdb on stetch machine: ``` apt install -y postgresql dbconfig-no-thanks apt-get install -y -t unstable libclojure-java apt-get install -y -t testing libtools-nrepl-clojure libtools-cli-clojure libslf4j-java libjava-jdbc-clojure apt-get install -y openjdk-8-jre-headless # java-1.8 should be the default runtime, if it's not check update-alternatives apt-get install -y -t unstable puppetdb ``` I was attempting to make the install repeatable with a puppet class; however I kept having issues. In the end I diffed the dpkg states between a machine provisioned with puppet and a machine installed by hand. Using the above steps resulted in almost all the java packages installed being from testing or unstable. I spent some time seeing if there were specific packages that were key to making it run, but I couldn't figure out anything meaningful. My takeaway was to prefer *-java and *-clojure from unstable and it worked more neatly. If you'd like, I can post the dpkg states for each. Kienan signature.asc Description: PGP signature
Bug#886293: RFS: godot/2.1.4-1 [ITP #793057]
Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package "godot": * Package name: godot * Version : 2.1.4-1 * Upstream Author : Juan Linietsky, Ariel Manzur, Godot Engine contributors * URL : https://godotengine.org/ * License : MIT (and various others) * Section : games It builds those binary packages: godot2 - game engine with editor godot2-runner - game engine runtime without editor (used for running games) godot2-server - headless version of the game engine with tools for automation To access further information about this package, please visit the following URL: https://mentors.debian.net/package/godot mentors.debian.net marked the watch file as not working, but it seems fine if I run uscan. Thanks, Kienan
Bug#793057: ITP: godot -- open source MIT licensed game engine
I've uploaded an updated package to mentors.debian.net. I think it's ready for more review/testing. I'm also looking for a sponsor if anyone is willing. Thanks, Kienan signature.asc Description: PGP signature
Bug#793057: ITP: godot -- open source MIT licensed game engine
Hi, I've had a bit of free time to work on this and I've uploaded another version (based on 2.1.4) to mentors.debian.net : https://mentors.debian.net/package/godot Thank both Francesco and Rémi for your advice in preceeding comments! I've made a number of changes, including having 3 packages as suggested by Rémi. There are still a couple of small warnings to clear up, in particular I'd like to tackle the debug symbols warning and get the build to use the hardening flags next. I also haven't cherry-picked the desktop/appdata files from upstream yet. All the changes I made are also available here: https://github.com/kienanstewart/godot/tree/2.1.4-stable-debian Thanks, Kienan signature.asc Description: PGP signature
Bug#793057: ITP: godot -- open source MIT licensed game engine
I've had a first pass at creating a package for godot : https://mentors.debian.net/package/godot There are some lintian warnings to clear up, and I was wondering a bit about the following * builds only support amd64 at the moment * how to handle packaging godot 3.0 when it's available (an alpha is currently out) Once I find some time to clear up the lintian warnings, I'll do the RFS procedure following the mentor's guide and https://wiki.debian.org/Games/Sponsors/Queue signature.asc Description: PGP signature
Bug#793057: ITP: godot -- open source MIT licensed game engine
I'm also interested in helping to package godot for debian. With the current stable of godot (2.1.3-stable), there's an incompatibility with the SSL version shipped in stretch (upstream issue: https://github.com/godotengine/godot/issues/8624) I was able to build with: scons platform=x11 target=release_debug bits=64 use_llvm=yes builtin_openssl=yes but I'm not sure if this will cause problems Thanks, Kienan signature.asc Description: PGP signature
Bug#859539: filezilla: Filezilla crashes at startup
Hi, I was unable to reproduce this bug on a clean install (QEMU VM), or on my laptop which had been upgraded from Jessie to Stretch some time ago. I followed the test proposed by John earlier. Perhaps there are some details in the config file or the bookmark path that may be pertinent to provoking this bug? What is the "Language Code" setting in filezilla.xml? filezilla: Installed: 3.24.0-1 Thanks, Kienan signature.asc Description: PGP signature
Bug#860337: Acknowledgement (php7.0: No transition path from php5 to php7.0 when upgrading to stretch)
Control: user debian-rele...@lists.debian.org Control: usertags -1 bsp-2017-04-ca-montreal signature.asc Description: PGP signature
