uyuni-project / uyuni

Source code for Uyuni
https://www.uyuni-project.org/
GNU General Public License v2.0
431 stars 180 forks source link

cobbler sync not working #5986

Open martux69 opened 2 years ago

martux69 commented 2 years ago

When I change the kernel options of a distribution with the cobbler cli the changes will not be reflected to uyuni. Example:

cobbler distro edit --name=opensuse_tumbleweed:1:ORG --in-place --kernel-options="useonlinerepo=0"
cobbler distro report
Name                           : opensuse_tumbleweed:1:ORG
Architecture                   : x86_64
Automatic Installation Template Metadata : {'org': '1', 'autoyast': 'true', 'media_path': '/ks/dist/org/1/opensuse_tumbleweed'}
TFTP Boot Files                : {}
Boot loader                    : <<inherit>>
Breed                          : suse
Comment                        : 
Fetchable Files                : {}
Initrd                         : /srv/www/distributions/opensuse/tumbleweed/boot/x86_64/loader/initrd
Kernel                         : /srv/www/distributions/opensuse/tumbleweed/boot/x86_64/loader/linux
Kernel Options                 : {'self_update': ['0'], 'install': ['http://10.65.120.99/distributions/opensuse/tumbleweed/'], 'insecure': ['1'], 'useonlinerepo': '0'}
Kernel Options (Post Install)  : {}
Management Classes             : []
OS Version                     : suse
Owners                         : ['admin']
Redhat Management Key          : 
Remote Boot Initrd             : ~
Remote Boot Kernel             : ~
Template Files                 : {}

But in the Uyuni web gui: grafik

Executing cobber sync and restart of the uyuni services make no differences.

meaksh commented 1 year ago

Thanks @martux69 for contributing!

This is actually not expected to work. The changes you do via cobbler CLI to stored collections are not expected to be reflected in the Uyuni DB. Manually editing stored collections via cobbler CLI is not recommended and you need to be really careful when using it to manually edit collections to avoid this possible inconsistencies with attributes that are being managed by Uyuni, like it is the case here for "Kernel Options".

Uyuni DB is the main source of thrust here, and Uyuni takes cares of synchronize its expected values from Uyuni DB into the cobbler stored collections, but not the other way around.

IMHO this is not really a bug, but more of a feature request. Maybe close this one in favor of an "Enhancement" request?