RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 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 "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". 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 "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-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 985960 - firewalld hang on yum update
Summary: firewalld hang on yum update
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: firewalld
Version: 7.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Thomas Woerner
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-07-18 15:20 UTC by Richard W.M. Jones
Modified: 2013-10-02 13:41 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-10-02 13:41:01 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Richard W.M. Jones 2013-07-18 15:20:30 UTC
Description of problem:

# yum update
[...]
  Cleanup    : glibmm24-devel-2.36.2-1.el7.x86_64                      590/1102 
  Cleanup    : perl-IO-Socket-IP-0.19-1.el7.noarch                     591/1102 
  Cleanup    : perl-ExtUtils-Manifest-1.61-240.el7.noarch              592/1102 
  Cleanup    : sos-2.2-34.el7.noarch                                   593/1102 
  Cleanup    : dyninst-8.1.1-1.el7.x86_64                              594/1102 
  Cleanup    : python-devel-2.7.4-2.el7.x86_64                         595/1102 
  Cleanup    : libvirt-devel-1.0.6-1.el7.x86_64                        596/1102 
  Cleanup    : libXtst-devel-1.2.1-5.el7.x86_64                        597/1102 
  Cleanup    : abrt-addon-vmcore-2.1.3-2.el7.x86_64                    598/1102 
  Cleanup    : firewall-config-0.3.1-1.el7.noarch                      599/1102 
  Cleanup    : firewalld-0.3.1-1.el7.noarch                            600/1102 

# then it hung here, nothing was happening according to 'top'

^Z
[1]+  Stopped                 sudo yum update
rjones@builder-rhel7:~$ fg
sudo yum update
  Cleanup    : augeas-devel-1.0.0-2.el7.x86_64                         601/1102 
  Cleanup    : libxml2-devel-2.9.0-4.el7.x86_64                        602/1102 
  Cleanup    : perl-XML-Writer-0.612-5.el7.noarch                      603/1102 

# it continued fine after ^Z + fg

Version-Release number of selected component (if applicable):

Upgrading from firewalld 0.3.1-1.el7 -> 0.3.3-2.el7.

How reproducible:

Don't know, and don't ask me to try.

Steps to Reproduce:

Unclear, but at a guess:
1. Install firewalld 0.3.1-1.el7
2. yum update to firewalld 0.3.3-2.el7
3.

Actual results:

Hangs during cleanup of the old package.

Expected results:

Should not hang.

Additional info:

Running RHEL 7 in a VM.

Comment 3 Richard W.M. Jones 2013-10-02 13:41:01 UTC
I don't have any more information than what is in comment 0.


Note You need to log in before you can comment on or make changes to this bug.