As part of Linux hardening, my blpackage removes an entry for /etc/inittab and adds another.
This always rolls back without problem.
I think I usually use the generic grammar file.
Generic grammar seems to work fine for me too. It is when I use httpd.conf grammar and machine config.xml. I am attaching the two files I am having trouble with.
I challenge anyone to make an update using a BLPackage and successfully undo. As a reward I will send you a Napoleon Dynamite sound clip.
UPDATE: Based on File attachment policies, a file was removed, see FAQ for more
I think I might be happier without that sound clip....
Then again... who's Napoleon Dynamite? Is he related to Miss Dynamite?
Actually, that was the /etc/inittab grammar file... O_o
He's my hero. I hear he's got BladeLogic skills too.
You'd need to use one of the hierarchical grammar types, since they will ensure that a node is placed in the right section. If you just used a generic or inittab grarmmar, it would/could easily just drop changes at the end of the file. It has no sense of parent and child nodes.
I'll give this one a peek tonight if I get a chance. How exactly does it fail? Does the job fail? Or does it say that it succeeds but makes improper rollback changes?
For the first one I used the Machine Config XML grammar, and for the second I used the httpd.conf grammar.
What I am doing is packing an entry as a BLPackage, modifying it, deploying it (up until this point it works fine), and then doing an undo on the deploy. Then it fails saying it can't find the entry anymore. I'm not modifying the name of the entry either, just one of the values on the line. So I don't understand why the transaction set isn't remembering what it's doing.
Support has reproduced the bug and sent it to engineering.
Where are all the Buckaroo Banzai fans nowadays?
I worked a ticket recently for Mark Jeffery which came into this error. It was related to using the fstab file and the fstab grammar. We ran into the same rollback issue you noted... It was logged as a defect to engineering. Log a ticket for it and I'll attach it to the existing defect if you wish.