Issue #11863 has been updated by Justin Stoller.
Hello Michael, I've filed a ticket for a feature request against the uninstaller noting your ticket as a use case for the uninstaller removing mysql with the `-pd` options. You can track that progress at ticket #11869. If you do have a pre-existing database there are additional questions that need to be answered and we've also been working on improving that workflow (see ticket #6038) The value in your answer file for using an existing db is: `q_puppet_enterpriseconsole_database_install=n` which will then require addition answers. I believe they are fairly well documented in the PE 2.0 answer file reference here: `http://docs.puppetlabs.com/pe/2.0/install_answer_file_reference.html` We'd appreciate any debugging information you have as to why the `-l` option seems to allow your install to work. I'll discuss it with the installer dev later today. If you have any further issues with Puppet Enterprise, the Open Source Puppet ticket area isn't the best place to bring them up. You can discuss them on the Puppet Enterprise ticket queue: `https://projects.puppetlabs.com/projects/puppet-enterprise` PE Users mailing list: `https://groups.google.com/a/puppetlabs.com/group/pe-users/topics` or if you've paid for support: `https://support.puppetlabs.com` Thank you for your feedback, Justin ---------------------------------------- Bug #11863: Errors when the PE 2.0 installer is run a second time https://projects.puppetlabs.com/issues/11863 Author: Michael Jang Status: Unreviewed Priority: Normal Assignee: Category: Target version: Affected Puppet version: Keywords: Branch: I've tried the uninstaller on two RHEL 6 systems. When I've run the installer again, responding "Y" to the question on whether to also install MySQL, I got varying results -- a fatal error on one system, a non-fatal error on a second system. My assumption is that people who try PE on a "home" lab will start with a Puppet master/cloud provisioner, and also install MySQL on a test system. It's when they also install MySQL for the first time with the PE installer when they may encounter this problem. I note that the uninstaller does not remove MySQL (even in complete uninstall mode with the -d -p switches). With that in mind, an attempt to use the puppet-enterprise-installer script a second time with the same answers leads to non-fatal errors, based on a now existing MySQL server. On one system, I got two errors that were effectively "info" level, as the installation proceeded to completion. ERROR 1007 (HY000) at line 2: Can't create database 'console'; database exists ERROR 1007 (HY000) at line 2: Can't create database 'console_inventory_service'; database exists) On a second system, the PE packages were installed, with the following messages: mysqladmin: connect to server at 'localhost' failed error: 'Access denied for user 'root'@'localhost' (using password: NO)' !! ERROR: Existing MySQL server found; can't reset its password. ERROR 1045 (28000): Access denied for user 'root'@'localhost' (using password: YES) which led to the following fatal error: !! ERROR: Cancelling installation Odd solution: the fatal error does not happen when "-l logfile" is added to the puppet-enterprise-installer script; the installation proceeds to completion. I'd add the log file, but it's as if the action overrides the attempt to reinstall the MySQL server. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
