[BUG] Transactional update module prevents sls execution about salt

[rdouman]

Hi Pablo I appreciate the response, I'll try the work around mentioned above ASAP. We first experienced this issue after upgrading from 3004 to 3005.

…

On Mon, 15 May 2023 at 17:43, Pablo Suárez Hernández < ***@***.***> wrote: I did some tests around this and I was able to replicate the issue. Not yet sure if this is related with the upgrade to Salt 3005.1 / 3006.0, or with the Python 3.10 version. Apparentely there is a kind of mess with LazyLoader imports, ending up with a wrong importing of the transactional_update execution module into the LazyLoader, exposing the functions under state.* instead of transactional_update.*. I've not identified yet the root cause but I was able to workaround the issue using this patch in the minion side: diff --git a/salt/modules/transactional_update.py b/salt/modules/transactional_update.py index 6493966782..658ebccc6b 100644--- a/salt/modules/transactional_update.py+++ b/salt/modules/transactional_update.py@@ -285,6 +285,8 @@ from salt.modules.state import _check_queue, _prior_running_states, _wait, runni __func_alias__ = {"apply_": "apply"} +__virtualname__ = "transactional_update"+ log = logging.getLogger(__name__) @@ -300,7 +302,7 @@ def __virtual__(): _prior_running_states, globals() ) running = salt.utils.functools.namespaced_function(running, globals())- return True+ return __virtualname__ else: return (False, "Module transactional_update requires a transactional system") — Reply to this email directly, view it on GitHub <#575 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAYR4FNBMSDTWAYLDOJVUSLXGJFKPANCNFSM6AAAAAAUMEVME4> . You are receiving this because you authored the thread.Message ID: ***@***.***>

-- R Douman Albert Einstein "There are two ways to live your life - one is as though nothing is a miracle, the other is as though everything is a miracle."

[rdouman]

Hi all,

I'm seeing more of this issue pop up on the internet, with no solution insight. Any idea when this will get priority ?

[rdouman]

This bug seems to be related to saltstack/salt#59690

[meaksh]

I did some tests around this and I was able to replicate the issue. Not yet sure if this is related with the upgrade to Salt 3005.1 / 3006.0, or with the Python 3.10 version.

Apparentely there is a kind of mess with LazyLoader imports, ending up with a wrong importing of the transactional_update execution module into the LazyLoader, exposing the functions under state.* instead of transactional_update.*.

I've not identified yet the root cause but I was able to workaround the issue using this patch in the minion side:

diff --git a/salt/modules/transactional_update.py b/salt/modules/transactional_update.py
index 6493966782..658ebccc6b 100644
--- a/salt/modules/transactional_update.py
+++ b/salt/modules/transactional_update.py
@@ -285,6 +285,8 @@ from salt.modules.state import _check_queue, _prior_running_states, _wait, runni
 
 __func_alias__ = {"apply_": "apply"}
 
+__virtualname__ = "transactional_update"
+
 log = logging.getLogger(__name__)
 
 
@@ -300,7 +302,7 @@ def __virtual__():
             _prior_running_states, globals()
         )
         running = salt.utils.functools.namespaced_function(running, globals())
-        return True
+        return __virtualname__
     else:
         return (False, "Module transactional_update requires a transactional system")