Skip to content
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

rocky9+warewulf+slurm network file not created #1946

Open
luciandf opened this issue Mar 4, 2024 · 5 comments
Open

rocky9+warewulf+slurm network file not created #1946

luciandf opened this issue Mar 4, 2024 · 5 comments

Comments

@luciandf
Copy link

luciandf commented Mar 4, 2024

Hello all,

I keep having problems with this new v3.x recipe. The network file is not created. There is a txt file in /etc/sysconfig/network-scripts saying that now the network configuration files are stored in /etc/NetworkManager/system-connections (because why not!) but there is nothing being generated there.

Does warewulf 3 know that if should put stuff there? Can I make it aware of this?

@adrianreber
Copy link
Member

It works in our CI system. Are you talking about SMS or clients? Warewulf 3 still uses sysconfig on the compute nodes and it still works.

@luciandf
Copy link
Author

luciandf commented Mar 4, 2024

there is nothins network related being created in the image. all I find is just this file called readme-ifcfg-rh.txt containing:

NetworkManager stores new network profiles in keyfile format in the
/etc/NetworkManager/system-connections/ directory.

Previously, NetworkManager stored network profiles in ifcfg format
in this directory (/etc/sysconfig/network-scripts/). However, the ifcfg
format is deprecated. By default, NetworkManager no longer creates
new profiles in this format.

Connection profiles in keyfile format have many benefits. For example,
this format is INI file-based and can easily be parsed and generated.

Each section in NetworkManager keyfiles corresponds to a NetworkManager
setting name as described in the nm-settings(5) and nm-settings-keyfile(5)
man pages. Each key-value-pair in a section is one of the properties
listed in the settings specification of the man page.

If you still use network profiles in ifcfg format, consider migrating
them to keyfile format. To migrate all profiles at once, enter:

# nmcli connection migrate

This command migrates all profiles from ifcfg format to keyfile
format and stores them in /etc/NetworkManager/system-connections/.

Alternatively, to migrate only a specific profile, enter:

# nmcli connection migrate <profile_name|UUID|D-Bus_path>

For further details, see:
* nm-settings-keyfile(5)
* nmcli(1)

@luciandf
Copy link
Author

luciandf commented Mar 4, 2024

and the same thing I have on the SMS... the network connection file is at /etc/NetworkManager/system-connections/enp6s18.nmconnection. System is Rocky 9.3.

@adrianreber
Copy link
Member

The configuration via sysconfig still works. I guess you are missing certain configuration variables before running the recipe.

Take a look at our results: http://repos.ohpc.io/stats/results/3/3.1/0-LATEST-OHPC-3.1-almalinux9.2-x86_64/console.out

If you search for c_ip[0] you see what we set. Do you have those values correctly set for for compute nodes?

@luciandf
Copy link
Author

luciandf commented Mar 4, 2024

something is happening because there is no network config file being generated on the client image. i tried again after installing the docs-ohpc package and finally found the recipe and inputs file. still nothing is happening.

is there another way to do this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants