Bug 1526749

Summary: Turning maintenance mode ON/OFF can be better done by the tool itself.
Product: Red Hat Satellite Reporter: Ashish Humbe <ahumbe>
Component: Satellite MaintainAssignee: Anurag Patel <apatel>
Status: CLOSED DUPLICATE QA Contact: Katello QA List <katello-qa-list>
Severity: medium Docs Contact:
Priority: high    
Version: 6.3.0CC: apatel, inecas, kgaikwad, sabnave
Target Milestone: UnspecifiedKeywords: Triaged
Target Release: Unused   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-01-10 13:53:26 UTC Type: Bug
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:    
Bug Blocks: 1496794    

Description Ashish Humbe 2017-12-17 06:35:21 UTC 
Description of problem:

If the firewall rules are flushed by the user then custom chain set by foreman-maintain (FOREMAN_MAINTAIN) will be deleted and upgrade through foreman-maintain fails since we could not turn off maintenance mode successfully.

Running Procedures after migrating to Satellite 6.2.z
================================================================================
katello-service start: 
/ No katello service to start                                         [OK]      
--------------------------------------------------------------------------------
Turn off maintenance mode:                                            [FAIL]
Failed executing iptables -D INPUT -j FOREMAN_MAINTAIN, exit status 1:
 iptables: No chain/target/match by that name.
--------------------------------------------------------------------------------
Scenario [Procedures after migrating to Satellite 6.2.z] failed.

The following steps ended up in failing state:

  [maintenance-mode-disable]


Additional Info: 
This bz is created with the reference of: https://bugzilla.redhat.com/show_bug.cgi?id=1524279#c3 to track different issues in different bz.
Comment 2 Anurag Patel 2018-01-10 13:53:26 UTC 
Tracking this in: https://bugzilla.redhat.com/show_bug.cgi?id=1487559

*** This bug has been marked as a duplicate of bug 1487559 ***