All I can say is that this has nothing to do with YAML, but with Python paths (code loading) in the workflow execution sub-process.
On Tue, Oct 10, 2017 at 10:29 AM, DeWayne Filppi <[email protected]> wrote: > In the absence of any context (because reproducing this is very involved), > does the below error ring any bells? I've seen it before, but don't recall > the fix. This error pops up during an install workflow. There seems to be > some kind of YAML problem, but it has already passed the parse/validation. > > | File > "/home/vagrant/incubator-ariatosca/aria/orchestrator/ > workflows/executor/process.py", > line 339, in _main > | aria.install_aria_extensions() > | File "/home/vagrant/incubator-ariatosca/aria/__init__.py", line > 66, in install_aria_extensions > | extension.init() > | File "/home/vagrant/incubator-ariatosca/aria/extension.py", > line > 153, in init > | parser.init() > | File "/home/vagrant/incubator-ariatosca/aria/extension.py", > line > 86, in init > | registrar.register(registrating_function) > | File "/home/vagrant/incubator-ariatosca/aria/extension.py", > line > 37, in register > | raise RuntimeError('Re-definition of {0} in {1}'.format(key, > function.__name__)) > |RuntimeError: Re-definition of yaml-1.1 in specification_url >
