search

OpenNebula / one-apps

Toolchain to build OpenNebula appliances
Apache License 2.0
12 stars 10 forks source link

Template network contextualization doesn't work with Open Nebula 6.8.0 and RHEL9 #119

Closed jschoewe closed 3 months ago

jschoewe commented 3 months ago

Description We're trying to instantiate a RHEL 9 template with a static IP. We installed the context packages onto the template according to this: https://github.com/OpenNebula/one-apps/wiki/linux_installation. RHEL 9 uses NetworkManager by default. The hostnames and static IPs show up just fine after instantiating, however, the gateway and DNS servers never get set. I've attached a picture of the template variables, I've tried every combination of params that I can think of in here, including removing NETWORK = "YES" and setting each ETH0 param manually and the DNS servers never get set.

To Reproduce Instantiate template with static IP

Expected behavior The given DNS servers should be associated with the network interface.

Details

Additional context I opened support case 54333 for this issue and it was prematurely closed. The following workaround was given: In Sunstone:

While this does work, manually updating every network object if our DNS servers ever change is not a viable long-term solution. This is also not documented anywhere, including the known issues page, so this issue is needed for visibility in case others experience the same issue.

Progress Status

OpenNebulaSupport commented 3 months ago

After testing: VM-specific ETH* context parameters can not be set, vnet context is being used. Same issue as in issue#6606

Issue related to issue#6552

rsmontero commented 3 months ago

After testing: VM-specific ETH* context parameters can not be set, vnet context is being used. Same issue as in issue#6606

Issue related to issue#6552

This issue is different, it seems the parameter set is properly set by ignored by the context packages. I'm moving this issue to one-app repo

rsmontero commented 3 months ago

OK, re-reading closing this issue and address this as part of the other ones already opened.