-
Notifications
You must be signed in to change notification settings - Fork 76
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ansible-core 2.14.5 & beefed up for latest 32-bit ARM (armhf) cryptography / piwheels / rust problems #3550
Conversation
FYI install appears to fail on 32-bit ARM for reasons beyond our control — ansible-core-2.11.12 partially installs as follow:
|
While the above error is ugly, it's also possible it simply doesn't matter when preparing a microSD for 32-bit RPi Zero W using a much more modern 64-bit Raspberry Pi... ? In any case: All Ansible-related work like installing of IIAB software and provisioning content... is generally-if-not-always completed entirely on a 64-bit Raspberry Pi... prior to inserting the microSD card into a 32-bit Zero W. |
I don't think requiring provision on 64 bit for 32 bit is too restrictive. |
Should be armv7l for the wheels. What kind of Pi is this and what does uname -m return? |
|
Example of good install #3494 (comment) |
Ansible installed on armv7 or better will now not run ansible when booted on an armv6l machine. |
Any objections to merging this well-tested-on-most-platforms PR as is? (And refining down the road if/as nec?) |
one minute please |
pycparser-2.21 is being pulled from outside of piwheels, that might be the issue, but push this and retry on an armv7 or better. |
From the looks of the test above ansible will not run on armv6l at all or the newest wheels from piwheels are suffering from the recent change to boot 64bit kernels by default. Think that one change broke most of the build pipelines out in the wild. The regular installs on non 'w' hardware with this PR will help sort out if the wheels are broken or not. |
This PR's
|
maybe cryptography==40.0.1 is buggy, might want to try an older version. |
CLARIF:
|
Shove that sdcard into a w and do the --version test |
cryptography==39.0.2 fails in the same way on armv6l :
|
About 5 min later, ansible-core 2.14.5 (that worked on 32-bit RasPiOS in RPi 3) failed as follows:
ASIDE: Just a reminder that even if Ansible ever does run on Zero W, it would be so painfully & incredibly slow, that no sane person should do this. 🐌 |
Wonder how far back this armv6l issue goes? Nothing stopping somebody from fiddling around in admin-console once booted on any hardware, that is where this ansible issue can burn the user. I would be looking at changing the minimum supported hardware recommendation just saying armv6l is not supported any way going forward. |
Might have to go back to a 'pre-rust' release, 38.0.4 if I recall correctly. For the same reasons of not having available wheels think U2304 32bit arm might not be recommended either. I haven't booted the 32bit version in a long time and I'm not investing any of my time to find out. |
Same problem with cryptography==38.0.4 just like cryptography==39.0.2 just like as cryptography==40.0.1:
WIth cryptography==37.0.4 the error is a bit different:
Either way, it looks like it's time to face the music... admitting that Ansible's not needed on 32-bit Raspberry Pi Zero W's 🕊️ |
Recap:
|
Tested on Ubuntu 23.04, 64-RasPiOS and
dpkg --print-architecture
output verified on 32-bit ARM (armhf).Building on: