New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 621151 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Last visit > 30 days ago
Closed: Jun 2016
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

puppet failed to config rpc-logserver

Project Member Reported by shuqianz@chromium.org, Jun 17 2016

Issue description

Notice: /Stage[main]/Lab::Autotest_common/Exec[reload-ipv6-privacy-conf]: Triggered 'refresh' from 1 events
Debug: /Stage[main]/Lab::Autotest_common/Exec[reload-ipv6-privacy-conf]: The container Class[Lab::Autotest_common] will propagate my refresh event
Error: /Stage[main]/Lab::Autotest_apache/File[/etc/init/rpc-logserver.conf]: Could not evaluate: Could not retrieve information from environment goobuntu_stable source(s) puppet:///modules/lab/autotest_master/rpc-logserver.conf
Debug: Exec[preconfigure_mysql](provider=shell): Executing '["/bin/sh", "-c", "echo 'mysql-server-5.5 mysql-server/root_password password autotest' | sudo debconf-set-selections\n                echo 'mysql-server-5.5 mysql-server/root_password_again password autotest' | sudo debconf-set-selections\n                "]'
Debug: Executing '/bin/sh -c echo 'mysql-server-5.5 mysql-server/root_password password autotest' | sudo debconf-set-selections
                echo 'mysql-server-5.5 mysql-server/root_password_again password autotest' | sudo debconf-set-selections
                '

 
Summary: puppet failed to config rpc-logserver (was: puppet failed to config rpc-logservre)
Another error found:

Notice: /Stage[main]/Lab::Autotest_common/File[/usr/local/autotest/creds/gmail_api_credentials_crosinfra2.dat]/ensure: defined content as '{md5}ae76e676d97175cc6d7c5d8c4415a22d'
Debug: /Stage[main]/Lab::Autotest_common/File[/usr/local/autotest/creds/gmail_api_credentials_crosinfra2.dat]: The container Class[Lab::Autotest_common] will propagate my refresh event
Error: Cannot create /usr/local/autotest/creds/chrome-infra/service_accounts; parent directory /usr/local/autotest/creds/chrome-infra does not exist
Error: /Stage[main]/Lab::Autotest_common/File[/usr/local/autotest/creds/chrome-infra/service_accounts]/ensure: change from absent to directory failed: Cannot create /usr/local/autotest/creds/chrome-infra/service_accounts; parent directory /usr/local/autotest/creds/chrome-infra does not exist
Debug: /Stage[main]/Lab::Autotest_common/File[/usr/local/autotest/creds/chrome-infra/service_accounts]: Nothing to manage: no ensure and the resource doesn't exist
Notice: /Stage[main]/Lab::Autotest_common/File[/usr/local/autotest/creds/chrome-infra/service_accounts/service_account_chromeos.json]: Dependency File[/usr/local/autotest/creds/chrome-infra/service_accounts] has failures: true
Warning: /Stage[main]/Lab::Autotest_common/File[/usr/local/autotest/creds/chrome-infra/service_accounts/service_account_chromeos.json]: Skipping because of failed dependencies

Project Member

Comment 3 by bugdroid1@chromium.org, Jun 17 2016

The following revision refers to this bug:
  https://chrome-internal.googlesource.com/chromeos/chromeos-admin/+/ba720918585863e2ab2ca26b51891d3deaf7e95f

commit ba720918585863e2ab2ca26b51891d3deaf7e95f
Author: Shuqian Zhao <shuqianz@chromium.org>
Date: Fri Jun 17 20:39:21 2016

Status: Fixed (was: Assigned)

Sign in to add a comment