Closed portertech closed 7 years ago
This issue was originally submitted by @patrickatomic
We have fixed this in the past on our fork of Omnibus. I wonder if the latest package wasn't built with our fork. The issue is described in more detail in Chef's Omnibus issues https://github.com/chef/omnibus/issues/663.
https://github.com/sensu/omnibus/pull/4/files is the fix we had implemented before which should be working for /usr/bin
. I'll try to reproduce the issue and see if appending the additional paths works.
@patrickatomic can you please see if https://s3.amazonaws.com/sensu-omnibus-artifacts/el/7/x86_64/sensu-0.29.0-4000.el7.x86_64.rpm/sensu-0.29.0-4000.el7.x86_64.rpm resolves the issue for you?
@patrickatomic ping
Seems related to https://github.com/sensu/sensu-omnibus/issues/224
fixed! thanks
On 24 July 2017 at 12:41, Sean Porter notifications@github.com wrote:
Seems related to #224 https://github.com/sensu/sensu-omnibus/issues/224
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/sensu/sensu-omnibus/issues/219#issuecomment-317481426, or mute the thread https://github.com/notifications/unsubscribe-auth/AITCoy5GTnd7DIZrfQ21NpIemPnYhr8Vks5sRMlWgaJpZM4OD_jB .
--
Patrick Cardin Senior System Administrator cell: 438 494 6300 http://1.atomic-light-001.appspot.com/email_signatures# www.atomicfiction.com
The fix has been implemented in PR https://github.com/sensu/omnibus/pull/9 and will be in the next release of Sensu (1.0.1).
This issue is a migrated/copy of https://github.com/sensu/sensu/issues/1695
looks like that new sensu package is conflicting with other OS packages... since some directory are "owned" by the sensu packages, and it shouldn't be the case... Doing a rpm -qlp sensu-0.29.0-11.el7.x86_64.rpm
indicates that, for instance, /usr /usr/bin /usr/bin/sensu-install /var
are owned by the sensu package... older versions didnt have that issue. Looks to me like the new RPM as been created using a "/*" in the %files section of the RPM spec... Centos6.7 and older versions won't complain about it, but starting from 6.8 and 7... the RPM DB is smart enough to detect it's causing conflicts...
/tmp/sesu (root@mtl-lnx-055) $ rpm -qf /usr/bin filesystem-3.2-21.el7.x86_64