Bugs : error when calling a module from a raft and create an module with a path

[PhilippeC.]

Hi,
I have got two errors:

1. You get an error msg when you call a module which is in a raft (not the default raft).

Unable to resolve method: **Raft::Module**

2. when you want to create a module in a path you have the following warning msg:

There were one or more errors processing your script:
This script is not in an expected format; a template plan must contain a single named template block with a name that matches the template name. This could happen if the script file was edited directly, or some other error occurred while saving. The template cannot be edited in visual mode until this is resolved.
If you FORCE SAVE, this template will not be able to be called by any other plans.

Test case for error 1:
Create a raft TestRaft
Create a module in TestRaft

##AH:UseTextMode
module ModuleInTestRaft
{
    Log-Debug ModuleInTestRaft;
}

Create a Plan CallModuleinRaft in Default Raft

##AH:UseTextMode
call TestRaft::ModuleInTestRaft();

Results :

DEBUG: 2019-11-02 15:06:17Z - Job 723 directly targets 1 server(s) by name.
DEBUG: 2019-11-02 15:06:17Z - Skipping collection run; execute only.
INFO : 2019-11-02 15:06:17Z - Collection run succeeded.
DEBUG: 2019-11-02 15:06:17Z - Beginning execution run...
ERROR: 2019-11-02 15:06:17Z - Unable to resolve method: TestRaft::ModuleInTestRaft
DEBUG: 2019-11-02 15:06:17Z - Cleaning up temporary files on Linux/SSH (10.1.111.11:22)...

Environnement:
Otter 2.2.10

Cdt
PhilippeC.

[ben]

Hello @PhilippeC,

Thanks for the bug report. I've identified the root cause for the first error and have a fix currently being reviewed. I haven't used raft paths at all, so I've asked a co-worker to look at the second error.

[gdivis]

Hi Philippe,

I've logged the path issue as OT-357, and scheduled a fix to be included in the next release of Otter (2.2.11), currently planned for release on Nov 15.

Thanks!
-Greg

[PhilippeC.]

Good news ...