Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem: Power on/off for any rackspace virtual machine shows error notificatoin 
Error - undefined method `stop' for #<Fog::Compute::RackspaceV2::Server:0x00000>


Version-Release number of selected component (if applicable): 6.1.2


How reproducible:


Steps to Reproduce:
1. Go to infrastructure and click on compute resource. 
2. Create compute resource using provider rackspace.
3. Try to stop/start any virtual machine.

Actual results:
undefined method `stop' for #<Fog::Compute::RackspaceV2::Server:0x00000>

Expected results:
Should stop or start vm

Additional info:

Moving 6.2 bugs out to sat-backlog.

Created redmine issue http://projects.theforeman.org/issues/17898 from this bug

Upstream bug assigned to afeferku

Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/17898 has been resolved.

Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA.
> > 
> > For information on the advisory, and where to find the updated files, follow the link below.
> > 
> > If the solution does not work for you, open a new bug report.
> > 
> > https://access.redhat.com/errata/RHSA-2018:0336