-
Notifications
You must be signed in to change notification settings - Fork 41
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
Issue with AlmaLinux cluster on Azure due to DHCP problem #338
Comments
Ah, no, seems like the error is elsewhere:
|
There was a release of |
Hmm, that is also not it:
|
-agent[10516]: Requesting catalog from mgmt1:8140 (10.0.1.6)
-agent[10516]: Catalog compiled by mgmt1
-agent[10516]: (/Stage[main]/Profile::Freeipa::Client/Exec[set_hostname]/returns) executed successfully (corrective)
-agent[10516]: (/Stage[main]/Jupyterhub::Kernel::Venv/Exec[kernel_venv]/returns) × No interpreter found in managed installations or system path
-agent[10516]: 'uv venv --seed --python-preference system /opt/ipython-kernel-eessi' returned 1 instead of one of [0]
-agent[10516]: (/Stage[main]/Jupyterhub::Kernel::Venv/Exec[kernel_venv]/returns) change from 'notrun' to ['0'] failed: 'uv venv --seed --python-preference system /opt/ipyt>
-agent[10516]: (/Stage[main]/Jupyterhub::Kernel::Venv/Exec[pip_ipykernel]) Dependency Exec[kernel_venv] has failures: true
-agent[10516]: (/Stage[main]/Jupyterhub::Kernel::Venv/Exec[pip_ipykernel]) Skipping because of failed dependencies
-agent[10516]: (/Stage[main]/Jupyterhub::Kernel::Venv/File[/opt/ipython-kernel-eessi/etc]) Skipping because of failed dependencies
-agent[10516]: (/Stage[main]/Jupyterhub::Kernel::Venv/File[/opt/ipython-kernel-eessi/etc/ipython]) Skipping because of failed dependencies
-agent[10516]: (/Stage[main]/Jupyterhub::Kernel::Venv/File[/opt/ipython-kernel-eessi/etc/ipython/ipython_config.py]) Skipping because of failed dependencies
-agent[10516]: (/Stage[main]/Profile::Freeipa::Client/Exec[ipa-install]/returns) [output redacted]
-agent[10516]: [command redacted] returned 2 instead of one of [0]
-agent[10516]: (/Stage[main]/Profile::Freeipa::Client/Exec[ipa-install]/returns) change from 'notrun' to ['0'] failed: [command redacted] returned 2 instead of one of [0] >
-agent[10516]: (/Stage[main]/Profile::Freeipa::Base/Service[systemd-logind]) Dependency Exec[ipa-install] has failures: true
-agent[10516]: (/Stage[main]/Profile::Freeipa::Base/Service[systemd-logind]) Skipping because of failed dependencies
-agent[10516]: (/Stage[main]/Profile::Freeipa::Client/File_line[ssh_known_hosts]) Skipping because of failed dependencies
-agent[10516]: (/Stage[main]/Profile::Freeipa::Client/Exec[selinux_login_default]) Skipping because of failed dependencies
-agent[10516]: (/Stage[main]/Profile::Freeipa::Client/Augeas[selinux_provider]) Skipping because of failed dependencies
-agent[10516]: (/Stage[main]/Profile::Sssd::Client/Service[sssd]) Skipping because of failed dependencies
-agent[10516]: (/Stage[main]/Profile::Slurm::Node/Service[slurmd]) Skipping because of failed dependencies
-agent[10516]: (/Stage[main]/Profile::Slurm::Node/Exec[systemctl restart slurmd]) Skipping because of failed dependencies
-agent[10516]: Applied catalog in 127.82 seconds |
The puppet log from a fresh boot looks like:
|
Interestingly, the problem only seems to occur on the Arm node, the Zen4 node came up just fine. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I tried to create a new cluster on Azure today using the same configuration that I used yesterday but while puppet configures successfully there seems to be a problem connecting to the cluster. I think it is a network issue:
and I notice there is a very recent issue similar to it upstream at RedHat: https://access.redhat.com/solutions/7002283
The text was updated successfully, but these errors were encountered: