Ticket #971 (closed defect: invalid)

Opened 12 years ago

Last modified 9 years ago

TGenshi plugin not binding on altsrced entry

Reported by: Owned by: desai
Priority: major Milestone: Bcfg2 1.2.0 Release
Component: bcfg2-server Version: 1.0
Keywords: Cc:


Given the following abstract Path entry:

<Path name='/etc/somefile.conf' altsrc='/etc/somefile-template'/>

And the following correctly-located TGenshi template file:


I would expect that /etc/somefile.conf on the client would be created with the TGenshi-parsed contents of {repo}/TGenshi/etc/somefile-template/template.newtxt on the server. However, the TGenshi plugin doesn't seem to want to bind to the altsrc template file. Instead, I'm getting the following error on the client side:

Entry Path:/etc/somefile.conf reports bind failure: no matching generator

And the following errors on the server side:

Failed binding entry Path:/etc/somefile.conf with altsrc None
Falling back to Path:/etc/somefile.conf
Failed to bind entry: Path /etc/somefile.conf

Based on that first message, I'd assume one of two things: either (a) the altsrc attribute isn't being read correctly (which seems unlikely), or (b) the TGenshi plugin isn't properly detecting that it's got a template that can fulfill the altsrc path. Unfortunately I'm a bit of a newbie on the inner workings of bcfg2, so that's as far as I got.

Other important information:

  • I discussed this with solj and m4z on #bcfg2 on freenode earlier today (2010-12-16, around 9:50am); there may be additional useful context there.
  • I'm running bcfg2 version "1.1.1-1~lucid1" from the alternate apt sources specified in the Ubuntu quickstart.


Change History

comment:1 Changed 12 years ago by

Determined that TGenshi's failure to bind had something to do with a syntax error in my template file. However, for some reason I wasn't getting any notices to that effect in the bcfg2-server logs. That would be a different issue, though; as it stands, the bug as I described it most likely isn't a bug at all.

comment:2 Changed 12 years ago by solj

  • Status changed from new to closed
  • Resolution set to invalid

Closing this for now. It'd be nice to know why you aren't getting the Genshi error during the templating phase. If you figure out the problem, I'd like to hear about it.

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


Add a comment

Modify Ticket

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

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

Note: See TracTickets for help on using tickets.