Hi All,
Some feedback about the new imagenerator:
A - Unable to connect with ssh to my local machine while at the command
line it works without any issue:
1 - 1 - hosts
[ledefirmware]
my_ip_address ansible_user=my_user ansible_become_pass=my_passd
1 - 2 - playbook.yml
- hosts: ledefirmware
roles:
- openwisp.openwisp2-imagegenerator
...
1 - 3 - command line
ansible-playbook -i hosts playbook.yml -e "recompile=1 cores=4"
got the following result:
TASK [setup]
*******************************************************************
fatal: [my_ip_address]: UNREACHABLE! => {"changed": false, "msg": "Failed
to connect to the host via ssh: Permission denied
(publickey,password).\r\n", "unreachable": true}
however with:
2 - 1 - hosts
[ledefirmware]
192.168.10.13
2 - 2 - playbook.yml
- hosts: ledefirmware
become_method: sudo
roles:
- openwisp.openwisp2-imagegenerator
2 - 3
ansible-playbook -i hosts playbook.yml -u xavier -k --ask-become-pass -e
"recompile=1 cores=4"
I don't have any problems, right now I'm not in a production scenario where
the build server is remote, so I use the command line to input the passwd
B - Finally the .config is generated with the appropriate system, subtarget
and profile.
Yes it rocks.
C - On my Debian Stretch RC2 I face a missing mkpasswd while hashing the
password. I needed to;
sudo apt-get install whois
Yes the mkpasswd belongs to the whois package, unexpected...
Now I need to tweak the playbook.yml to get the job done.
First with a minimal LEDE firmware for my test router, then with the
openwisp-config like I did manually.
I noticed that recently there is a new dependance with px5g who uses
mbedtls. I need to carefully check whether or not curl is still in
dependence with openssl rather than mbedtls.
Many Thanks for this improvement
Cheers
--
You received this message because you are subscribed to the Google Groups
"OpenWISP" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
