Project

General

Profile

Actions

Bug #24965

closed

Can not start Stoped Openstack Servers

Added by Clemens Bergmann over 5 years ago. Updated over 5 years ago.

Status:
Closed
Priority:
Normal
Category:
Compute resources - OpenStack
Target version:
-
Fixed in Releases:
Found in Releases:

Description

When Clicking the link to start a Server that runs on openstack we get an Error that the policy does not allow this action.
The Reason lies in https://github.com/theforeman/foreman/blob/develop/app/models/concerns/fog_extensions/openstack/server.rb#L16. If the VM is in mode "SHUTOFF" it can not be started with resume_server but must be called with start_server.
I suspect that five years ago when this code was written (https://projects.theforeman.org/issues/2891). Openstack did not support the SHUTOFF state.
I suggest adding an if option for that state (https://github.com/cbergmann/foreman/commit/1e786556dea1a7e6127fd72e529fa374b62b606e).
The second question is how to implement the stop function. Currently it is implementend with "suspend_server" but I suggest changing this to stop_server.
In the Openstack enviroment we use (Open Telekom Cloud) the suspend Function is not allowed. VMs are only allowed to be started and stopped.
The problem is that this change would change the behavior for existing installations. VMs that where suspended before would then be stopped. That might irritate users.
What is your opinion on this?

Kind regards
Clemens

Actions #1

Updated by Clemens Bergmann over 5 years ago

  • Description updated (diff)
Actions #2

Updated by Clemens Bergmann over 5 years ago

  • Assignee set to Daniel Lobato Garcia

I suggest Daniel looks at this because he implemented the functions in the first place.

Thanks again.
Clemens

Actions #3

Updated by Marek Hulán over 5 years ago

  • Assignee deleted (Daniel Lobato Garcia)

Sorry, it's not how it works :-) Daniel might be busy with other tasks atm. Would you be interesting on working on the patch? We coukd try to help at our dev irc channel.

Actions #4

Updated by Clemens Bergmann over 5 years ago

Hi,

thanks for the reply.
Sorry for the assignment. I just wanted to notify Daniel because I thought he surely had a good reasons to use suspend and tried to ask him about these.
My suggested patch is in the commit found here: https://github.com/cbergmann/foreman/commit/1e786556dea1a7e6127fd72e529fa374b62b606e
Do you think this might be a valid change or would the implied change in behavior negatively affect user expectations?

Actions #5

Updated by Marek Hulán over 5 years ago

  • Category set to Compute resources - OpenStack

I'm not openstack domain expert but the patch looks reasonable to me. Would you mind opening a PR with this patch? Hopefully someone with more knowledge would review and test. If you're not sure about the process, please see https://theforeman.org/contribute.html#SubmitPatches

Actions #6

Updated by The Foreman Bot over 5 years ago

  • Status changed from New to Ready For Testing
  • Pull request https://github.com/theforeman/foreman/pull/6085 added
Actions #7

Updated by Lukas Zapletal over 5 years ago

  • Fixed in Releases 1.20.0 added
Actions #8

Updated by The Foreman Bot over 5 years ago

  • Assignee set to Stephen Benjamin
  • Pull request https://github.com/theforeman/foreman/pull/6086 added
Actions #9

Updated by Anonymous over 5 years ago

  • Status changed from Ready For Testing to Closed
Actions

Also available in: Atom PDF