What to do if I see:

---

... paramiko.transport - INFO - Authentication (publickey) failed.

... root - DEBUG - connect (2): Authentication failed.
... root - ERROR - Can't connect to FC* as toor4nsn: Authentication failed.

several potential reasons:

* ssh not enabled yet (use BTSSM)

* as usual for a full Enb running the authorized_keys for toor4nsn is empty
under .ssh/
(ls -l /user/toor4nsn/.ssh/authorized_keys
-rw------- 1 root root 0 Sep 18 2015 /user/toor4nsn/.ssh/authorized_keys)
you have to add "--ask_for_password" to your command line
E.g.
echo "[password]" | python yaft.py -i 192.168.255.129 -z my_load.zip -R
--ask_for_password

* Someone broke the ownership of toor4nsn directory (should be 'root root')

Error case:
-----------
ls -ld /ffs/fs1/config/toor4nsn
drwxr-xr-x 3 99000712 2012 4096 Jul 27 05:59 /ffs/fs1/config/toor4nsn

Fix it by:
----------
chown root:root /ffs/fs1/config/toor4nsn

Correct case:
-------------
ls -ld /ffs/fs1/config/toor4nsn
drwxr-xr-x 3 root root 4096 Jul 27 2017 /ffs/fs1/config/toor4nsn

---

... File "C:\Python27\Lib\getpass.py", line 95, in win_getpass

... msvcrt.putch(c)
... TypeError: putch() argument 1 must be char, not unicode

When giving "--ask_for_password" this might occure on Windows machines.

This is a known problem in some Python Windows versions. See:
https://github.com/eddie3/gogrepo/issues/24
https://github.com/vassim/linuxacademy-dl/issues/17

Please update your Python version (_not_ a YAFT issue)

---

... Yupper returned error ...

... Please contact I_EXT_LFS_BOOT@internal.nsn.com

The called yupper script failed - this is _not_ a YAFT issue.

Please write email to above mailing list and provide:
* the yaft log file
* the 2 yupper log files from the target
---

... Error: Your load contains only '0' entries to copy to your HW (FCTJ/FCTJ). At
least '6' expected. Wrong content/load?

YAFT can't find any content to be copied to HW. This could be because:
* your zip-file given does not contain any content for your HW (wrong package for
your HW)
* your zip file given contains additional subdirectory like
CBTS00_FSM4_MZ_9999_000367_000012_release_BTSSM_downloadable/bts_sw/TragetBD*
instead of just
bts_sw/TragetBD*
so YAFT can't find the TragetBD file as it is located in a sub-sub-directory.
(Means your zip file is broken. You could extract the zip and use -d option as
workaround.)
* your directory given is empty - no XML file could be found

---

Which version of the YAFT tool should I use?

Short answer: always the latest available!

Check out: which version of the YAFT tool should I use
and don't forget to update at least once/day!

---

... ERROR - Can't connect to channel ... sftp not running on your HW!

'sftp' is not running on your HW (is needed to copy files (of the load) to your
HW).
Please check on your HW following command:
grep sftp /etc/ssh/sshd_config
should return something like:
Subsystem sftp /usr/lib/ssh/sftp-server

If missing (broken load), add above line to the end of the file and restart (see
further down)
if available, check if path/file (in this example '/usr/lib/ssh/sftp-server') is
existing
If not existing, check for right location by:
find / -name "sftp-server"
and replace the entry with this location in the config.
If existing, hmmm, scary, try to restart sftp daemon

After all above scenariostry restart/activate the sftp daemon by:

on FSM3 : /usr/lib/ssh/sftp-server
on FSM4/LF/... : systemctl restart sshd

---

... cp: error writing '/ffs/fs3/...': No space left on device

The 3rd/failsafe partition (fs3) is quiet small - currently no PS_REL fits to this
small partition
(see https://jira3.int.net.nokia.com/browse/CNI-21414)
So try to flash LFS only. Something like:
python yaft.py -R \
-x /build/ltesdkroot//Platforms/xx_PS_LFS_REL/<LFS release>-
LTE/os/version_control.xml \
--flash_failsafe_partition \
<your additional parameter like IP ...>

---

... ddal -s ddal_boot_set_reset_loop_count 0 ...

... root - ERROR - Error: Can't set reset counter to zero (DDAL_RETURN_VALUE=-2
DDAL_STRERROR='No such file or directory'
)

DDAL does not (yet) support this function even mentioned in help
=> DDAL implementation issue in the running SW
Never the less it is one of the last steps in SW update,
so just reboot your HW and next SW update will run smoothly.

---