Cannot deploy with MAAS because of broken legacy reporter import

[Blake Rouse]

I am unable to deploy using curtin trunk because the legacy reporter fails to import.

[ 32.374747] cloud-init[969]: Traceback (most recent call last):
[ 32.375585] cloud-init[969]: File "/usr/lib/python3.4/runpy.py", line 170, in _run_module_as_main
[ 32.376609] cloud-init[969]: "__main__", mod_spec)
[ 32.377345] cloud-init[969]: File "/usr/lib/python3.4/runpy.py", line 85, in _run_code
[ 32.380289] cloud-init[969]: exec(code, run_globals)
[ 32.381252] cloud-init[969]: File "/curtin/curtin/commands/main.py", line 153, in <module>
[ 32.384207] cloud-init[969]: sys.exit(main())
[ 32.385254] cloud-init[969]: File "/curtin/curtin/commands/main.py", line 77, in main
[ 32.392364] cloud-init[969]: add_subcmd(subps, subcmd)
[ 32.393772] cloud-init[969]: File "/curtin/curtin/commands/main.py", line 37, in add_subcmd
[ 32.395015] cloud-init[969]: __import__(subcmd_full)
[ 32.396000] cloud-init[969]: File "/curtin/curtin/commands/install.py", line 32, in <module>
[ 32.400220] cloud-init[969]: from curtin.reporter.legacy import load_reporter
[ 32.401051] cloud-init[969]: ImportError: No module named 'curtin.reporter.legacy'

[Ryan Harper (raharper)]

Can you provide more information on how curtin was invoked? Including any
curtin config that was passed.

On Sun, Aug 30, 2015 at 10:19 AM, Blake Rouse <email address hidden>
wrote:

> Public bug reported:
>
> I am unable to deploy using curtin trunk because the legacy reporter
> fails to import.
>
> [ 32.374747] cloud-init[969]: Traceback (most recent call last):
> [ 32.375585] cloud-init[969]: File "/usr/lib/python3.4/runpy.py", line
> 170, in _run_module_as_main
> [ 32.376609] cloud-init[969]: "__main__", mod_spec)
> [ 32.377345] cloud-init[969]: File "/usr/lib/python3.4/runpy.py", line
> 85, in _run_code
> [ 32.380289] cloud-init[969]: exec(code, run_globals)
> [ 32.381252] cloud-init[969]: File "/curtin/curtin/commands/main.py",
> line 153, in <module>
> [ 32.384207] cloud-init[969]: sys.exit(main())
> [ 32.385254] cloud-init[969]: File "/curtin/curtin/commands/main.py",
> line 77, in main
> [ 32.392364] cloud-init[969]: add_subcmd(subps, subcmd)
> [ 32.393772] cloud-init[969]: File "/curtin/curtin/commands/main.py",
> line 37, in add_subcmd
> [ 32.395015] cloud-init[969]: __import__(subcmd_full)
> [ 32.396000] cloud-init[969]: File "/curtin/curtin/commands/install.py",
> line 32, in <module>
> [ 32.400220] cloud-init[969]: from curtin.reporter.legacy import
> load_reporter
> [ 32.401051] cloud-init[969]: ImportError: No module named
> 'curtin.reporter.legacy'
>
> ** Affects: curtin
> Importance: Critical
> Status: Triaged
>
> --
> You received this bug notification because you are subscribed to curtin.
> Matching subscriptions: curtin-bugs-all
> https://bugs.launchpad.net/bugs/1490288
>
> Title:
> Cannot deploy with MAAS because of broken legacy reporter import
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/curtin/+bug/1490288/+subscriptions
>

[Ryan Harper (raharper)]

Quick checking of a deployed curtin environment shows that I can import it
with the curtin module in PYTHONPATH.

I can also use the legacy config included in docs/topics/reporting.rst with
no issue.

On Sun, Aug 30, 2015 at 3:14 PM, Ryan Harper <email address hidden>
wrote:

> Can you provide more information on how curtin was invoked? Including any
> curtin config that was passed.
>
> On Sun, Aug 30, 2015 at 10:19 AM, Blake Rouse <email address hidden>
> wrote:
>
>> Public bug reported:
>>
>> I am unable to deploy using curtin trunk because the legacy reporter
>> fails to import.
>>
>> [ 32.374747] cloud-init[969]: Traceback (most recent call last):
>> [ 32.375585] cloud-init[969]: File "/usr/lib/python3.4/runpy.py", line
>> 170, in _run_module_as_main
>> [ 32.376609] cloud-init[969]: "__main__", mod_spec)
>> [ 32.377345] cloud-init[969]: File "/usr/lib/python3.4/runpy.py", line
>> 85, in _run_code
>> [ 32.380289] cloud-init[969]: exec(code, run_globals)
>> [ 32.381252] cloud-init[969]: File "/curtin/curtin/commands/main.py",
>> line 153, in <module>
>> [ 32.384207] cloud-init[969]: sys.exit(main())
>> [ 32.385254] cloud-init[969]: File "/curtin/curtin/commands/main.py",
>> line 77, in main
>> [ 32.392364] cloud-init[969]: add_subcmd(subps, subcmd)
>> [ 32.393772] cloud-init[969]: File "/curtin/curtin/commands/main.py",
>> line 37, in add_subcmd
>> [ 32.395015] cloud-init[969]: __import__(subcmd_full)
>> [ 32.396000] cloud-init[969]: File
>> "/curtin/curtin/commands/install.py", line 32, in <module>
>> [ 32.400220] cloud-init[969]: from curtin.reporter.legacy import
>> load_reporter
>> [ 32.401051] cloud-init[969]: ImportError: No module named
>> 'curtin.reporter.legacy'
>>
>> ** Affects: curtin
>> Importance: Critical
>> Status: Triaged
>>
>> --
>> You received this bug notification because you are subscribed to curtin.
>> Matching subscriptions: curtin-bugs-all
>> https://bugs.launchpad.net/bugs/1490288
>>
>> Title:
>> Cannot deploy with MAAS because of broken legacy reporter import
>>
>> To manage notifications about this bug go to:
>> https://bugs.launchpad.net/curtin/+bug/1490288/+subscriptions
>>
>
>

[Ryan Harper (raharper)]

Requesting invocation command line and any configs specified.

[Blake Rouse (blake-rouse)]

It has nothing to do with the configuration file. The package that is built and installed has it missing. Install curtin from ppa:maas-maintainers/experimental, which smoser pushed and it will be missing.

ubuntu@maas-net:~$ ls /usr/lib/python2.7/dist-packages/curtin/reporter/
events.py handlers.py __init__.py registry.py
events.pyc handlers.pyc __init__.pyc registry.pyc

There is no legacy folder! Something is broken in the way the packaging is built.

[Ryan Harper (raharper)]

Yeah, looks like setup.py doesn't have curtin.reporter.legacy which would
trigger the import and copy of the files into target.

On Sun, Aug 30, 2015 at 4:36 PM, Blake Rouse <email address hidden>
wrote:

> It has nothing to do with the configuration file. The package that is
> built and installed has it missing. Install curtin from ppa:maas-
> maintainers/experimental, which smoser pushed and it will be missing.
>
> ubuntu@maas-net:~$ ls /usr/lib/python2.7/dist-packages/curtin/reporter/
> events.py handlers.py __init__.py registry.py
> events.pyc handlers.pyc __init__.pyc registry.pyc
>
> There is no legacy folder! Something is broken in the way the packaging
> is built.
>
> ** Changed in: curtin
> Status: Incomplete => Triaged
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1490288
>
> Title:
> Cannot deploy with MAAS because of broken legacy reporter import
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/curtin/+bug/1490288/+subscriptions
>

[Scott Moser (smoser)]

fixing.

[Blake Rouse (blake-rouse)]

Please upload a new package to the experimental ppa once fixed.

[Scott Moser (smoser)]

shoudl be fixed now and uploaded.

[Scott Moser (smoser)]

marking fix-released because it had only ever been regressed in trunk and only ever published to the place where it is now fixed.