aurora-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Maxim Khutornenko (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (AURORA-494) aurora_admin's perform_maintenance_hosts command doesn't fail on unknown hosts
Date Thu, 29 May 2014 23:59:09 GMT

     [ https://issues.apache.org/jira/browse/AURORA-494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Maxim Khutornenko resolved AURORA-494.
--------------------------------------

    Resolution: Duplicate

> aurora_admin's perform_maintenance_hosts command doesn't fail on unknown hosts
> ------------------------------------------------------------------------------
>
>                 Key: AURORA-494
>                 URL: https://issues.apache.org/jira/browse/AURORA-494
>             Project: Aurora
>          Issue Type: Bug
>          Components: Client, Scheduler
>            Reporter: David Robinson
>            Priority: Minor
>
> If you feed the aurora_admin's perform_maintenance_hosts command a filename containing
a list of random strings (supposedly FQDNs) it'll happily drain those random strings!
> {noformat}
> $ cat drain.txt 
> my-imaginary-server
> your-imaginary-server
> any-imaginary-server
> $ aurora_admin perform_maintenance_hosts --filename=drain.txt my-cluster
>  INFO] Ending maintenance for: set(['my-imaginary-server', 'your-imaginary-server', 'any-imaginary-server'])
>  INFO] Response from scheduler: OK (message: None)
>  INFO] Maintenance status for: set(['my-imaginary-server', 'your-imaginary-server', 'any-imaginary-server'])
>  INFO] Starting maintenance for: set(['my-imaginary-server', 'your-imaginary-server',
'any-imaginary-server'])
>  INFO] Response from scheduler: OK (message: None)
>  INFO] Draining tasks on: set(['any-imaginary-server'])
>  INFO] Response from scheduler: OK (message: None)
>  INFO] Sleeping for 30 secs.
>  INFO] Maintenance status for: ['any-imaginary-server']
>  INFO] Ending maintenance for: set(['any-imaginary-server'])
>  INFO] Response from scheduler: OK (message: None)
>  INFO] Maintenance status for: set(['any-imaginary-server'])
>  INFO] Draining tasks on: set(['my-imaginary-server'])
>  INFO] Response from scheduler: OK (message: None)
>  INFO] Sleeping for 30 secs.
>  INFO] Maintenance status for: ['my-imaginary-server']
>  INFO] Ending maintenance for: set(['my-imaginary-server'])
>  INFO] Response from scheduler: OK (message: None)
>  INFO] Maintenance status for: set(['my-imaginary-server'])
>  INFO] Draining tasks on: set(['your-imaginary-server'])
>  INFO] Response from scheduler: OK (message: None)
>  INFO] Sleeping for 30 secs.
>  INFO] Maintenance status for: ['your-imaginary-server']
>  INFO] Ending maintenance for: set(['your-imaginary-server'])
>  INFO] Response from scheduler: OK (message: None)
>  INFO] Maintenance status for: set(['your-imaginary-server'])
> {noformat}
> It'd be great if there was actually some validation that notified a user if a host wasn't
valid.
> This tripped me up because I was using hostnames instead of the FQDNs. Easy mistake to
make, difficult to troubleshoot when everything says 'OK'.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message