RDO tickets are now tracked in Jira https://issues.redhat.com/projects/RDO/issues/
Bug 1148426 - Using the Juno RDO packstack --allinone fails trying to remove firewalld-0.3.11-3.fc20.noarch
Summary: Using the Juno RDO packstack --allinone fails trying to remove firewalld-0.3....
Keywords:
Status: CLOSED DUPLICATE of bug 1148399
Alias: None
Product: RDO
Classification: Community
Component: openstack-puppet-modules
Version: unspecified
Hardware: Unspecified
OS: Linux
unspecified
unspecified
Target Milestone: Milestone3
: Juno
Assignee: Ivan Chavero
QA Contact: Ami Jeain
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-10-01 12:39 UTC by Sean Toner
Modified: 2014-10-24 05:39 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-10-23 18:58:11 UTC
Embargoed:


Attachments (Terms of Use)

Description Sean Toner 2014-10-01 12:39:25 UTC
Description of problem
======================

This is on a fedora 20 system having just run yum update, and after installing the Juno RDO rpm (http://rdo.fedorapeople.org/openstack-juno/rdo-release-juno.rpm).  

While running packstack --allinone, it fails while trying to remove the firewalld-0.3.11-3.fc20.noarch rpm.  This is because anaconda has a dependency on firewalld.  The log from puppet:

1;31mError: /Stage[main]/Firewall::Linux::Redhat/Package[firewalld]/ensure: change from 0.3.11-3.fc20 to absent failed: Execution of '/usr/bin/rpm -e firewalld-0.3.11-3.fc20.noarch' returned 1: error: Failed dependencies:
        firewalld >= 0.3.5-1 is needed by (installed) anaconda-20.25.16-1.fc20.x86_64
        firewalld = 0.3.11-3.fc20 is needed by (installed) firewall-config-0.3.11-3.fc20.noarch

I can manually work around this by issuing `yum remove firewalld` which will remove the anaconda dependency as well


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

packstack Juno 2014.2.dev1266.g63d9c50


How reproducible
================


Steps to Reproduce
==================

1. Install Fedora 20
2. yum update 
3. yum groupinstall "KDE Plasma Workspaces"
4. sudo yum install http://rdo.fedorapeople.org/openstack-juno/rdo-release-juno.rpm
5. sudo yum install -y openstack-packstack
6. packstack --allinone

Actual results
==============

Errors:

Copying Puppet modules and manifests                 [ DONE ]
Applying 192.168.122.48_prescript.pp
192.168.122.48_prescript.pp:                      [ ERROR ]            
Applying Puppet manifests                         [ ERROR ]

ERROR : Error appeared during Puppet run: 192.168.122.48_prescript.pp
Error: Execution of '/usr/bin/rpm -e firewalld-0.3.11-3.fc20.noarch' returned 1: error: Failed dependencies:
You will find full trace in log /var/tmp/packstack/20141001-080818-TOTPkh/manifests/192.168.122.48_prescript.pp.log

Expected results:


Additional info:

Comment 2 Rich Bowen 2014-10-01 16:03:37 UTC
I am experiencing this same problem on CentOS7

Comment 3 Alan Pevec 2014-10-01 20:30:52 UTC
> Error: /Stage[main]/Firewall::Linux::Redhat/Package[firewalld]/ensure:
> change from 0.3.11-3.fc20 to absent failed: Execution of '/usr/bin/rpm -e
> firewalld-0.3.11-3.fc20.noarch' returned 1: error: Failed dependencies:
>         firewalld >= 0.3.5-1 is needed by (installed)
> anaconda-20.25.16-1.fc20.x86_64
>         firewalld = 0.3.11-3.fc20 is needed by (installed)
> firewall-config-0.3.11-3.fc20.noarch

So this is in puppet firewall module, Packstack just disables firewalld in templates/prescript.pp:
service { "firewalld":
  ensure => "stopped",
  enable => false,
  before => Service['iptables'],
}

I'm not sure why is puppet module going for nuclear option.

> I can manually work around this by issuing `yum remove firewalld` which will
> remove the anaconda dependency as well

That's a general issue with RPM handling in puppet package provider, AFAICT it tries to be RPM-distro agnostic by using rpm as the common lowest-level tool but that fails miserably like here due to dependencies or that it doesn't handle provides...

Comment 4 Alan Pevec 2014-10-01 20:42:06 UTC
> I'm not sure why is puppet module going for nuclear option.

It's from
https://github.com/puppetlabs/puppetlabs-firewall/commit/ad961d79e433bf65ca8ff42bad89d00f6d127436

Lars, I saw you worked on puppetlabs-firewall, do you know why is firewalld _package removal_ required?
Isn't firewalld service disabling like in Packstack enough?

Comment 5 Lars Kellogg-Stedman 2014-10-01 20:48:56 UTC
I think that simply disabling it may lead to unexpected problems if someone were to accidentally enable it, or run it, or whatever.  We get enough firewall-related problem reports as it is.

It's not something I feel strongly about, though.

Comment 6 fbayhan 2014-10-02 10:40:02 UTC
(In reply to Rich Bowen from comment #2)
> I am experiencing this same problem on CentOS7

me too.

Workaround solution.

sudo yum remove firewalld

Then re-run packstack with the same answer file.

packstack --answer-file=<generated packstack file>

Comment 7 Mike Ruckman 2014-10-02 16:22:49 UTC
Same thing on F21.

Pastes of logs:
prescript.pp.log - http://paste.fedoraproject.org/138578/22663401/
setup.log - http://paste.fedoraproject.org/138577/14122663/
stdout - http://paste.fedoraproject.org/138585/22667921/

Comment 8 wes hayutin 2014-10-17 19:51:59 UTC
recreated on f21..

Comment 9 Alan Pevec 2014-10-23 18:58:11 UTC

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


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