Bug 1475248 - Back button disable while navigating instance from provider itself
Back button disable while navigating instance from provider itself
Status: NEW
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: User Experience (Show other bugs)
unspecified
Unspecified Unspecified
low Severity low
: GA
: cfme-future
Assigned To: Serena
Dave Johnson
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2017-07-26 05:31 EDT by Nikhil Dhandre
Modified: 2018-05-04 15:32 EDT (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Nikhil Dhandre 2017-07-26 05:31:04 EDT
Description of problem:

Back button disables when freshly navigate to an instance using the provider.
(compute > clouds > providers > Azure > Instance) 


How reproducible: always


Steps to Reproduce:

Method-1
1. add cloud appliance Azure
2. compute > clouds > providers > Azure > 
                          In Relationships > Instances > Select any one Instance.
3. You will get >>>>> back button disable. 

Method-2:
1. close appliance UI and log in again.
2. compute > clouds > Instances > select last Instance.
3. You will get >>>>> back button enables with history(All instances by provider) for navigation.


Actual results:
Back button disable

Expected results:
Back button enable

I think in the first method also its has to enable with history(All instances by provider)

Additional info:
Yes, In explorer in both method "Instances by Provider" tab is there. but still....

Snapshots:

M-1: https://drive.google.com/a/redhat.com/file/d/0BwdZUxbvLToZZDB6dml1Q3lTdGc/view?usp=sharing

M-2: https://drive.google.com/a/redhat.com/file/d/0BwdZUxbvLToZV19od3kxRU5fNmM/view?usp=sharing

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