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
2.6.6 Fails to start without proxy_url_ext (and _int?) defined in settings #1311
Comments
the real discussion here is what to do when attributes are added/removed/updated in Cobbler settings. imho we should provide a migration script (easier for user) or provide required environment changes in release notes (easier for developers). |
yes, my bad. it's hardwired into my brain to review .rpmnew files after upgrading.... but i agree we should handle this case more gracefuly... |
between minor version upgrades, cobbler shouldn't fail to start, because a new attribute that's been added doesn't exist in the configuration file. |
I'll add new proxy settings to DEFAULTS list in cobbler/settings.py, this will solve this problem. |
@opoplawski: a3a67a4 in master fixes this issue. It must be backported to 2.6 branch. I added all settings which were missing, must check if all of those exist in 2.6 branch. Obviously, the relevant ones are:
|
This was already merged to 2.6 branch. Should close this issue as soon as 2.6.7 is out. |
2.6.7 has been released which fixes this issue. |
Did this get pushed? I don't see 2.6.7 in Fedora 21? |
It's in updates-testing waiting for positive feedback: https://admin.fedoraproject.org/updates/FEDORA-2015-0039/cobbler-2.6.7-1.fc21 |
Ah, OK. I've grabbed it from there, thanks. |
Updated to 2.6.6 via yum. New settings file goes to settings.rpmnew. Without updating settings, cobblerd fails to start with:
Editing config.py to keep the original exception shows:
Adding the entries to settings fixes. Is there a way for the module to have a default value so we don't get an exception on load?
The text was updated successfully, but these errors were encountered: