Ask Your Question
0

Devstack Install Fail with Permissions

asked 2017-01-20 04:12:54 -0500

boball gravatar image

There seems to be some real issue with permissions when following the devstack install instructions that I can see are widespread. Has there been a security change in Linux latest versions that applies Deny First model that's catching us relative noobs out?

The notion of being able to use root seems over-optimistic and the sudo user created at usual Linux install doesn't appear to get the full root privileges that start.sh needs to write to all folders it needs to, hence the multiple failures people are having trying to install.

Yes, there are stated individual chown fixes for this but this still doesn't address the problem as some initial edits are not possible cos of permission denied when attempting echoing a line into /etc/sudoers to allow full access or chowning /etc and so the circle is complete! This gives me little confidence that I'll end up with a working Devstack install and while I appreciate the create devstack script seems to do the business to allow the install to complete, some of the basic prior permissions not being in place at the beginning makes for something that I feel will likely fall apart on it's first update.

Any solutions to this or maybe a new install document that works more universally or a better installer? Don't ask, don't get!!

edit retag flag offensive close merge delete

Comments

devstack is a tool for developers to quickly spin up OpenStack for development and testing. For that reason, the documentation is not much more than "how to get started" plus some additional information. If you have problems with permissions, I guess you are supposed to read the logs and the code.

Bernd Bausch gravatar imageBernd Bausch ( 2017-01-20 17:48:48 -0500 )edit

Having said that, if you have specific problems with devstack, error descriptions, log file contents and a description of your configuration would allow other people to help you.

Bernd Bausch gravatar imageBernd Bausch ( 2017-01-20 17:50:32 -0500 )edit

1 answer

Sort by » oldest newest most voted
0

answered 2017-01-26 05:02:37 -0500

boball gravatar image

Thanks for retreating from the 'local shop for local people' stance in your initial reply, doesn't really work with a globally accessible website and download!

Nevertheless, I take your point and realise that this install is aimed at a specific audience and admit I was a bit short on info to allow you to see the problem I'm having.

The problem I have is really just one of confidence and must be something a lot of noobs are struggling with. All I've done is strictly follow the Devstack All in One install instructions with a v16.0.4 min Ubu server installation, as suggested, and all is good. Then dutifully following the instructions to install starting with creating a user, no problem, grab sudo, all good, and then an echo line to get you in the sudoers file and that's where it all falls down.

stack@UbuStack:~$ sudo echo "stack ALL=(ALL) NOPASSWD: ALL" >> /etc/sudoers bash: /etc/sudoers: Permission denied

Whatever user you use, with or without sudo, doesn't let you write to this location, even after a hopeful chown which also returns the above error as it's all owned by root/root and that's where it starts to unravel as your user basically doesn't have the rights to spread the writing of files when you run the start.sh script, erroring on permissions in many places not least /opt locations.

This is it! Finding it as an issue with all Ubu versions I'm installing now from v14 onwards so not a Devstack issue, more an Ubu problem. Should I be able to use the pre-installed root account (password?) and do what's needed for the install to complete this way? General reading indicates I shouldn't (be able to) do this. Maybe I should be posting this on an Ubu forum as it may be better addressed there.

Cheers, Rob.

edit flag offensive delete link more

Comments

This is not a devstack or Openstack problem. The sudoers file is not writable for a normal user. You must be root before issuing the echo command, or do something like sudo sh -c "echo stack ALL=(ALL) NOPASSWD: ALL >>/etc/sudoers"

Personally, I would become root via su, then run visudo.

Bernd Bausch gravatar imageBernd Bausch ( 2017-01-26 06:44:06 -0500 )edit

By the way, I am merely reporting what devstack is for. I have no involvement with devstack. The web page says: "It is used interactively as a development environment and as the basis for much of the OpenStack project’s functional testing." I guess you should take this as a warning.

Bernd Bausch gravatar imageBernd Bausch ( 2017-01-26 06:47:58 -0500 )edit

Thanks Bernd, appreciate your help and didn't intend to sound mean in any way. As you say, this is Def NOT a Devstack issue and is firmly embedded in Ubu root privileges and permissions. Your su suggestion is sound as long as I can get past root's password, which may prove problematic! Thanks, Rob.

boball gravatar imageboball ( 2017-01-27 05:10:14 -0500 )edit

:) Well, in order to establish sudo access for a user, you need to be root. Take it like a man :)

Bernd Bausch gravatar imageBernd Bausch ( 2017-01-27 21:55:57 -0500 )edit

Aaahh! sudo su root appears to get me on as root so will try all the stuff that baulked on me before! Revalations!

Thanks Bernd, with your help. I have finally grown a pair! Cheers, Rob.

boball gravatar imageboball ( 2017-01-30 09:52:35 -0500 )edit

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools

Stats

Asked: 2017-01-20 04:12:54 -0500

Seen: 168 times

Last updated: Jan 26 '17