Modify

Ticket #9 (closed defect: fixed)

Opened 14 years ago

Last modified 13 years ago

Traceback from a Postinstall

Reported by: leggett@… Owned by: desai
Priority: minor Milestone: Bcfg2 0.8.1 Release
Component: bcfg2-client Version:
Keywords: Cc:

Description

This confuses me since the Postinstall is acutally commented out, but I get this:

[root@nmpdr-anno-1:/fc/qlafc-linux-8.01.01-1-install]$ /usr/sbin/bcfg2 -q -n Failure in Verify for entry: <Postinstall name="/sbin/new-kernel-pkg --package kernel --mkinitrd --depmod --install uname -r"/> File /usr/lib/python2.3/site-packages/Bcfg2/Client/Toolset.py, line 263, in VerifyEntry?

method = getattr(self, "Verify%s" % (entry.tag))

exceptions.AttributeError?: 'ToolsetImpl?' object has no attribute 'VerifyPostinstall?'

/usr/lib/python2.3/site-packages/Bcfg2/Client/Toolset.py:215: FutureWarning?: %u/%o/%x/%X of negative int will return a signed string in Python 2.4 and up

print "State verify evidently failed for %s" % (msg)

State verify evidently failed for <Element Postinstall at b7ca4488>

With this bundle: <Bundle name="qlogic-fc" version="2.0">

<System name="rh">

<!-- modprobe.conf needs some work for it to work right <ConfigFile? name="/etc/modprobe.conf"/> --> <Package name="qla2xxx"/> <Package name="scli"/> <!-- <Postinstall name="/sbin/new-kernel-pkg --package kernel --mkinitrd --depmod --install uname -r"/> -->

</System>

</Bundle>

Attachments

Change History

comment:1 Changed 14 years ago by desai

  • Milestone set to Bcfg2 0.8.1 Release

comment:2 Changed 14 years ago by leggett@…

  • Priority changed from major to minor

The problem was two-fold. I had misspelled PostInstall? (forgot the capital "i"). Then, when I commented out the line the XML parser got confused since there were now '--' in the comment. Replacing these with the HTML escaped representation, &#45;&#45;, fixed that problem. Obviously, it would be nice to include double dashes in comments. Double dashes in a non-commented out line pose no problem.

comment:3 Changed 14 years ago by desai

  • Status changed from new to assigned

comment:4 Changed 14 years ago by desai

  • Status changed from assigned to closed
  • Resolution set to fixed

OK. It sounds like there is an issue with xml parseability as well, but I doubt there is much we can do about it other than documentation. I am going to close this one out.

WARNING! You need to establish a session before you can create or edit tickets. Otherwise the ticket will get treated as spam.

View

Add a comment

Modify Ticket

Change Properties
<Author field>
Action
as closed
The resolution will be deleted. Next status will be 'reopened'
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.