Bug 1272288 - "Couldn't find MiqServer with id=0 [ops/x_button]" when starting the Scheduler role on a different appliance
Summary: "Couldn't find MiqServer with id=0 [ops/x_button]" when starting the Schedule...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: UI - OPS
Version: 5.4.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: GA
: cfme-future
Assignee: Dan Clarizio
QA Contact: Alex Newman
URL:
Whiteboard: schedule:distributed
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-10-16 01:21 UTC by bmorriso
Modified: 2018-01-30 18:38 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-06-07 18:43:11 UTC
Category: ---
Cloudforms Team: ---
Target Upstream Version:
Embargoed:
anewman: automate_bug-


Attachments (Terms of Use)

Description bmorriso 2015-10-16 01:21:06 UTC
Description of problem:

In a configuration with two appliances in one region, starting up the scheduler role (or any of the other region-level singleton roles) on the appliance where it isn't already active causes this error message to appear in the UI:

"Couldn't find MiqServer with id=0 [ops/x_button]" 

The scheduler role is still successfully activated.

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

How reproducible:
always

Steps to Reproduce:
1. Navigate to Configure > Configuration > Diagnostics > 
CFME Region: Region 0 > Roles By Server
2. Start the Scheduler Role on the appliance where it is inactive.
3. 

Actual results:
An error page appears with the message "Couldn't find MiqServer with id=0 [ops/x_button]" 


Expected results:
Remain on the diagnostics page. 

Additional info:

Comment 2 Dave Johnson 2015-10-26 18:31:55 UTC
Blair, is this the case on 5.5 as well?  Is the workaround to go to the individual appliance and set the role?

Comment 3 Chris Pelland 2017-06-07 18:43:11 UTC
This BZ has been closed since it was opened on a version of CloudForms that has reached the end of its lifecycle.  If you find that this bug is still relevant, please open a new BZ against the relevant supported version of CloudForms.


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