On Sep 24, 2012, at 3:36 AM, Andrew Fitzsimon <afitzsim(a)redhat.com> wrote:
Why not hide the button ?
That's the proper solution. Another option that is less preferred is to have a clearly
disabled visual state for the button (grey it out) so that it is obvious that the button
is disabled.
For now, it sounds like we have a problem if a user thinks they can click it and expects
something to happen.
On 24/09/2012, at 5:34 PM, Tomas Hrcka <thrcka(a)redhat.com> wrote:
> On Fri, 2012-09-21 at 13:36 -0400, James Labocki wrote:
>> I'd like to confirm the behavior I am experiencing is expected with regards
to the restart button in conductor.
>>
>> 1. Launch two instances. One to RHEV provider and one to EC2 provider.
>>
>> 2. Wait until instances are running.
>>
>> 3. Select RHEV instance and select "restart".
>> a. Nothing happens in the conductor UI.
>> b. Nothing happens in the RHEV-M interface.
>
>
>
>>
>> 4. Select Amazon instance select "restart".
>> a. Instance restarts in EC2
>>
>> Is this known and expected behavior that the restart button on RHEV can be
selected, but it does not do anything?
>
> The restart button for providers without restart capabilities is
> disabled. That is why nothing happens when you press the button, it does
> not send request to the conductor.
>
>>
>>
>> If this is a bug please let me know and I can open a bugzilla to fix it. If this
is not a bug, can you provide insight on the level of effort to either:
>>
>> 1. check the provider when displaying instance information and remove the ability
to press restart on providers that do not support restarting instances (RHEV)?
>>
>> 2. Make the restart button restart the instances on RHEV.
>>
>> Thanks for your help!
>>
>> -James
>
>