[ https://issues.jboss.org/browse/JBIDE-25703?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-25703: ------------------------------------- When executing the following steps, I cannot replicate: 1. Exec: Have downloaded cdk 3.3 2. Exec: Create CDK 3.2+ server adapter 3. Exec: Start server adapter 4. Assert: Adapter is started, Os connection is created 5. Exec: Open OS 3 connection 6. Assert: check that path to oc is propagated into 'Override 'oc' location' label Actual result: The openshift connection has "override workspace setting" checked, and a value is already there, and is correct. Note that we did not set the workspace setting in this usecase. When executing different steps, I still cannot replicate: 1. Exec: Have downloaded cdk 3.3 2. Exec: Create CDK 3.2+ server adapter 3. Exec: Start server adapter 4. Assert: Adapter is started, Os connection is created 5. Exec: Setup OC for workspace in Preferences (ie. ~/.minishift/cache/oc/v3.7.14/windows/oc.exe) 6. Exec: Open OS 3 connection 7. Assert: "override oc location" is checked 8. Assert that if you uncheck "override oc location", the page has no errors And a third usecase: 1. Exec: Have downloaded cdk 3.3 2. Exec: Create CDK 3.2+ server adapter 3. Exec: Start server adapter 4. Assert: Adapter is started, Os connection is created 5. Exec: Open OS 3 connection 6. Assert: "override oc location" is checked 7. Uncheck 'override oc location' 8. Assert the field does not validate, because workspace setting is missing 9. Click the Workspace Settings hyperlink 10. Set the workspace setting. Click apply. Close the preference window, focus on the openshift 3 connection wizard 11. Assert the validation is now successful. If the complaint here is that the validation doesn't go away until you close the preference page, that's a bit of a stretch in terms of a bug. Validation will only be kicked off once the preference page is closed, not once the setting is changed. Is this the bug? -- This message was sent by Atlassian JIRA (v7.5.0#75005)