Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
Changing CV of an existing host in the UI fails with "Executing dynflow action inside a transaction is not a good idea"
Version-Release number of selected component (if applicable):
Satellite 6.4 snap 12
How reproducible:
always
Steps to Reproduce:
1. have an existing content host subscribed to Library/default_org_view
2. in UI, go to hosts > all hosts > click edit next to the host
3. on the Host tab, change the content view setting to a different view
Actual results:
After submitting, an error box is displayed with: Oops, we're sorry but something went wrong Executing dynflow action inside a transaction is not a good idea
Expected results:
CV is updated as expected
Additional info:
Other host settings can be updated without complications
Closing as duplicate of 1566825, as it already track the ability to change CV in host. The error you provided should be gone once correct packages are pulled.
*** This bug has been marked as a duplicate of bug 1566825 ***