Greetings all,
I solved, well ---- I found what was causing the issue. The module;
*tfm-rubygem-foreman_chef
*is the problem. This is repeatable. Fresh installation; with these
two revisions; same condition.
For Katello 3.2 release; 0.4.2-1.fm1_14.el7 <---- this revision breaks
the system.
For Katello 3.3 release; 0.5.0-1.fm1_14.el7 <---- this revision breaks
the system.
Removing each latest revision and downgrading to 0.4.0-1.fm1_13.el7 will
fix the issue of *Executing dynflow action inside a transaction is not a
good idea *on Host Registration and Deletion.
# yum list tfm-rubygem-foreman_chef --showduplicates
Available Packages
tfm-rubygem-foreman_chef.noarch
0.4.0-1.fm1_13.el7
foreman-plugins
tfm-rubygem-foreman_chef.noarch
0.4.2-1.fm1_14.el7
foreman-plugins
tfm-rubygem-foreman_chef.noarch
0.5.0-1.fm1_14.el7
foreman-plugins
# yum remove tfm-rubygem-foreman_chef
# yumdownloader tfm-rubygem-foreman_chef-0.4.0-1.fm1_13.el7
# yum localinstall tfm-rubygem-foreman_chef-0.4.0-1.fm1_13.el7
# foreman-installer
Running foreman-installer rebuilds the apipie.cache; removing traces of the
previous module
Katello 3.2
Id: 2c40a3e6-c20b-4c86-af49-10daabbdec99
Label: Actions::Katello::Host::Register
Name: Register Host lpxxxxxxxxxxxxxxx.xxx.xxxxxxx.xxx
Owner: foreman_admin
Execution type: Delayed
Start at: 2017-02-12 05:16:51 UTC
Start before: -
Started at: 2017-02-12 05:16:51 UTC
Ended at: 2017-02-12 05:16:56 UTC
State: stopped
Result: success
Katello 3.3
Name: Register Host coruscant.xxxxxx.xxx
Result: success
Triggered by: xxxxxxx
Execution type: Immediate
Start at: about 9 hours ago
Started at: about 9 hours ago
Ended at: about 9 hours ago
Start before: -
On Sunday, February 12, 2017 at 6:42:45 AM UTC-5, Daniel Pratt wrote:
>
>
> Fresh install of Katello, 3.3 and 3.2 --- server completely configured,
> Unable to Register, and Delete Host.
>
> Actions::Katello::Host::Destroy
>
> Exception:
>
> RuntimeError: Executing dynflow action inside a transaction is not a good idea
>
> Backtrace:
>
> /opt/theforeman/tfm/root/usr/share/gems/gems/foreman-tasks-0.8.2/app/models/foreman_tasks/concerns/action_triggering.rb:145:in
> `ensure_not_in_transaction!'
> /opt/theforeman/tfm/root/usr/share/gems/gems/foreman-tasks-0.8.2/app/models/foreman_tasks/concerns/action_triggering.rb:132:in
> `dynflow_task_wrap'
> /opt/theforeman/tfm/root/usr/share/gems/gems/foreman-tasks-0.8.2/app/models/foreman_tasks/concerns/action_triggering.rb:37:in
> `destroy'
> /opt/theforeman/tfm/root/usr/share/gems/gems/katello-3.2.1.1/app/lib/actions/katello/host/destroy.rb:33:in
> `plan'
> ......snip.......
>
>
>
> Here's the attempt to register a host, and condition.
>
> ------
>
> Action:
>
> Actions::Katello::Host::Register
>
> Exception:
>
> RuntimeError: Executing dynflow action inside a transaction is not a good idea
>
> Backtrace:
>
> /opt/theforeman/tfm/root/usr/share/gems/gems/foreman-tasks-0.8.2/app/models/foreman_tasks/concerns/action_triggering.rb:145:in
> `ensure_not_in_transaction!'
> /opt/theforeman/tfm/root/usr/share/gems/gems/foreman-tasks-0.8.2/app/models/foreman_tasks/concerns/action_triggering.rb:132:in
> `dynflow_task_wrap'
> /opt/theforeman/tfm/root/usr/share/gems/gems/foreman-tasks-0.8.2/app/models/foreman_tasks/concerns/action_triggering.rb:33:in
> `save!'
> /opt/theforeman/tfm/root/usr/share/gems/gems/katello-3.2.1.1/app/lib/actions/katello/host/register.rb:10:in
> `block in plan'
> ..... snip.........
>
>
--
You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.
