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.

Bug 1426398

Summary: World invalidation can fail, when execution plans are missing
Product: Red Hat Satellite Reporter: Satellite Program <pm-sat>
Component: Tasks PluginAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED ERRATA QA Contact: Adam Ruzicka <aruzicka>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.2.0CC: aruzicka, bbuckingham, bkearney, ehelms, inecas, jberry86, jcallaha, pierre-yves.goubet, pmoravec, vgunasek, will_darton
Target Milestone: UnspecifiedKeywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1390931 Environment:
Last Closed: 2018-02-21 16:51:07 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1390931    
Bug Blocks:    

Comment 2 Adam Ruzicka 2017-08-23 08:08:43 UTC
Verified.
Version Tested: Satellite-6.3 Snap 12

Package versions:
satellite-6.3.0-16.0.beta.el7sat.noarch
tfm-rubygem-dynflow-0.8.24-1.fm1_15.el7sat.noarch

Followed steps described in #1, the execution plan with missing data was skipped and the world was invalidated properly.

2017-08-23 07:55:58  [foreman-tasks/dynflow] [E] Could not load execution plan 873dce4a-b7aa-4f00-971d-269d9e151974
2017-08-23 07:55:58  [foreman-tasks/dynflow] [E] Could not load steps for execution plan 873dce4a-b7aa-4f00-971d-269d9e151974 (Dynflow::Errors::DataConsistencyError)
 | /opt/theforeman/tfm/root/usr/share/gems/gems/dynflow-0.8.24/lib/dynflow/execution_plan.rb:498:in `block in steps_from_hash'
 | /opt/theforeman/tfm/root/usr/share/gems/gems/dynflow-0.8.24/lib/dynflow/execution_plan.rb:495:in `each'
 | /opt/theforeman/tfm/root/usr/share/gems/gems/dynflow-0.8.24/lib/dynflow/execution_plan.rb:495:in `inject'
 | /opt/theforeman/tfm/root/usr/share/gems/gems/dynflow-0.8.24/lib/dynflow/execution_plan.rb:495:in `steps_from_hash'
 | /opt/theforeman/tfm/root/usr/share/gems/gems/dynflow-0.8.24/lib/dynflow/execution_plan.rb:401:in `new_from_hash'

-----B<------------------------------------------------------------B<-----
                      Trace snipped, goes on for a while
-----B<------------------------------------------------------------B<-----

2017-08-23 07:55:58  [foreman-tasks/dynflow] [E] invalid plan 873dce4a-b7aa-4f00-971d-269d9e151974, skipping
2017-08-23 07:55:58  [foreman-tasks/dynflow] [E] invalid worlds found {"ed40b539-917e-4cfc-89d3-9670b4274edf"=>:invalidated, "2561ef2f-a8ef-47f9-b148-7039db39f005"=>:valid}

Comment 3 Satellite Program 2018-02-21 16:51:07 UTC
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA.
> 
> For information on the advisory, and where to find the updated files, follow the link below.
> 
> If the solution does not work for you, open a new bug report.
> 
> https://access.redhat.com/errata/RHSA-2018:0336