Bug 443454
Summary: | python errors when cobbler sync command is run | ||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Tim McConnell <timothy.mcconnell> | ||||||||||||||
Component: | cobbler | Assignee: | Michael DeHaan <mdehaan> | ||||||||||||||
Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||||||
Severity: | low | Docs Contact: | |||||||||||||||
Priority: | low | ||||||||||||||||
Version: | 8 | ||||||||||||||||
Target Milestone: | --- | ||||||||||||||||
Target Release: | --- | ||||||||||||||||
Hardware: | i686 | ||||||||||||||||
OS: | Linux | ||||||||||||||||
Whiteboard: | |||||||||||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||||||||||
Doc Text: | Story Points: | --- | |||||||||||||||
Clone Of: | Environment: | ||||||||||||||||
Last Closed: | 2008-04-21 21:03:33 UTC | Type: | --- | ||||||||||||||
Regression: | --- | Mount Type: | --- | ||||||||||||||
Documentation: | --- | CRM: | |||||||||||||||
Verified Versions: | Category: | --- | |||||||||||||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||||||
Cloudforms Team: | --- | Target Upstream Version: | |||||||||||||||
Embargoed: | |||||||||||||||||
Attachments: |
|
Description
Tim McConnell
2008-04-21 16:50:06 UTC
You did not specifiy a version above. What does "rpm -q cobbler" give you? It looks like you've somehow broken your save files in /var/lib/cobbler. You will probably want to remove them and try again. Without knowing how they got in this state I'm not sure what can be done. Hand-editing is the most likely cause, but it could be that you've managed to feed the cobbler command line or web app some data it doesn't like. That's the kind of data I need to find out what we would need to filter against. A stock "cobbler sync" does not throw this error. please reply to tmcconnell (In reply to comment #1) > You did not specifiy a version above. What does "rpm -q cobbler" give you? cobbler-0.8.3-3.fc8 > It looks like you've somehow broken your save files in /var/lib/cobbler. You > will probably want to remove them and try again. > > Without knowing how they got in this state I'm not sure what can be done. > > Hand-editing is the most likely cause, but it could be that you've managed to > feed the cobbler command line or web app some data it doesn't like. That's the > kind of data I need to find out what we would need to filter against. > > A stock "cobbler sync" does not throw this error. > > Okay Hand editing the /etc/dhcpd.conf file is a no no so how do you make cobbler "manage DHCP" ? (In reply to comment #1) > You did not specifiy a version above. What does "rpm -q cobbler" give you? cobbler-0.8.3-3.fc8 > It looks like you've somehow broken your save files in /var/lib/cobbler. You > will probably want to remove them and try again. > > Without knowing how they got in this state I'm not sure what can be done. > > Hand-editing is the most likely cause, but it could be that you've managed to > feed the cobbler command line or web app some data it doesn't like. That's the > kind of data I need to find out what we would need to filter against. > > A stock "cobbler sync" does not throw this error. > > Okay Hand editing the /etc/dhcpd.conf file is a no no so how do you make cobbler "manage DHCP" ? Hand editing the DHCP file is quite sane, hand editing /var/lib/cobbler/distros, profiles, or systems is not. Did you do any of that? It could also be that you have a problem with the syntax of your settings file as well, perhaps maybe there's an extra space after the "1" where you turned on manage_dhcp ? Attach the settings file and your other config files and I can perhaps take a look at them to see where the problem lies. (To clarify, the file you should be editing when using DHCP management is /etc/cobbler/dhcp.template, which cobbler uses to render /etc/dhcpd.conf) Created attachment 303172 [details]
default cobbler kickstart file
was edited to get the correct pxe ks file for our uses
Created attachment 303175 [details]
dhcpd.conf
cobbler needs to use these settings for our PXE server
Created attachment 303177 [details]
Settings for cobbler
The only other cobbler file I tried to edit besides th default kickstart file.
Thanks for the attaching the settings file, the other two files are not going to be problems, as the error is a YAML parsing error. The files I need to see are: /var/lib/cobbler/distros /var/lib/cobbler/profiles /var/lib/cobbler/systems If you didn't hand edit them, it's still possible the command line was GIGO'd somehow, and that may help me understand what data got inserted in that it can't read back. Thanks! Created attachment 303188 [details]
distros
Created attachment 303189 [details]
/profiles
/profiles
Created attachment 303190 [details]
/systems
/systems
none of which I have edited I can't reproduce the error with any of the attached files. Looking over the information again, the error does end with this: """ YamlLoaderException: bad key for map: near line 19: manage_dhcp 0 """ In which case it looks like you are missing a colon between manage_dhcp and the 0, yet this is the not the same as the file you emailed. Possibly not the same file? Let me check something OK in the one I uploaded to the site it has multiple manage_dhcp entries, I removed an re installed cobbler and the new file only has one manage_dhcp entries. maybe the multiple entries are the problem? Possible. The lack of the colon is also a problem. Either way, sounds like you are fixed. I'm probably going to look for some way to migrate the new installs away from the slightly confusing YAML syntax for that one config file in a later version. ok thanks for the help For future reference, a couple of faster ways to get help: (A) IRC -- #cobbler on irc.freenode.net (A) the mailing list, et-mgmt-tools -- subscription required -- https://www.redhat.com/archives/et-mgmt-tools/ Bugzilla is of course fine, but this saves the trouble of filling out the various fields and allows for other people to answer, so you might have your problem resolved more quickly. Generally I primarily use Trac for keeping track [sic] of Cobbler items -- https://fedorahosted.org/cobbler where you can find an account at https://admin.fedoraproject.org/accounts |