-
Beniamino Galvani authored
When a master connection is deactivated by user, we set the autoconnect-blocked reason 'user-request' for the connection and we propagate the same reason to slaves. Doing so prevents the autoactivation of slaves when the master is manually activated again, because the only way to override the 'user-request' blocked reason is through manual activation of slaves. Instead what should happen is that the manual deactivation of a master marks slaves as blocked for failed dependencies. When the master becomes available again, slaves can autoactivate if the profile allows it. https://bugzilla.redhat.com/show_bug.cgi?id=1437598
b31118cf