Forum Discussion

npmaslow_68104's avatar
npmaslow_68104
Historic F5 Account
Jun 01, 2009

Potential v10 Compatibility Issue

PROBLEM DESCRIPTION:

 

Expected behavior - Irule editor should be able to update irules without issue.

 

Actual Behavior - LTM logs an error message in /var/log/ltm when you make changes to an irule using the Windows client/editor. There is also potential that sometimes 'Save' does not update all irules edited during that session. This has only been partially reproducted in that only the 'highlighted' or 'presently active' irule appears to be saved sometimes in my testing, though it is still something to consider.

 

 

STEPS TO REPRODUCE:

 

Use irule editor to connect to a v10 LTM.

 

Create irule

 

Modify that irule, save changes

 

View the /var/log/ltm file on the unit. It should record the following error: May 27 07:34:48 local/bigipcobaltqeda2 err mcpd[1968]: 01020066:3: The requested rule (DTS-CobaltIGSelection) already exists in partition Common.

 

Create a second irule.

 

Save it.

 

Make changes to both irules.

 

Hit save.

 

Potentially only one of the two irules will be updated. <-- this is less common than the logging bit, which always occurs.
application delivery
devops
irule editor
iRules

6 Replies

Sort By
  • Joe_Pruitt's avatar
    Joe_Pruitt
    Jun 01, 2009
    I just performed the following on my v10.0.1 system

     

     

    1. Create an iRule (a_test).

     

    2. Click Save.

     

    At this point nothing is in my log and the iRule has been saved.

     

     

    3. Create a second iRule

     

    4. Click Save

     

    This iRule is saved as well with no errors in the log.

     

     

    5. Make changes to both iRules

     

    6. Click Save

     

    This saves the currently selected iRule.

     

     

    7. Click "File.Save All"

     

    This saves all modified iRules.

     

     

    With regards to your log error, are you creating an iRule with the same name as one that already exists on your system? You are implying that your iRule was saved since you tried to save it again later. Is the log error include the name of the iRule you are creating (ie. DTS-CobaltIGSelection) or is it the same error regardless of the iRule you are trying to save?

     

     

    What is your partition setup? Are you working in the Common Partition or a separately created one?

     

     

    Also, have you tried creating the same iRule name and contents in the GUI and looked in the logs for this error? The iRule Editor is just a wrapper around the iControl interfaces and then into the mcpd database so if you are seeing this error, it would likely be seen in the GUI and CLI as well. If you could verify that it's working there but only not with the Editor, that may help narrow things down a bit.

     

     

    -Joe

     

  • npmaslow_68104's avatar
    npmaslow_68104
    Historic F5 Account
    Jun 02, 2009
    Thanks for the reply.

     

     

    The log message only occurs if an already existing irule is modified using the irules editor client. (I just went through the step of creating it in the example as well for completeness)

     

     

    The log message will occur if there is only one partition (common) on the system. The test system that I used had only a base install on it. No other configuration elements other than the irule and a test standard vip/pool.

     

     

    The message does not occur if the irule is modified via the webgui or cli.
  • JRahm's avatar
    JRahm
    Icon for Admin rankAdmin
    Jun 02, 2009
    I saw the same behavior on my 10.0 HF1 & HF2 systems.
  • npmaslow_68104's avatar
    npmaslow_68104
    Historic F5 Account
    Jun 09, 2009
    This also occurs under 10.0.1 in my testing, so it is not just 10.0.0 as originally indicated.
  • Joe_Pruitt's avatar
    Joe_Pruitt
    Jun 15, 2009
    Just found the issue. This is an editor "feature" in the way it creates temporary iRules to do syntax checking. Prior to v10 I don't believe this was logged but it looks like it is now. The iRules should be saved but you will get this error message in your log during the validation process. I will look for a fix but rest assured that your iRules are getting saved.

     

     

    -Joe