-
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
error installing on ub 2404 vm #3737
Comments
root@ub2204base:/opt/iiab/iiab# ll /usr/share/doc/avahi-daemon/examples/ |
iiab/roles/network/tasks/install.yml Lines 21 to 24 in 673fff9
Any chance you've set Run |
I'm rerunning, but it looked like avahi was installed but was missing a file |
using stock local vars none |
Nope. I built an entirely new vm and got the same error
|
/usr/share/doc/avahi-daemon/examples is just empty |
on Deb 12 I see
|
I patched it with ssh.service from deb 12 install and got past the error. |
FWIW I cannot reproduce this, e.g. on this 24.04 VM: http://sprunge.us/942sP6?en
Can you create an empty 24.04 VM (do not install anything) and then run For me this is the result:
(Is your result different? Any idea why if so?) |
root@ub2404base:~# ll /usr/share/doc/avahi-daemon/examples |
Wonder if it's my Canadian archive root@ub2404base:~# cat /etc/apt/sources.list.d/ubuntu.sources Types: deb |
Insane! If apt is failing to deliver legit apt packages a week after 24.04's release, this sounds quite serious. |
TASK [1-prep : Grab a clean copy of ssh.service] *************************************************************************************
An exception occurred during task execution. To see the full traceback, use -vvv. The error was: If you are using a module and expect the file to exist on the remote, see the remote_src option
fatal: [127.0.0.1]: FAILED! => {"changed": false, "msg": "Could not find or access '/usr/share/doc/avahi-daemon/examples/ssh.service' on the Ansible Controller.\nIf you are using a module and expect the file to exist on the remote, see the remote_src option"}
The text was updated successfully, but these errors were encountered: