Source template has changed - post upgrade to 11.4.1

Hi Fred, I have reviewed your clarification but that does not reveal the step by step process to make it dis appear. My worry is, if there is no way , or do we have to upgrade it again, means, mine is production system. I have to show some process or steps to make it clear that ... XYZ is reason... and 1.2.3.4.5.... are the steps to correct it.

The yellow triangle is a reflection of the "sys application service template-modified" field in tmsh. This is not user-modifiable. In answering your question, I am not sure which concern have when working with a production system. (1) You could be concerned that re-running the iApp would interrupt traffic. It should not. iApps do not delete and create config from scratch, but rather deploy specific changes. If you make no changes to the iApp, and simply re-run it, then no changes are made to config and traffic flows normally. The system will change "template-modified" from "yes" to "no" after the iApp is re-executed, either via tmsh or the UI, and the yellow triangle will go away. (2) You could also be concerned that the iApp code was somehow changed, and re-running it could change the config, thereby disrupting traffic. If this is the case, you basically want to freeze your config to stop anyone from running the iApp, which you can do by re-parenting the iApp to template = none (click "change" on the re-configure page in the UI, or use the tmsh command "modify sys application service myapp.app/myapp template none"). Once the iApp's parent template is re-assigned, the yellow triangle will go away. (3) You could have some concerns about touching a production config, but still want to retain the ability to use the iApp in the future. Two options there: either (a) re-parent the iApp to template "none" for now, and re-parent it back when you want to make changes, or (b) make re-running the iApp part of your procedures during the outage window when upgrading BIG-IP.

In case you are managing multiple systems, I should mention that any of the above steps can also be accomplished via SOAP or REST.