Midnight Commander on master node doesn't exist

Bug #1527347 reported by Maksim Malchuk
42
This bug affects 9 people
Affects Status Importance Assigned to Milestone
Mirantis OpenStack
Opinion
Wishlist
Fuel Sustaining

Bug Description

Please add Midnight Commander to Centos 7.0 on the master node because it can't be installed in easy way:

[root@fuel ~]# yum install mc
Loaded plugins: fastestmirror, priorities
Loading mirror speeds from cached hostfile
No package mc available.
Error: Nothing to do

Revision history for this message
Dmitry Teselkin (teselkin-d) wrote :

Nothing to do from our side - mc is available in base repos.

Changed in mos:
assignee: MOS Linux (mos-linux) → Fuel for Openstack (fuel)
Revision history for this message
Maksim Malchuk (mmalchuk) wrote :

[root@fuel ~]# grep baseurl /etc/yum.repos.d/*
/etc/yum.repos.d/8.0_auxiliary.repo:baseurl=file:///var/www/nailgun/2015.1.0-8.0/centos/auxiliary/
/etc/yum.repos.d/nailgun.repo:baseurl=file:/var/www/nailgun/2015.1.0-8.0/centos/x86_64
/etc/yum.repos.d/nailgun.repo:baseurl=file:/var/www/nailgun/2015.1.0-8.0/mos-centos/x86_64

[root@fuel ~]# find /var/www/nailgun/ -iname 'mc*.rpm'
/var/www/nailgun/2015.1.0-8.0/mos-centos/x86_64/Packages/mcollective-common-2.5.3-3.el7~mos8.0.3.noarch.rpm
/var/www/nailgun/2015.1.0-8.0/mos-centos/x86_64/Packages/mcollective-2.5.3-3.el7~mos8.0.3.noarch.rpm
/var/www/nailgun/2015.1.0-8.0/mos-centos/x86_64/Packages/mcollective-client-2.5.3-3.el7~mos8.0.3.noarch.rpm

package doesn't exist

Revision history for this message
Michael Polenchuk (mpolenchuk) wrote :

Add the following lines into /etc/yum.repos.d/extra.repo:

#####
[base]
name=CentOS-$releasever - Base
mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch=$basearch&repo=os
gpgcheck=0
#####

then as usually `yum install -y mc`
P.S. Importance should be raised

Revision history for this message
Maksim Malchuk (mmalchuk) wrote :

Michael, feel free to raise the importance.
Also, if You think if this is joke, so please update the official documentation for this case.

Changed in mos:
milestone: none → 8.0
Revision history for this message
Roman Podoliaka (rpodolyaka) wrote :

Why don't we have base repos enabled by default?

Revision history for this message
Maksim Malchuk (mmalchuk) wrote :

Roman, i think to prevent accidental run 'yum update' which should broke the Fuel.

Revision history for this message
Aleksey Zvyagintsev (azvyagintsev) wrote :

Come on guys:
1) We can and we shouldn't enable base distro repos- its dangerous for fuel.
2) If you really need package
- Add base repo manually and install it
OR
- make aa simple commit with new package into
https://github.com/openstack/fuel-main/blob/master/requirements-rpm.txt

Revision history for this message
Roman Podoliaka (rpodolyaka) wrote :

I don't propose to install mc, vim, etc on the master node.

I just wish we had base repo enabled by default (just as we do on Ubuntu slaves now), so that it's easy to consume updates from the Linux distro and install distro packages, without putting them to our mirrors or (even worse) building our own version of a particular package (not only we have to support it in this case, it's not clear where to get debugging symbols from and so on).

It's not cleat to me why it's dangerous for Fuel, looks like it's really fragile then.

Revision history for this message
Maksim Malchuk (mmalchuk) wrote :

Fix proposed to branch: master
Review: https://review.openstack.org/#/c/259377/

Changed in mos:
assignee: Fuel for Openstack (fuel) → Maksim Malchuk (mmalchuk)
status: New → In Progress
Revision history for this message
Aleksey Zvyagintsev (azvyagintsev) wrote :

@Roman:
Our fuel-master not so stable yet, to use upstream repos for updates. Also we still sometime use patches kernel and etc.
(anyway, its only my opinion. anyone from fuel-build team will comment there?
)
Looks like for now only this repos are "trusted" for fuel by default:
https://github.com/openstack/fuel-main/blob/master/iso/bootstrap_admin_node.sh#L344-L360

Changed in mos:
importance: Wishlist → Low
Changed in mos:
status: In Progress → Invalid
assignee: Maksim Malchuk (mmalchuk) → nobody
milestone: 8.0 → none
importance: Low → Wishlist
importance: Wishlist → Undecided
Revision history for this message
Adam Heczko (aheczko-mirantis) wrote :

Hello, I'd like to restore this ticket from Invalid state.
My user story:
As a cloud administrator, I'd like to install latest security updates.
For this purpose I expect to have command 'yum -y update --security' working and updating only necessary packages.

See:
https://access.redhat.com/solutions/10021

IMO disabling repositories doesn't make much sense, rather it makes users angry about how Fuel behaves.
My understanding is that Fuel is *aplication* and not *appliance*.
So IMO disabling repositories is not the expected behavior.
Note that we still should warn customers about possible implications of updating Fuel master node.
But it is related to documentation coming with Fuel and appropriate user information.

information type: Public → Public Security
Changed in mos:
status: Invalid → New
status: New → Confirmed
importance: Undecided → Medium
milestone: none → 8.0
Revision history for this message
Maksim Malchuk (mmalchuk) wrote :
Revision history for this message
Roman Podoliaka (rpodolyaka) wrote :

Adam, let's use another bug for this and leave this one for mc case specifically.

Changed in mos:
status: Confirmed → Opinion
importance: Medium → Wishlist
assignee: nobody → Maksim Malchuk (mmalchuk)
Changed in mos:
assignee: Maksim Malchuk (mmalchuk) → Fuel for Openstack (fuel)
milestone: 8.0 → 10.0
assignee: Fuel for Openstack (fuel) → Fuel Sustaining (fuel-sustaining-team)
information type: Public Security → Public
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.