Red Hat Bugzilla – Bug 1272288
"Couldn't find MiqServer with id=0 [ops/x_button]" when starting the Scheduler role on a different appliance
Last modified: 2018-01-30 13:38:08 EST
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):
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.
An error page appears with the message "Couldn't find MiqServer with id=0 [ops/x_button]"
Remain on the diagnostics page.
Blair, is this the case on 5.5 as well? Is the workaround to go to the individual appliance and set the role?
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.