add one note in FAQ rename helm package

source/user_guide/FAQ_user.rst

@@ -225,6 +225,14 @@ Add the dependenciesin the ``Dockerfile`` file like bellow :
 How to upgrade my helm dependency / I can't enable a feature 
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
+.. |img1| image:: /_static/delete-example.png
+  :height: 3em
+.. note::
+
+  Don't forget to stop the current deployed instance by clicking on |img1| pipeline's step before apply the changes.
+
+
+
 Basic use case is that the doc mention a feature, you enable it in values.yaml, but don't see the effect. 
 The cause can be that you don't use latest version of the helm package, the part of the toolkit which provide feature such as storage, nodowntime, ... 
 
@@ -315,3 +323,20 @@ Here after is what your git diff should look like : changes in values.yaml, Char
       autoscaling:
         enabled: false
       nodowntime:
+
+
+How to fix error "UPGRADE FAILED: failed to create resource" ?
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+If, after upgrade my helm dependency by changing name of helm package, you obtain the following error in the "deploy" pipeline step : 
+
+.. image:: /_static/error_upgrade_failed.png
+  :align: center
+
+.. code-block:: bash
+
+    Error: UPGRADE FAILED: failed to create resource: admission webhook "validate.nginx.ingress.kubernetes.io" denied the request: host "XXXXXX.dev.pasteur.cloud" and path "/" is already defined in ingress XXXXX/XXXX
+
+.. |img2| image:: /_static/deploy_in_dev_failed.png
+  :height: 3em
+You have just forget to stop previously the running instance. Click on |img1| pipeline's step and on |img2| to deploy again.
\ No newline at end of file