You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Hadoop QA (JIRA)" <ji...@apache.org> on 2016/07/04 20:02:10 UTC

[jira] [Commented] (AMBARI-17554) ambari-server update-host-name failing

    [ https://issues.apache.org/jira/browse/AMBARI-17554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15361754#comment-15361754 ] 

Hadoop QA commented on AMBARI-17554:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12816063/AMBARI-17554.patch
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:red}-1 tests included{color}.  The patch doesn't appear to include any new or modified tests.
                        Please justify why no new tests are needed for this patch.
                        Also please list what manual steps were performed to verify this patch.

    {color:green}+1 javac{color}.  The applied patch does not increase the total number of javac compiler warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase the total number of release audit warnings.

    {color:green}+1 core tests{color}.  The patch passed unit tests in ambari-server.

Test results: https://builds.apache.org/job/Ambari-trunk-test-patch/7686//testReport/
Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/7686//console

This message is automatically generated.

> ambari-server update-host-name failing
> --------------------------------------
>
>                 Key: AMBARI-17554
>                 URL: https://issues.apache.org/jira/browse/AMBARI-17554
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.4.0
>            Reporter: Vitaly Brodetskyi
>            Assignee: Vitaly Brodetskyi
>            Priority: Critical
>             Fix For: 2.4.0
>
>         Attachments: AMBARI-17554.patch
>
>
> Steps to reproduce :
> 1) Run the following command on one of the hosts (which is not the ambari server) in the cluster : 
> {code}
> hostname renamedHost-0
> {code}
> 2) On the ambari-server change the host name in the /etc/hosts for the host whose name was changed in step1
> 3) Create a file like the following to indicate the host changed :
> {code}
> {
> 	"cl1" : {
> 		"renamedHost-0.openstacklocal" : "rerenamedhost-0.openstacklocal"
> 	}
> }
> {code}
> 4) Run ambari-server update-host-name <filename>
> The error shown :
> {code}
> 03 Jul 2016 07:24:31,914  INFO [main] Configuration:1022 - Reading password from existing file
> 03 Jul 2016 07:24:31,931  INFO [main] Configuration:1491 - Hosts Mapping File null
> 03 Jul 2016 07:24:31,932  INFO [main] HostsMap:60 - Using hostsmap file null
> 03 Jul 2016 07:24:32,742  INFO [main] ControllerModule:199 - Detected ORACLE as the database type from the JDBC URL
> 03 Jul 2016 07:24:34,884  INFO [main] ControllerModule:607 - Binding and registering notification dispatcher class org.apache.ambari.server.notifications.dispatchers.SNMPDispatcher
> 03 Jul 2016 07:24:34,895  INFO [main] ControllerModule:607 - Binding and registering notification dispatcher class org.apache.ambari.server.notifications.dispatchers.EmailDispatcher
> 03 Jul 2016 07:24:34,905  INFO [main] ControllerModule:607 - Binding and registering notification dispatcher class org.apache.ambari.server.notifications.dispatchers.AlertScriptDispatcher
> 03 Jul 2016 07:24:38,223 ERROR [main] HostUpdateHelper:545 - Unexpected error, host names update failed
> com.google.inject.CreationException: Guice creation errors:
> 1) No implementation for org.apache.ambari.server.audit.AuditLogger was bound.
>   while locating org.apache.ambari.server.audit.AuditLogger
>     for field at org.apache.ambari.server.actionmanager.ActionDBAccessorImpl.auditLogger(ActionDBAccessorImpl.java:86)
>   at org.apache.ambari.server.controller.ControllerModule.configure(ControllerModule.java:324)
> 2) No implementation for org.apache.ambari.server.audit.AuditLogger was bound.
>   while locating org.apache.ambari.server.audit.AuditLogger
>     for field at org.apache.ambari.server.api.services.LogoutService.auditLogger(LogoutService.java:41)
>   at org.apache.ambari.server.controller.ControllerModule.bindByAnnotation(ControllerModule.java:525)
> 2 errors
>         at com.google.inject.internal.Errors.throwCreationExceptionIfErrorsExist(Errors.java:435)
>         at com.google.inject.internal.InternalInjectorCreator.initializeStatically(InternalInjectorCreator.java:154)
>         at com.google.inject.internal.InternalInjectorCreator.build(InternalInjectorCreator.java:106)
>         at com.google.inject.Guice.createInjector(Guice.java:95)
>         at com.google.inject.Guice.createInjector(Guice.java:72)
>         at com.google.inject.Guice.createInjector(Guice.java:62)
>         at org.apache.ambari.server.update.HostUpdateHelper.main(HostUpdateHelper.java:516)
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)