Bug 1392470 - Node restart fails with 'Not available'
Summary: Node restart fails with 'Not available'
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: UI - OPS
Version: 5.7.0
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: GA
: cfme-future
Assignee: Marek Aufart
QA Contact: Dave Johnson
URL:
Whiteboard: openstack
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-07 15:09 UTC by Oleksandr Kolisnyk
Modified: 2018-10-02 14:32 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-10-02 14:30:18 UTC
Category: ---
Cloudforms Team: Openstack
Target Upstream Version:


Attachments (Terms of Use)
Err screen (125.41 KB, image/png)
2016-11-07 15:09 UTC, Oleksandr Kolisnyk
no flags Details

Description Oleksandr Kolisnyk 2016-11-07 15:09:13 UTC
Created attachment 1218054 [details]
Err screen

Setup:
CFME 5.7 (beta 2) + RHOS 10 (as Infrastructure provider)

Steps to Reproduce:
1. Log in to Cloudforms UI
2. Go Compute -> Infrastructure -> Nodes
3. Check one of the nodes, then click Power -> Restart

Actual results:
Failing with message "Restart: not available for <<NODE_ID>>"

Expected results:
Message "Node restart was initiated"

Comment 2 Oleksandr Kolisnyk 2016-11-07 15:11:09 UTC
Same issue for node reset (Power -> Reset)

Comment 3 Dave Johnson 2017-07-14 03:48:49 UTC
Please assess the importance of this issue and update the priority accordingly.  Somewhere it was missed in the bug triage process.  Please refer to https://bugzilla.redhat.com/page.cgi?id=fields.html#priority for a reminder on each priority's definition.

If it's something like a tracker bug where it doesn't matter, please set it to Low/Low.

Comment 4 Tzu-Mainn Chen 2017-07-18 14:37:34 UTC
Oleksandr, I think this is fixed in most recent releases - would you be able to test again?

Comment 8 Josh Carter 2018-10-02 14:30:18 UTC
Dear customer, 

The CloudForms team is reviewing the current CloudForms Bug(defect) backlog in order to target engineering efforts. We are closing any bugs for versions that no longer have an active errata stream or that have hit their age limit. We are committing to better management of the backlog as we move forward. If you have an bug that you are still able to reproduce on a current version of CloudForms please open a new bug. 

If you have any concerns about this, please let us know.

Thanks and regards!

Comment 9 Josh Carter 2018-10-02 14:32:50 UTC
Dear customer, 

The CloudForms team is reviewing the current CloudForms Bug(defect) backlog in order to target engineering efforts. We are closing any bugs for versions that no longer have an active errata stream or that have hit their age limit. We are committing to better management of the backlog as we move forward. If you have an bug that you are still able to reproduce on a current version of CloudForms please open a new bug. 

If you have any concerns about this, please let us know.

Thanks and regards!


Note You need to log in before you can comment on or make changes to this bug.