Hi, to share my testing experience with cobbler2.0 (thanks for it!) hoping it can hepls others.
My context: - having one cobbler server1 being migrated from 1.6.x to 2.0. - having one cobbler server2 directly installed in 2.0 Both servers configured with ldap authentication in /etc/cobbler/[settings, modules.conf] authorization is also on in modules.conf [module = authz_ownership] Both servers are running with SELinux in enforcing mode. The cobbler 2.0 SW was built from the source in each case. I noticed the following: - on server2 set up from scratch cobbler import .... was complaining that the issued rsync command was failing I had to disable selinux for rsync to make cobbler import working with the following command. root# setsebool -P rsync_disable_trans=1 may be a better way exist ? or something to be notified by the cobbler check command ? Note this is not an issue is selinux is _not_ in enforcing mode. - on server1 (migrated from 1.6.x) and after migration: - Had to removed the "omapi" section from the /etc/cobbler/dhcp.template file a task for cobbler check ? (not sure but that helps dumb guy like myself not reading the docs... :-( ) - Some text comments attached with the systems had "accents"/diacritics char. I had to removed them (from jason files) to avoid a python stack trace in the new WEB interface (1.6.x was not having issue there - may be due to the move to django) - In the new WEB interface, I got python stack trace when trying to sort the "Systems" view on a per profile basis The pb was with the /usr/share/cobbler/session/sessionid..... file the following solved the issue: root# chcon -t httpd_sys_content_t /usr/share/cobbler/web/sessions and to be sure it will be persistent: root # /usr/sbin/semanage fcontext -a -t httpd_sys_content_t "/usr/share/cobbler/web(/.*)?" may be something that can be addressed at installation time ? Note this is not an issue is selinux is _not_ in enforcing mode. - The "owners" field is not displayed anymore in the web interface. That was very usefull to figure out who to contact. Any easy way to make it visible again ? Apart the small annoyance sabove, cobbler2.0 on server1 (the migrated one) works very well and I continue testing and experimenting with it. thanks, Phil.
_______________________________________________ cobbler mailing list cobbler@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/cobbler