[Bug 551544] Re: puppet in lucid does not support upstart status
Hi Lorello, In the puppet source code at github you can see how the status is checked via upstart: https://github.com/puppetlabs/puppet/blob/master/lib/puppet/provider/service/upstart.rb The is a search for 'start' on the status output. So if ssh is running and status ssh gives the following output 'ssh start/running, process x' then puppet should know the service is running. Also you can check https://projects.puppetlabs.com/issues/12773 since it has some more information on this as well. How exactly can we reproduce your problem? -- 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/551544 Title: puppet in lucid does not support upstart status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/551544/+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 987207] [NEW] Puppetmaster-passenger will not start after reinstalling due to libapache2-mod-passenger
Public bug reported: As requested by Micah Gersten: When purging and installing puppetmaster-passenger again it wont start. This is somehow due to a2enmod passenger which is not executed properly. The output of the second install is attached as logfile since thats where this bug shows up. Howto reproduce on fresh ubuntu precise machine: 1: aptitude install puppetmaster-passenger 2: aptitude purge puppetmaster-passenger 3: aptitude install puppetmaster-passenger. First install: apache2 is installed togheter with libapache2-mod-passenger. The install script of libapache2-mod-passenger will make sure a2enmod passenger is executed. First purge: libapache2-mod-passenger gets removed, and mod-passenger is disabled (apache2 is not removed though) Second install: libapache2-mod-passenger is installed again, but not enabled. The workaround to properly reinstall without running into problems is to completely remove puppetmaster-passenger and libapache2-mod-passenger: 1: aptitude install puppetmaster-passenger 2: aptitude purge puppetmaster-passenger 3: aptitude purge libapache2-mod-passenger 4: aptitude install puppetmaster-passenger As far as I can see the problem is that when puppetmaster-passenger is purged the dependency libapache2-mod-passenger doesnt get properly removed. The next time puppetmaster-passenger is installed the dependency mod-passenger wont get enabled. Im not sure if this is a bug in the dependency control, or a bug in the install/remove scripts from libapache2-mod-passenger. ** 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/987207 Title: Puppetmaster-passenger will not start after reinstalling due to libapache2-mod-passenger To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/987207/+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 987207] Re: Puppetmaster-passenger will not start after reinstalling due to libapache2-mod-passenger
** Attachment added: installprecise2.txt https://bugs.launchpad.net/bugs/987207/+attachment/3099784/+files/installprecise2.txt -- 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/987207 Title: Puppetmaster-passenger will not start after reinstalling due to libapache2-mod-passenger To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/987207/+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 954368] Re: Upstart script puppet agent
Hi James, Thanks for your feedback! 1) The upstart script has been extended with daemon checks, checks on the defaults file flags and also give error outputs. I added the puppet.conf upstart script as attachment. 2) Since mongrel support will be deleted from debian (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=663921) im assuming that ubuntu 12.10 wont have mongrel support either. This would mean that the puppetmaster upstart script wont need to support the mongrel backend and only standard webrick. See attachment puppetmaster.conf 3) Also added the puppetqd upstart script as attachment in puppetqd.conf. 4) It would be nice to have an upstart script for puppetmaster-passenger too. But i think this would be the apache2 upstart script. Is there any eta on the apache2 upstart script, or if someone is working on that already? ** Bug watch added: Debian Bug tracker #663921 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=663921 ** Attachment added: puppet.conf https://bugs.launchpad.net/ubuntu/q-series/+source/puppet/+bug/954368/+attachment/2909098/+files/puppet.conf -- 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/954368 Title: Upstart script puppet agent To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/954368/+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 954368] Re: Upstart script puppet agent
** Attachment added: puppetqd.conf https://bugs.launchpad.net/ubuntu/q-series/+source/puppet/+bug/954368/+attachment/2909100/+files/puppetqd.conf -- 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/954368 Title: Upstart script puppet agent To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/954368/+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 954368] Re: Upstart script puppet agent
** Attachment added: puppetmaster.conf https://bugs.launchpad.net/ubuntu/q-series/+source/puppet/+bug/954368/+attachment/2909099/+files/puppetmaster.conf -- 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/954368 Title: Upstart script puppet agent To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/954368/+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 954368] [NEW] Upstart script puppet agent
Public bug reported: Upstart script for the puppet agent. See attachment for debdiff. ** Affects: puppet (Ubuntu) Importance: Undecided Status: New ** Tags: agent puppet upstart -- 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/954368 Title: Upstart script puppet agent To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/954368/+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 954368] Re: Upstart script puppet agent
** Patch added: debdiff for puppet https://bugs.launchpad.net/bugs/954368/+attachment/2865153/+files/puppet_2.7.11-1ubuntu3.debdiff -- 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/954368 Title: Upstart script puppet agent To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/954368/+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 948909] Re: puppetmaster-passenger does not install cleanly from scrach
This is fixed in bug 948983 ** Changed in: puppet (Ubuntu) Status: Confirmed = Fix Committed -- 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/948909 Title: puppetmaster-passenger does not install cleanly from scrach To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/948909/+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 948983] Re: puppetmaster-passenger default vhost has wrong documentroot
1: Correct, if /etc/puppet/puppet.conf has no [main] section with ssldir set (to /var/lib/puppet/ssl) the puppetmaster-passenger package install will use its default /etc/puppet/ssl path for the SSL variables in the /etc/apache2/sites-available/puppetmaster vhost and the generated certificate files. -- 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/948983 Title: puppetmaster-passenger default vhost has wrong documentroot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/948983/+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 948983] Re: puppetmaster-passenger default vhost has wrong documentroot
James, check bug 948909 which i posted yesterday. Its about the a2enmod headers -- 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/948983 Title: puppetmaster-passenger default vhost has wrong documentroot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/948983/+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 950183] [NEW] puppetmaster-passenger postinst creates wrong certificate files and puppetmaster vhost if puppet config print has an error
Public bug reported:
How to reproduce:
echo abc /etc/puppet/puppet.conf
root@host:~# puppet config print
err: Could not parse /etc/puppet/puppet.conf: Could not match line abc at
/etc/puppet/puppet.conf:abc
root@host:~# aptitude install puppetmaster-passenger
The following NEW packages will be installed:
puppetmaster-common{a} puppetmaster-passenger
0 packages upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/27.9 kB of archives. After unpacking 635 kB will be used.
Do you want to continue? [Y/n/?] y
Selecting previously unselected package puppetmaster-common.
(Reading database ... 25302 files and directories currently installed.)
Unpacking puppetmaster-common (from .../puppetmaster-common_2.7.11-1_all.deb)
...
Selecting previously unselected package puppetmaster-passenger.
Unpacking puppetmaster-passenger (from
.../puppetmaster-passenger_2.7.11-1_all.deb) ...
Processing triggers for man-db ...
Processing triggers for ureadahead ...
Setting up puppetmaster-common (2.7.11-1) ...
* Starting puppet queue
[ OK ]
Setting up puppetmaster-passenger (2.7.11-1) ...
err: Could not parse /etc/puppet/puppet.conf: Could not match line abc at
/etc/puppet/puppet.conf:abc
notice: err: has a waiting certificate request
notice: Signed certificate request for err:
notice: Removing file Puppet::SSL::CertificateRequest err: at
'/etc/puppet/ssl/ca/requests/err:.pem'
notice: Removing file Puppet::SSL::CertificateRequest err: at
'/etc/puppet/ssl/certificate_requests/err:.pem'
notice: could has a waiting certificate request
notice: Signed certificate request for could
notice: Removing file Puppet::SSL::CertificateRequest could at
'/etc/puppet/ssl/ca/requests/could.pem'
notice: Removing file Puppet::SSL::CertificateRequest could at
'/etc/puppet/ssl/certificate_requests/could.pem'
notice: not has a waiting certificate request
notice: Signed certificate request for not
notice: Removing file Puppet::SSL::CertificateRequest not at
'/etc/puppet/ssl/ca/requests/not.pem'
notice: Removing file Puppet::SSL::CertificateRequest not at
'/etc/puppet/ssl/certificate_requests/not.pem'
notice: parse has a waiting certificate request
notice: Signed certificate request for parse
notice: Removing file Puppet::SSL::CertificateRequest parse at
'/etc/puppet/ssl/ca/requests/parse.pem'
notice: Removing file Puppet::SSL::CertificateRequest parse at
'/etc/puppet/ssl/certificate_requests/parse.pem'
crit: directory traversal detected in Puppet::SSL::Certificate::File:
/etc/puppet/puppet.conf:
err: Cached certificate for /etc/puppet/puppet.conf: failed: invalid key
crit: directory traversal detected in Puppet::SSL::Certificate::Ca:
/etc/puppet/puppet.conf:
err: Could not call generate: invalid key
Module ssl already enabled
Enabling site puppetmaster.
To activate the new configuration, you need to run:
service apache2 reload
Syntax error on line 18 of /etc/apache2/sites-enabled/puppetmaster:
SSLCertificateFile: file '/etc/puppet/ssl/certs/squigley.namespace.at.pem' does
not exist or is empty
Action 'configtest' failed.
The Apache error log may have more information.
...fail!
invoke-rc.d: initscript apache2, action restart failed.
dpkg: error processing puppetmaster-passenger (--configure):
subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
puppetmaster-passenger
E: Sub-process /usr/bin/dpkg returned an error code (1)
A package failed to install. Trying to recover:
Setting up puppetmaster-passenger (2.7.11-1) ...
err: Could not parse /etc/puppet/puppet.conf: Could not match line abc at
/etc/puppet/puppet.conf:abc
err: Could not call generate: A Certificate already exists for err:
Module ssl already enabled
Site puppetmaster already enabled
Syntax error on line 18 of /etc/apache2/sites-enabled/puppetmaster:
SSLCertificateFile: file '/etc/puppet/ssl/certs/squigley.namespace.at.pem' does
not exist or is empty
Action 'configtest' failed.
The Apache error log may have more information.
...fail!
invoke-rc.d: initscript apache2, action restart failed.
dpkg: error processing puppetmaster-passenger (--configure):
subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
puppetmaster-passenger
** 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/950183
Title:
puppetmaster-passenger postinst creates wrong certificate files and
puppetmaster vhost if puppet config print has an error
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/950183/+subscriptions
--
[Bug 950183] Re: puppetmaster-passenger postinst creates wrong certificate files and puppetmaster vhost if puppet config print has an error
Adem, I can confirm that if it returns 0 on failure, which is really bad behaviour. Its really sad that such simple things can cause so much trouble. For now the fastest fix is to see if err: is returned by puppet config print in the postinst before even doing anything and if so the postinst should exit the install, roll back any changes and give a message that puppet.conf should be fixed first before reinstalling. -- 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/950183 Title: puppetmaster-passenger postinst creates wrong certificate files and puppetmaster vhost if puppet config print has an error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/950183/+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 950183] Re: puppetmaster-passenger postinst creates wrong certificate files and puppetmaster vhost if puppet config print has an error
Ok, I think the puppet config print variable should be changed to puppet --configprint variable: # puppet config print abc; echo $? err: Could not parse /etc/puppet/puppet.conf: Could not match line abc at /etc/puppet/puppet.conf:bla invalid parameter: abc 0 # puppet --configprint abc; echo $? invalid parameter: abc 1 # puppet config print certname; echo $? err: Could not parse /etc/puppet/puppet.conf: Could not match line abc at /etc/puppet/puppet.conf:bla host.example.com 0 # puppet --configprint certname; echo $? host.example.com 0 -- 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/950183 Title: puppetmaster-passenger postinst creates wrong certificate files and puppetmaster vhost if puppet config print has an error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/950183/+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 950183] Re: puppetmaster-passenger postinst creates wrong certificate files and puppetmaster vhost if puppet config print has an error
Yeah, that does the trick. Replace puppet config print in the postinst with puppet --configprint and this bug can be resolved: root@host:/etc# dpkg -i puppetmaster-passenger_2.7.11-1_all.deb Selecting previously unselected package puppetmaster-passenger. (Reading database ... 25803 files and directories currently installed.) Unpacking puppetmaster-passenger (from puppetmaster-passenger_2.7.11-1_all.deb) ... Setting up puppetmaster-passenger (2.7.11-1) ... err: Could not parse /etc/puppet/puppet.conf: Could not match line bla at /etc/puppet/puppet.conf:bla notice: Signed certificate request for ca notice: Rebuilding inventory file notice: host.example.com has a waiting certificate request notice: Signed certificate request for host.example.com notice: Removing file Puppet::SSL::CertificateRequest host.example.com at '/etc/puppet/ssl/ca/requests/host.example.com.pem' notice: Removing file Puppet::SSL::CertificateRequest host.example.com at '/etc/puppet/ssl/certificate_requests/host.example.com.pem' Module ssl already enabled Enabling site puppetmaster. To activate the new configuration, you need to run: service apache2 reload * Restarting web server apache2 ... waiting Maybe someone else knows why the error is still in the output though? -- 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/950183 Title: puppetmaster-passenger postinst creates wrong certificate files and puppetmaster vhost if puppet config print has an error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/950183/+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 948909] [NEW] puppetmaster-passenger does not install cleanly from scrach
Public bug reported: When installing puppetmaster-passenger the install will not finish without errors. After doing some research the problem is because apache2 mod_headers is not enabled. Output from install: To activate the new configuration, you need to run: service apache2 reload Syntax error on line 29 of /etc/apache2/sites-enabled/puppetmaster: Invalid command 'RequestHeader', perhaps misspelled or defined by a module not included in the server configuration Action 'configtest' failed. The Apache error log may have more information. ...fail! invoke-rc.d: initscript apache2, action restart failed. dpkg: error processing puppetmaster-passenger (--configure): subprocess installed post-installation script returned error exit status 1 Setting up ruby1.8-dev (1.8.7.352-2ubuntu1) ... Setting up ssl-cert (1.0.28) ... Setting up libstdc++6-4.6-dev (4.6.3-1ubuntu2) ... Setting up g++-4.6 (4.6.3-1ubuntu2) ... Setting up g++ (4:4.6.2-4ubuntu1) ... update-alternatives: using /usr/bin/g++ to provide /usr/bin/c++ (c++) in auto mode. Setting up build-essential (11.5ubuntu2) ... Processing triggers for libc-bin ... ldconfig deferred processing now taking place Errors were encountered while processing: puppetmaster-passenger E: Sub-process /usr/bin/dpkg returned an error code (1) A package failed to install. Trying to recover: Setting up puppetmaster-passenger (2.7.11-1) ... Module ssl already enabled Site puppetmaster already enabled Syntax error on line 29 of /etc/apache2/sites-enabled/puppetmaster: Invalid command 'RequestHeader', perhaps misspelled or defined by a module not included in the server configuration Action 'configtest' failed. The Apache error log may have more information. ...fail! invoke-rc.d: initscript apache2, action restart failed. dpkg: error processing puppetmaster-passenger (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: puppetmaster-passenger The fix: a2enmod headers /etc/init.d/apache2 restart It seems that only the SSL module is enabled through this install, but it needs mod_headers too in order to run ** 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/948909 Title: puppetmaster-passenger does not install cleanly from scrach To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/948909/+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 948983] [NEW] puppetmaster-passenger default vhost has wrong documentroot
Public bug reported:
After a clean install of puppetmaster-passenger on 12.04 the vhost
/etc/apache2/sites-available/puppetmaster is wrong:
1: SSL certificates for puppetmaster on ubuntu are not in /etc/puppet/ssl but
in /var/lib/puppet/ssl
2: Rack application for puppetmaster on ubuntu is not in /etc/puppet but in
/usr share/puppet
This config which works for me (PLEASE NOTE: $FQDN should be actual fqdn of the
server)
# you probably want to tune these settings
PassengerHighPerformance on
PassengerMaxPoolSize 12
PassengerPoolIdleTime 1500
# PassengerMaxRequests 1000
PassengerStatThrottleRate 120
RackAutoDetect Off
RailsAutoDetect Off
Listen 8140
VirtualHost *:8140
SSLEngine on
SSLProtocol -ALL +SSLv3 +TLSv1
SSLCipherSuite ALL:!ADH:RC4+RSA:+HIGH:+MEDIUM:-LOW:-SSLv2:-EXP
SSLCertificateFile /var/lib/puppet/ssl/certs/$FQDN.pem
SSLCertificateKeyFile /var/lib/puppet/ssl/private_keys/$FQDN.pem
SSLCertificateChainFile /var/lib/puppet/ssl/certs/ca.pem
SSLCACertificateFile/var/lib/puppet/ssl/certs/ca.pem
# If Apache complains about invalid signatures on the CRL, you can try
disabling
# CRL checking by commenting the next line, but this is not recommended.
SSLCARevocationFile /var/lib/puppet/ssl/ca/ca_crl.pem
SSLVerifyClient optional
SSLVerifyDepth 1
SSLOptions +StdEnvVars
RequestHeader set X-SSL-Subject %{SSL_CLIENT_S_DN}e
RequestHeader set X-Client-DN %{SSL_CLIENT_S_DN}e
RequestHeader set X-Client-Verify %{SSL_CLIENT_VERIFY}e
DocumentRoot /usr/share/puppet/rack/puppetmasterd/public/
RackBaseURI /
Directory /usr/share/puppet/rack/puppetmasterd/
Options None
AllowOverride None
Order allow,deny
allow from all
/Directory
/VirtualHost
** 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/948983
Title:
puppetmaster-passenger default vhost has wrong documentroot
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/948983/+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
