Bug 1874889 - Missing arrows on CPU and Memory input box
Summary: Missing arrows on CPU and Memory input box
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Compute Resources
Version: 6.8.0
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Lukáš Hellebrandt
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-09-02 13:57 UTC by Radek Mynar
Modified: 2021-10-18 12:49 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-10-18 12:49:02 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
missing arrows (72.05 KB, image/png)
2020-09-02 13:57 UTC, Radek Mynar
no flags Details
missing arrows in vmware (122.69 KB, image/png)
2020-09-22 15:37 UTC, Radek Mynar
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 30288 0 Normal Closed replace the existing CPU/Cores/Socket input 2021-10-18 12:49:02 UTC
Foreman Issue Tracker 30784 0 Normal Closed replace the existing memory allocation input 2021-10-18 12:49:02 UTC

Description Radek Mynar 2020-09-02 13:57:45 UTC
Created attachment 1713443 [details]
missing arrows

Description of problem:

When creating a new host on libvirt there are no arrows visible in numeric input box for CPUs and Memory

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

How reproducible:
always

Steps to Reproduce:
1. Add a libvirt Compute Resource or use existing
2. Go to Hosts -> Create Host
3. Choose to create the host on libvirt
4. Go to tab 'Virtual Machine'

Actual results:
The arrows are not visible

Expected results:
The arrows are visible

Additional info:
Observed on Firefox and Chromium. The arrows are visible in Satellite 6.7.2

Comment 1 Brad Buckingham 2020-09-08 17:32:44 UTC
Does clicking on where the arrows should be still work?

Comment 2 Radek Mynar 2020-09-09 08:38:51 UTC
The buttons work as expected, it's only about the missing arrows.

Comment 5 Mike McCune 2020-09-21 21:55:43 UTC
This happens with RHEV too. See:

http://people.redhat.com/~mmccune/missing-arrows-68.png

Comment 7 Tomer Brisker 2020-09-22 12:57:09 UTC
Moving to CR component as this isn't libvirt specific. 
Is there any error in the browser console when loading the form?

Comment 9 Radek Mynar 2020-09-22 15:37:23 UTC
Created attachment 1715730 [details]
missing arrows in vmware

Comment 10 Radek Mynar 2020-09-22 15:57:01 UTC
These arrows are also missing in VMware. It may be interesting, that the arrows are visible in section Storage->Size (see screenshot).

I tried to reload the page with disabled cache and received following warnings in console:

> Chyba zdrojové mapy: Error: request failed with status 404
> URL adresa zdroje: https://dhcp-2-251.vms.sat.rdu2.redhat.com/webpack/foreman_ansible/foreman_ansible-2cd048dff2e246fee89b.js
> URL adresa zdrojové mapy: foreman_ansible-2cd048dff2e246fee89b.js.map
> Chyba zdrojové mapy: Error: NetworkError when attempting to fetch resource.
> URL adresa zdroje: https://dhcp-2-251.vms.sat.rdu2.redhat.com/webpack/katello/katello:fills-5ab4cca6c72a91a7a062.js
> URL adresa zdrojové mapy: katello:fills-5ab4cca6c72a91a7a062.js.map 2
> Chyba zdrojové mapy: Error: request failed with status 404
> URL adresa zdroje: https://dhcp-2-251.vms.sat.rdu2.redhat.com/webpack/foreman_rh_cloud/foreman_rh_cloud:subscriptions_extension-d90a8900df38b45c9a2f.js
> URL adresa zdrojové mapy: foreman_rh_cloud:subscriptions_extension-d90a8900df38b45c9a2f.js.map 2
> Chyba zdrojové mapy: Error: request failed with status 404
> URL adresa zdroje: https://dhcp-2-251.vms.sat.rdu2.redhat.com/webpack/foreman_ansible/foreman_ansible-2cd048dff2e246fee89b.js
> URL adresa zdrojové mapy: foreman_ansible-2cd048dff2e246fee89b.js.map

Sorry for some Czech words, they are about source map errors (See: https://developer.mozilla.org/en-US/docs/Tools/Debugger/Source_map_errors). I don't know if these errors are related to this bug. If not, we can we can create another bug.

Comment 13 Tomer Brisker 2021-10-18 12:49:02 UTC
These fields were completely rewritten in 6.9.0 using React components, closing as CURRENTRELEASE. If issue persists please reopen.


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