Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Missing Comparison Sections (depending on navigation steps) #6239

Open
hstastna opened this issue Sep 26, 2019 · 6 comments
Open

Missing Comparison Sections (depending on navigation steps) #6239

hstastna opened this issue Sep 26, 2019 · 6 comments

Comments

@hstastna
Copy link

hstastna commented Sep 26, 2019

When comparing various items (VMs, Hosts, Templates...), displayed in a nested list, Comparison Sections accordion is missing, it is not possible to change between the sections, only Workload section is available.

Steps to reproduce: (one of possible scenarios)

  1. Compute > Infrastructure > Datastores
  2. Display some datastore's textual summary (click on some datastore)
  3. Click on Managed VMs from Relationships table
  4. Choose at least 2 VM(s) (check the checkboxes)
  5. Configuration > Compare Selected items
    => Comparison Sections accordion is missing
    miss_acc

Expected result:
Comparison Sections present, as it is for example for comparing VMs, displayed in Compute > Infrastructure > Virtual Machines:
comparison_section


Additional info:
I've tested the presence of the issue in: 5.9, 5.10, 5.11 and it is present for all of them.

The presence of this issue depends also on navigation steps, it works for some items displayed in a nested list (for example VMs displayed from a provider's details page).

If you will not be able to reproduce this, it may be because of a different issue: https://bugzilla.redhat.com/show_bug.cgi?id=1733120 (fixed)

@hstastna
Copy link
Author

@h-kataria @himdel @martinpovolny What do you think about this issue? Does it make sense to work on this or are we already working on moving Compare screen to React? Thanks in advance :)

@himdel
Copy link
Contributor

himdel commented Nov 26, 2019

I think the cause is that Datastore controller doesn't really know how to render listnavs for vm or template.

So, I think it may make sense to wait, otherwise we need a way for controller A to use controller B code to display a listnav that controller B would display normally (for any combination of A and B where A has a nested list of B), and we tried that already in #2913 without much progress.

(That said, I only know about the generic case, I haven't really looked if the Comparison listnav would be a simpler case.)

@h-kataria h-kataria added the bug label Dec 6, 2019
@h-kataria h-kataria assigned hstastna and unassigned rvsia Dec 6, 2019
@hstastna
Copy link
Author

hstastna commented Dec 17, 2019

@himdel I am asking myself, if it is really necessary for Datastore controller (and probably some others) to know how to render listnavs for displaying missing Comparison Sections . We just need to render the appropriate div with Comparison Sections, nothing else. That shouldn't be so difficult. The appropriate template is just not rendered. In explorer screens, it happens through replace_right_cell_text method.

@himdel
Copy link
Contributor

himdel commented Jan 6, 2020

Feel free to try :).

As far as I can tell, it involves rendering layouts/listnav/compare_secions, which only happens in VmCommon#replace_right_cell now, but theoretically only depends on making sure to provide the right values for @lastaction, @drift_obj, @sb[:compare_db], @sections_tree and @explorer.

Not sure if any of that can work without having layouts/listnav rendered in the first place, with @compare set to true and a bunch of layout logic in render_listnav_filename which will probably be wrong in some places.

@h-kataria h-kataria assigned ZitaNemeckova and unassigned hstastna Apr 14, 2020
@h-kataria
Copy link
Contributor

@ZitaNemeckova can you take a look if this can be easily fixed as per #6239 (comment)

@miq-bot
Copy link
Member

miq-bot commented Feb 27, 2023

This issue has been automatically marked as stale because it has not been updated for at least 3 months.

If you can still reproduce this issue on the current release or on master, please reply with all of the information you have about it in order to keep the issue open.

Thank you for all your contributions! More information about the ManageIQ triage process can be found in the triage process documentation.

@miq-bot miq-bot added the stale label Feb 27, 2023
@Fryguy Fryguy removed the stale label Mar 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

8 participants