[Android Q&A, Help & Troubleshooting] obsolete1:
I'm so close I can taste it...I read a similar post from an Xperia with the same problem but their solution does not work for me

Install system fs image: /home/robert/aokp/system/out/target/product/otter2/system.img
/home/robert/aokp/system/out/target/product/otter2/system.img+ maxsize=948486528 blocksize=4224 total=266563552 reserve=9584256
Package target files: /home/robert/aokp/system/out/target/product/otter2/obj/PACKAGING/target_files_intermediates/aokp_otter2-target_files-eng.robert.zip
Package OTA: /home/robert/aokp/system/out/target/product/otter2/aokp_otter2-ota-eng.robert.zip
./device/amazon/otter2/releasetools/bowser_ota_from_target_files -v \
-p /home/robert/aokp/system/out/host/linux-x86 \
-k build/target/product/security/testkey \
--backup=false \
--no_assert=false \
--override_device=otter2 \
/home/robert/aokp/system/out/target/product/otter2/obj/PACKAGING/target_files_intermediates/aokp_otter2-target_files-eng.robert.zip /home/robert/aokp/system/out/target/product/otter2/aokp_otter2-ota-eng.robert.zip

Given a target-files zipfile, produces an OTA package that installs
that build. An incremental OTA is produced if -i is given, otherwise
a full OTA is produced.

Usage: ota_from_target_files [flags] input_target_files output_ota_package

-b (--board_config) <file>
Deprecated.

-k (--package_key) <key> Key to use to sign the package (default is
the value of default_system_dev_certificate from the input
target-files's META/misc_info.txt, or
"build/target/product/security/testkey" if that value is not
specified).

For incremental OTAs, the default value is based on the source
target-file, not the target build.

-i (--incremental_from) <file>
Generate an incremental OTA using the given target-files zip as
the starting build.

-w (--wipe_user_data)
Generate an OTA package that will wipe the user data partition
when installed.

-n (--no_prereq)
Omit the timestamp prereq check normally included at the top of
the build scripts (used for developer OTA packages which
legitimately need to go back and forth).

-e (--extra_script) <file>
Insert the contents of file at the end of the update script.

-a (--aslr_mode) <on|off>
Specify whether to turn on ASLR for the package (on by default).

--backup <boolean>
Enable or disable the execution of backuptool.sh.
Disabled by default.

--configid <boolean>
Enable or disable the execution of modelid_cfg.sh.
Enabled by default.

--override_device <device>
Override device-specific asserts. Can be a comma-separated list.

-p (--path) <dir>
Prepend <dir>/bin to the list of places to search for binaries
run by this script, and expect to find jars in <dir>/framework.

-s (--device_specific) <file>
Path to the python module containing device-specific
releasetools code.

-x (--extra) <key=value>
Add a key/value pair to the 'extras' dict, which device-specific
extension code may look at.

-v (--verbose)
Show command lines being executed.

-h (--help)
Display this usage message and exit.

** option --no_assert not recognized **

I know this is towards the end of the MakeFile so I can assume that everything builds okay and it looks like it has a problem in the packaging...but I could be wrong

*EDIT:

I tried just plain deleting that section of the MakeFile and build finished YES!!! Commenting it out did not work strange now to see if it works