You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Andrew Onischuk (JIRA)" <ji...@apache.org> on 2015/10/06 13:54:26 UTC
[jira] [Created] (AMBARI-13322) Should not log "unable to get
latest URL" as ERROR
Andrew Onischuk created AMBARI-13322:
----------------------------------------
Summary: Should not log "unable to get latest URL" as ERROR
Key: AMBARI-13322
URL: https://issues.apache.org/jira/browse/AMBARI-13322
Project: Ambari
Issue Type: Bug
Reporter: Andrew Onischuk
Assignee: Andrew Onischuk
Fix For: 2.1.3
When running w/o internet, Ambari will not be able to reach the "latest URL".
Currently, this gets logged as an ERROR in ambari-server.log. But when
something else goes wrong (completely unrelated), users might think this ERROR
log entry is the cause. But it's not.
Since w/o internet is a common case, this should not be ERROR to minimize this
chance for confusion.
21 Sep 2015 22:12:39,673 INFO [Stack Version Loading Thread] LatestRepoCallable:74 - Loading latest URL info for stack HDP-2.2 from http://public-repo-1.hortonworks.com/HDP/hdp_urlinfo.json
21 Sep 2015 22:12:39,673 ERROR [Stack Version Loading Thread] LatestRepoCallable:93 - Could not load the URI for stack HDP-2.2 from http://public-repo-1.hortonworks.com/HDP/hdp_urlinfo.json (public-repo-1.hortonworks.com)
We should just make it INFO and maybe add a bit more info? Like this?
INFO [Stack Version Loading Thread] LatestRepoCallable:93 - Could not load the URI for stack HDP-2.2 from http://public-repo-1.hortonworks.com/HDP/hdp_urlinfo.json (public-repo-1.hortonworks.com). Using default repository values.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)