[
https://issues.apache.org/jira/browse/AMBARI-1562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeff Sposetti updated AMBARI-1562:
----------------------------------
Description:
During Agent bootstrap + registration (the Confirm Hosts step), and during
cluster Install/Start/Test, there is a chance the hosted stack repositories or
the EPEL repository can timeout, giving an error "no more mirrors".
This causes the host to be marked "fail" which can be concerning to the user.
1) we should trap this timeout error specifically and auto-retry. The timeout
might only be temporary and will work on retry.
2) After a certain amount of retries, we should produce a specific "fail"
message for the end user to help troubleshoot.
was:
During Agent bootstrap + registration (the Confirm Hosts step), and during
cluster Install/Start/Test, there is a chance the hosted stack repositories or
the EPEL repository can timeout, giving an error "no more mirrors".
This causes the host to be marked "fail" which can be concerning to the user.
1) we should trap this timeout error specifically and auto-retry. The timeout
might only be temporary and will work on retry.
2) After a certain amount of retries, we should produce a specific "fail"
message for the end user to help them troubleshoot.
> During install, retry on repo timeout and show better error message is
> retries fail
> -----------------------------------------------------------------------------------
>
> Key: AMBARI-1562
> URL: https://issues.apache.org/jira/browse/AMBARI-1562
> Project: Ambari
> Issue Type: Improvement
> Affects Versions: 1.2.0
> Reporter: Jeff Sposetti
>
> During Agent bootstrap + registration (the Confirm Hosts step), and during
> cluster Install/Start/Test, there is a chance the hosted stack repositories
> or the EPEL repository can timeout, giving an error "no more mirrors".
> This causes the host to be marked "fail" which can be concerning to the user.
> 1) we should trap this timeout error specifically and auto-retry. The timeout
> might only be temporary and will work on retry.
> 2) After a certain amount of retries, we should produce a specific "fail"
> message for the end user to help troubleshoot.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
