[Bug 1594316] Re: HTTP response we received was '302 Found' when using "puppet module install"
This bug report can be rejected, the redirect has been removed on the server side so the existing code and clients using API v1 work again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1594316 Title: HTTP response we received was '302 Found' when using "puppet module install" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1594316/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1594316] Re: HTTP response we received was '302 Found' when using "puppet module install"
Yes, I think it only affects Trusty. I think it's unlikely that upstream will provide a patch as upstream since 3.6.0 has moved to a newer API version that isn't affected by this issue. It does look likely from the FORGE-327 ticket above that the server behaviour will be changed for this older API version - if so, I'll update here so this ticket can be closed if it's resolved that way. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1594316 Title: HTTP response we received was '302 Found' when using "puppet module install" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1594316/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1594316] Re: HTTP response we received was '302 Found' when using "puppet module install"
** Summary changed: - HTTP response we received was '404 Not Found' when using "puppet module install" + HTTP response we received was '302 Found' when using "puppet module install" -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1594316 Title: HTTP response we received was '302 Found' when using "puppet module install" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1594316/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1594316] Re: HTTP response we received was '404 Not Found' when using "puppet module install"
I've also filed a ticket with Puppet to see if the server behaviour can be changed for the old API: https://tickets.puppetlabs.com/browse/FORGE-327 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1594316 Title: HTTP response we received was '404 Not Found' when using "puppet module install" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1594316/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1594316] [NEW] HTTP response we received was '404 Not Found' when using "puppet module install"
Public bug reported: The "puppet module" command is now throwing errors when installing modules from the Puppet Forge (https://forge.puppet.com), as it redirects from puppetlabs.com to puppet.com. # puppet module install puppetlabs/ntp Notice: Preparing to install into /etc/puppet/modules ... Notice: Downloading from https://forge.puppetlabs.com ... Error: Could not execute operation for 'puppetlabs/ntp' The server being queried was https://forge.puppetlabs.com The HTTP response we received was '302 Found' Check the author and module names are correct. The command should install and unpack the module to /etc/puppet/modules/ntp, but instead fails. As a workaround you can add "--module_repository https://forge.puppet.com/; to the command. This affects Puppet 3.4.3 on Ubuntu 14.04 (trusty), and any version prior to 3.6.0 which uses the v1 API. Newer versions use the v3 API on forgeapi.puppetlabs.com instead and are unaffected. The package should probably be patched to change module_repository to forge.puppet.com in lib/puppet/defaults.rb, or to use the v3 API (https://tickets.puppetlabs.com/browse/PUP-2093 and probably others). # lsb_release -rd Description:Ubuntu 14.04 LTS Release:14.04 # apt-cache policy puppet puppet: Installed: 3.4.3-1ubuntu1.1 Candidate: 3.4.3-1ubuntu1.1 Version table: *** 3.4.3-1ubuntu1.1 0 500 http://archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.4.3-1 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: puppet 3.4.3-1ubuntu1.1 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 Date: Mon Jun 20 10:19:25 2016 PackageArchitecture: all ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: puppet UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: puppet (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty uec-images -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1594316 Title: HTTP response we received was '404 Not Found' when using "puppet module install" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1594316/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1491406] Re: augeas-lenses-1.2.0 - NagiosCfg lens broken for /etc/nagios.cfg due to spaces
Ryan, changing an existing value will preserve the whitespace (something Augeas tries hard to do), so you'll probably need to add a new setting to observe the behaviour. You could delete the existing cfg_file entry and create a new one, e.g. augtool> rm /files/etc/nagios3/nagios.cfg/cfg_file augtool> set /files/etc/nagios3/nagios.cfg/cfg_file /etc/nagios3/commands.cfg.local or if Nagios supports any setting name then you could define something new: augtool> set /files/etc/nagios3/nagios.cfg/example test -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1491406 Title: augeas-lenses-1.2.0 - NagiosCfg lens broken for /etc/nagios.cfg due to spaces To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/augeas/+bug/1491406/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1580731] Re: augeas-lenses filter for PHP files doesn't match php7.0-* files
I'd suggest just adding these two entries to the includes list: /etc/php/*/*/*.ini /etc/php/*/fpm/pool.d/*.conf Unless there are other incompatible INI files that might be matched? I'm not familiar with the PHP packages to be sure. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1580731 Title: augeas-lenses filter for PHP files doesn't match php7.0-* files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/augeas/+bug/1580731/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1570472] Re: Set systemd as default service provider
I've tested the diff in #4 on Ubuntu 16.04, with puppet-common 3.8.5-2, it seems to fix the issue correctly. Prior to the patch, Puppet would try and manage services using upstart: /Stage[main]/Tftp::Service/Service[tftpd-hpa]: Could not evaluate: Execution of '/sbin/status tftpd-hpa' returned 1: status: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1570472 Title: Set systemd as default service provider To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1570472/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1510318] Re: Augeas 1.3 can't read some conf files
I'm attaching the trio of commits to fix the bug in a single patch, rebased on top of the upstream 1.3.0 release. Hopefully somebody can use this as the basis of a patch against the package itself. Locally it seems to resolve parsing of the ssl.conf file at https://github.com/letsencrypt/letsencrypt/issues/981#issuecomment-148485384. ** Patch added: "Patch against upstream release-1.3.0" https://bugs.launchpad.net/ubuntu/+source/augeas/+bug/1510318/+attachment/4506538/+files/0001-Httpd-Do-not-pass-empty-as-body-to-section.patch -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1510318 Title: Augeas 1.3 can't read some conf files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/augeas/+bug/1510318/+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
[Bug 1510318] Re: Augeas 1.3 can't read some conf files
I'm attaching the trio of commits to fix the bug in a single patch, rebased on top of the upstream 1.3.0 release. Hopefully somebody can use this as the basis of a patch against the package itself. Locally it seems to resolve parsing of the ssl.conf file at https://github.com/letsencrypt/letsencrypt/issues/981#issuecomment-148485384. ** Patch added: "Patch against upstream release-1.3.0" https://bugs.launchpad.net/ubuntu/+source/augeas/+bug/1510318/+attachment/4506538/+files/0001-Httpd-Do-not-pass-empty-as-body-to-section.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1510318 Title: Augeas 1.3 can't read some conf files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/augeas/+bug/1510318/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1510318] Re: Augeas 1.3 can't read some conf files
With regards to manual regression testing for a stable update, I'd suggest running "augtool print /files/etc/apache2" (with Apache, mod_ssl and optionally, other Apache modules installed) to check if any files that used to parse now fail in any way. Hopefully the number of errors will be reduced. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1510318 Title: Augeas 1.3 can't read some conf files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/augeas/+bug/1510318/+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
[Bug 1510318] Re: Augeas 1.3 can't read some conf files
With regards to manual regression testing for a stable update, I'd suggest running "augtool print /files/etc/apache2" (with Apache, mod_ssl and optionally, other Apache modules installed) to check if any files that used to parse now fail in any way. Hopefully the number of errors will be reduced. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1510318 Title: Augeas 1.3 can't read some conf files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/augeas/+bug/1510318/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1267385] [NEW] Default file mode now 0600 instead of 0644 (regression in CVE-2013-4969 fix)
Public bug reported:
The fix for CVE-2013-4969 (tempfile vulnerability) contained a
regression affecting the default file mode if none is specified on a
file resource. This has been fixed in upstream 3.4.2 and 2.7.25.
Upstream bug: https://tickets.puppetlabs.com/browse/PUP-1255
Please apply the following patch from 2.7.x to fix the issue:
https://github.com/puppetlabs/puppet/commit/6a11abb8ac
This currently affects the Foreman installer as some resources in our
modules rely on this behaviour.
Reproduced on Ubuntu 12.04 with puppet 2.7.11-1ubuntu2.6:
# puppet apply -e 'file { /tmp/a: content = foo }'
notice: /Stage[main]//File[/tmp/a]/ensure: defined content as
'{md5}acbd18db4cc2f85cedef654fccc4a4d8'
notice: Finished catalog run in 0.08 seconds
# ls -l /tmp/a
-rw--- 1 root root 3 Jan 9 09:13 /tmp/a
||/ Name Version Description
+++---
ii puppet 2.7.11-1ubuntu2.6Centralized configuration
management - agent startup and
** Affects: puppet (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to puppet in Ubuntu.
https://bugs.launchpad.net/bugs/1267385
Title:
Default file mode now 0600 instead of 0644 (regression in
CVE-2013-4969 fix)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1267385/+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
[Bug 1267385] [NEW] Default file mode now 0600 instead of 0644 (regression in CVE-2013-4969 fix)
Public bug reported:
The fix for CVE-2013-4969 (tempfile vulnerability) contained a
regression affecting the default file mode if none is specified on a
file resource. This has been fixed in upstream 3.4.2 and 2.7.25.
Upstream bug: https://tickets.puppetlabs.com/browse/PUP-1255
Please apply the following patch from 2.7.x to fix the issue:
https://github.com/puppetlabs/puppet/commit/6a11abb8ac
This currently affects the Foreman installer as some resources in our
modules rely on this behaviour.
Reproduced on Ubuntu 12.04 with puppet 2.7.11-1ubuntu2.6:
# puppet apply -e 'file { /tmp/a: content = foo }'
notice: /Stage[main]//File[/tmp/a]/ensure: defined content as
'{md5}acbd18db4cc2f85cedef654fccc4a4d8'
notice: Finished catalog run in 0.08 seconds
# ls -l /tmp/a
-rw--- 1 root root 3 Jan 9 09:13 /tmp/a
||/ Name Version Description
+++---
ii puppet 2.7.11-1ubuntu2.6Centralized configuration
management - agent startup and
** Affects: puppet (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1267385
Title:
Default file mode now 0600 instead of 0644 (regression in
CVE-2013-4969 fix)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1267385/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1054306] Re: ncftool list fails
On 24/09/12 18:14, Serge Hallyn wrote: result of 'grep -i fail' over the output: FAIL: lens-modules.sh FAIL: lens-modules_conf.sh Thanks for finding this, I really should have run a full test after making the change. Sorry for that. There were these two other module lenses that were using bits of the modprobe lens, so my name change broke it. Attached is a followup patch committed as c0ff479 which repairs the damage caused. -- Dominic Cleal domi...@computerkb.co.uk ** Patch added: 1054306-modprobe-wrap-c0ff479.patch https://bugs.launchpad.net/bugs/1054306/+attachment/3339679/+files/1054306-modprobe-wrap-c0ff479.patch -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to augeas in Ubuntu. https://bugs.launchpad.net/bugs/1054306 Title: ncftool list fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/augeas/+bug/1054306/+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
Re: [Bug 1054306] Re: ncftool list fails
On 24/09/12 18:14, Serge Hallyn wrote: result of 'grep -i fail' over the output: FAIL: lens-modules.sh FAIL: lens-modules_conf.sh Thanks for finding this, I really should have run a full test after making the change. Sorry for that. There were these two other module lenses that were using bits of the modprobe lens, so my name change broke it. Attached is a followup patch committed as c0ff479 which repairs the damage caused. -- Dominic Cleal domi...@computerkb.co.uk ** Patch added: 1054306-modprobe-wrap-c0ff479.patch https://bugs.launchpad.net/bugs/1054306/+attachment/3339679/+files/1054306-modprobe-wrap-c0ff479.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1054306 Title: ncftool list fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/augeas/+bug/1054306/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1054306] Re: ncftool list fails
Could you share the contents of /etc/modprobe.d/iwlwifi.conf ? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to netcf in Ubuntu. https://bugs.launchpad.net/bugs/1054306 Title: ncftool list fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/augeas/+bug/1054306/+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
Re: [Bug 1054306] Re: ncftool list fails
On 21/09/12 21:51, Serge Hallyn wrote: @Dominic they are pasted into comment #3. Apologies, I hadn't refreshed. I was able to reproduce this in debian sid with that same file, so have filed a debian bug (waiting for a reply with the bug#) I've fixed this upstream in commit e599fed9, patch attached if you want to apply it. http://git.fedorahosted.org/cgit/augeas.git/commit/?id=e599fed9 Regards, -- Dominic Cleal domi...@computerkb.co.uk ** Patch added: 1054306-modprobe-wrap.patch https://bugs.launchpad.net/bugs/1054306/+attachment/3329888/+files/1054306-modprobe-wrap.patch -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to netcf in Ubuntu. https://bugs.launchpad.net/bugs/1054306 Title: ncftool list fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/augeas/+bug/1054306/+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
[Bug 1054306] Re: ncftool list fails
Could you share the contents of /etc/modprobe.d/iwlwifi.conf ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1054306 Title: ncftool list fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/augeas/+bug/1054306/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1054306] Re: ncftool list fails
On 21/09/12 21:51, Serge Hallyn wrote: @Dominic they are pasted into comment #3. Apologies, I hadn't refreshed. I was able to reproduce this in debian sid with that same file, so have filed a debian bug (waiting for a reply with the bug#) I've fixed this upstream in commit e599fed9, patch attached if you want to apply it. http://git.fedorahosted.org/cgit/augeas.git/commit/?id=e599fed9 Regards, -- Dominic Cleal domi...@computerkb.co.uk ** Patch added: 1054306-modprobe-wrap.patch https://bugs.launchpad.net/bugs/1054306/+attachment/3329888/+files/1054306-modprobe-wrap.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1054306 Title: ncftool list fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/augeas/+bug/1054306/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 283469] Re: Icon problems after switching to cystal svg iconset
Confirmed in my upgrade from 8.04 to 8.10 final and also back in 8.04 when installing KDE4 packages. -- Icon problems after switching to cystal svg iconset https://bugs.launchpad.net/bugs/283469 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
