Support of fuse-sshfs on master node
Bug #1327994 reported by
Alexander Kislitsky
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Fix Committed
|
High
|
Sergey Otpuschennikov |
Bug Description
Customers and we need to have to develop on already deployed master node. For transparent mounting working directories into container we can use fuse-sshfs.
It is not enough to just install package fuse-sshfs on existed master node or in container - module fuse-sshfs is not loaded in container.
Fix of this bug is required for https:/
Changed in fuel: | |
importance: | Undecided → Critical |
description: | updated |
Changed in fuel: | |
importance: | Critical → High |
Changed in fuel: | |
assignee: | Fuel OSCI Team (fuel-osci) → Sergey Otpuschennikov (sotpuschennikov) |
Changed in fuel: | |
status: | Confirmed → In Progress |
To post a comment you must log in.
When we install sshfs from EPEL repository like described in http:// www.centosblog. com/sshfs- how-to- mount-remote- partition- via-ssh- on-centos/ into container module is not loaded with the error:
> modprobe fuse 2.6.32- 431.el6. x86_64/ modules. dep: No such file or directory
FATAL: Could not load /lib/modules/
On master node we have kernel 2.6.32- 431.el6. x86_64, but from EPEL repository kernel 3.10.30- 1.mira2. x86_64 is delivered.
So pay attention with which kernel fuse-sshfs module will have been built, please.