Project

General

Profile

Actions

Bug #26905

closed

katello nightly installation fails due conflict with mongodb package from epel repo

Added by roman plevka over 5 years ago. Updated over 5 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
foreman-installer script
Target version:
-
Difficulty:
Triaged:
Yes
Fixed in Releases:
Found in Releases:

Description

When trying to install katello nightly (with epel repos):
there is a stage that fails on trying to install mongodb-client:

/Stage[main]/Mongodb::Client/Package[mongodb_client]/ensure: change from 'purged' to 'present' failed
...
Error: rh-mongodb34-mongodb-syspaths conflicts with mongodb-2.6.12-6.el7.x86_6

the issue seems to be with the following module:
/usr/share/foreman-installer/modules/mongodb/manifests/client.pp

this error won't crash the installer, It actually finishes with: "success".

reproducer:
- enable satellite maintenance repo
- get forklift
- ansible-playbook c local -i,$(hostname) -e katello_version=nightly -e foreman_installer_skip_installer=True playbooks/katello.yml
run katello installer:

```
foreman-installer --scenario katello -v\
--foreman-initial-admin-password="changeme" \
--disable-system-checks \
--foreman-proxy-dns="true" \
--foreman-proxy-dns-interface="eth0" \
--foreman-proxy-dns-zone="foo.com" \
--foreman-proxy-dhcp="true" \
--foreman-proxy-dhcp-interface="eth0" \
--foreman-proxy-tftp="true" \
--foreman-proxy-tftp-servername="qe-foreman-rhel7.foo.com" \
--foreman-proxy-register-in-foreman="true" \
--foreman-proxy-puppetca="true" \
--foreman-proxy-puppet="true" \
--foreman-proxy-dhcp-range="10.8.213.10 10.8.213.250" \
--foreman-proxy-dhcp-gateway="10.8.213.254"\
--foreman-proxy-dns-reverse="213.8.10.in-addr.arpa" \
--katello-proxy-url="http://proxy.foo.com" \
--katello-proxy-port="3128" --katello-proxy-username="admin" \
--katello-proxy-password="redhat" \
--enable-foreman-plugin-remote-execution \
--enable-foreman-proxy-plugin-remote-execution-ssh \
--enable-foreman-plugin-discovery \
--enable-foreman-proxy-plugin-discovery \
--enable-foreman-plugin-openscap \
--enable-foreman-proxy-plugin-openscap \
--enable-foreman-plugin-ansible \
--enable-foreman-proxy-plugin-ansible \
--foreman-proxy-dns-forwarders="10.8.104.51" \
--foreman-proxy-dns-forwarders="10.11.5.19" \
--foreman-proxy-dns-forwarders="10.10.160.2" \
--foreman-proxy-dns-forwarders="10.5.30.160"
```

Actions #1

Updated by Tomer Brisker over 5 years ago

  • Category set to foreman-installer script
  • Assignee set to Eric Helms

should be resolved by https://github.com/theforeman/foreman-installer/commit/718121360a5e07438e24dea70247b36bfbfae7a7, can you check if the change fixes the issue for you?

Actions #2

Updated by Tomer Brisker over 5 years ago

  • Triaged changed from No to Yes
Actions #3

Updated by roman plevka over 5 years ago

Tomer Brisker wrote:

should be resolved by https://github.com/theforeman/foreman-installer/commit/718121360a5e07438e24dea70247b36bfbfae7a7, can you check if the change fixes the issue for you?

Thanks! It looks like the issue's resolved. The installer now passes with no errors.

Actions #4

Updated by roman plevka over 5 years ago

  • Status changed from New to Resolved
Actions

Also available in: Atom PDF