[jboss-jira] [JBoss JIRA] (WFCORE-1354) Cannot clone a profile with a remoting subsystem but no io subsystem

[Brian Stansberry (JIRA)]

Brian Stansberry created WFCORE-1354:
----------------------------------------

             Summary: Cannot clone a profile with a remoting subsystem but no io subsystem
                 Key: WFCORE-1354
                 URL: https://issues.jboss.org/browse/WFCORE-1354
             Project: WildFly Core
          Issue Type: Bug
          Components: Domain Management, Remoting
    Affects Versions: 2.0.10.Final
            Reporter: Brian Stansberry
            Assignee: Brian Stansberry
             Fix For: 2.0.11.Final


The remoting subsystem added a requirement for the new io subsystem's worker capability, but it has special logic such that the requirement is only added if an endpoint resource is configured. So, legacy configs (pre-io) won't have that resource, so there is no requirement.

This breaks down in the case of the profile 'clone' op, as a placeholder resource we add for the endpoint (to allow reads of the default endpoint config data) ends up getting 'described' and added by the cloning process. So that added resource triggers an unmet requirement for the io worker:

{code}
[domain at localhost:9990 /] /profile=default:clone(to-profile=test)
{
    "outcome" => "failed",
    "failure-description" => {"domain-failure-description" => "WFLYCTL0369: Required capabilities are not available:
    org.wildfly.io.worker.default in context 'profile=test'; There are no known registration points which can provide this capability."},
    "rolled-back" => true
}
{code}

I'm not sure how to deal with this; some sort of marker is needed to disable 'describing' that placeholder resource.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)