[jira] [Created] (UIMA-6103) start_ducc should always check ssh access
Burn Lewis created UIMA-6103: Summary: start_ducc should always check ssh access Key: UIMA-6103 URL: https://issues.apache.org/jira/browse/UIMA-6103 Project: UIMA Issue Type: Bug Components: DUCC Affects Versions: 3.0.0-Ducc Reporter: Burn Lewis Only one of the 2 ways to start agents makes the check ... change so both use the same code -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Resolved] (UIMA-6099) DUCC should reject invalid scheduling class names
[ https://issues.apache.org/jira/browse/UIMA-6099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Burn Lewis resolved UIMA-6099. -- Resolution: Fixed > DUCC should reject invalid scheduling class names > - > > Key: UIMA-6099 > URL: https://issues.apache.org/jira/browse/UIMA-6099 > Project: UIMA > Issue Type: Bug > Components: DUCC >Affects Versions: 3.0.0-Ducc >Reporter: Burn Lewis >Assignee: Burn Lewis >Priority: Minor > Fix For: future-DUCC > > > Currently job requests hang if the scheduling class is unknown -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Commented] (UIMA-6099) DUCC should reject invalid scheduling class names
[ https://issues.apache.org/jira/browse/UIMA-6099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16896450#comment-16896450 ] Burn Lewis commented on UIMA-6099: -- Moved scheduling class checks from CLI to OR or SM assign default -- check for valid name -- change to a fixed class if necessary. > DUCC should reject invalid scheduling class names > - > > Key: UIMA-6099 > URL: https://issues.apache.org/jira/browse/UIMA-6099 > Project: UIMA > Issue Type: Bug > Components: DUCC >Affects Versions: 3.0.0-Ducc >Reporter: Burn Lewis >Assignee: Burn Lewis >Priority: Minor > Fix For: future-DUCC > > > Currently job requests hang if the scheduling class is unknown -- This message was sent by Atlassian JIRA (v7.6.14#76016)
