On 10/27/2014 10:05 AM, Prasun Gera wrote:
Just wanted to check if this issue was reproduced by RedHat. I don't see any updates on Satellite yet that resolve this.
It's being addressed. I'm not involved with the side that will put updates on Satellite, so I can't say when they'll appear
On Fri, Oct 17, 2014 at 4:55 AM, Prasun Gera <prasun.gera@xxxxxxxxx <mailto:prasun.gera@xxxxxxxxx>> wrote: Actually, that's not such a great idea and will likely cause issues in the future. I wouldn't recommend it. I'm not using this in production, and was just tinkering around. On Fri, Oct 17, 2014 at 4:27 AM, Prasun Gera <prasun.gera@xxxxxxxxx <mailto:prasun.gera@xxxxxxxxx>> wrote: I actually managed to remove all the conflicted packages using rpm --erase --nodeps (in case it helps someone). This is what worked for me: rpm --erase --nodeps augeas-libs glusterfs glusterfs-api glusterfs-fuse glusterfs-libs glusterfs-rdma libsmbclient samba samba-client samba-common samba-winbind samba-winbind-clients (This saves /etc/samba/smb.conf.rpmsave) yum install augeas-libs glusterfs glusterfs-api glusterfs-fuse glusterfs-libs glusterfs-rdma libsmbclient samba samba-client samba-common samba-winbind samba-winbind-clients cp /etc/samba/smb.conf /etc/samba/smb.conf.bkp cp /etc/samba/smb.conf.rpmsave /etc/samba/smb.conf This seems to be working all right, although I haven't tested this much yet. On Fri, Oct 17, 2014 at 4:21 AM, RAGHAVENDRA TALUR <raghavendra.talur@xxxxxxxxx <mailto:raghavendra.talur@xxxxxxxxx>> wrote: On Fri, Oct 17, 2014 at 3:59 AM, Kaleb KEITHLEY <kkeithle@xxxxxxxxxx <mailto:kkeithle@xxxxxxxxxx>> wrote: On 10/16/2014 06:25 PM, Prasun Gera wrote: Thanks. Like I said, I'm not using the glusterfs public/epel repositories. Oh. Sorry. No, I didn't see that. Do you mean that I should add the public repos ? Nope. If you weren't already using the public repos then don't add them now. Sorry for any confusion. I don't have any packages from the public repo. So I thought that my system should be internally consistent since all the packages that it has are from RHN. It's the base OS channel that is causing the problems. Disabling the RHSS storage channel doesn't fix it. I'll alert Red Hat's release engineering. Sounds like they borked something. Prasun, The conflict is between different versions of samba and glusterfs in rhs channel and rhel channel. Temporary workaround for you should be yum update --exclude="glusterfs*" --exclude="samba*" --exclude="libsmb*" Let us know if that works. *Raghavendra Talur * * * -- Kaleb _________________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx <mailto:Gluster-users@xxxxxxxxxxx> http://supercolony.gluster.__org/mailman/listinfo/gluster-__users <http://supercolony.gluster.org/mailman/listinfo/gluster-users>
-- Kaleb _______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx http://supercolony.gluster.org/mailman/listinfo/gluster-users
