Bug 1626983 - Pages with pxe image information are missing
Summary: Pages with pxe image information are missing
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: UI - OPS
Version: 5.10.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: GA
: 5.10.0
Assignee: Zita Nemeckova
QA Contact: Radim Hrazdil
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-09-10 08:54 UTC by Radim Hrazdil
Modified: 2020-06-16 06:14 UTC (History)
6 users (show)

Fixed In Version: 5.10.0.15
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-02-12 16:52:42 UTC
Category: ---
Cloudforms Team: ---
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Samples comparing 5.9 vs 5.10 (2.04 MB, application/x-gzip)
2018-09-10 08:54 UTC, Radim Hrazdil
no flags Details

Description Radim Hrazdil 2018-09-10 08:54:35 UTC
Created attachment 1482046 [details]
Samples comparing 5.9 vs 5.10

Description of problem:

After adding PXE server and refreshing relationships (so that pxe images are updated), if you navigate to the individual pxe images, the page shows information about the pxe server, instead of the selected pxe image.

See the included video samples that compare the navigation with cfme 5.9. Please, excuse the quality of captured video samples (flickering), it should give an idea though.


Version-Release number of selected component (if applicable):
Version 5.10.0.12.20180822200426_5f6e52b

How reproducible:
100%

Steps to Reproduce:
1. add PXE server, refresh and wait for images to appear
2. Try to navigate to some pxe image
3.

Actual results:
Instead of pxe image page, the PXE Server details page is displayed

Expected results:
PXE Image details page should be desplayed

Additional info:

Comment 4 Radim Hrazdil 2018-09-19 10:31:14 UTC
Verified that PXE images detail pages are accessible.
CFME: Version 5.10.0.15.20180914163601_fb02d7e


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