Fixes #36807 - UX fixes and add update count action

[sjha4]

What are the changes introduced in this pull request?

Added task link
Added action on page to refresh counts (Also sets up code to add syncs in the future)
UX fixes

Considerations taken when implementing this change?

What are the testing steps for this pull request?

1. Go to Capsule> content tab and make sure the new action works.
2. Also some minor cosmetic changes.

[sjha4]

[test katello]

[ianballou]

I also noticed that failing content counts updates pauses the task. I think we could just make it stop completely and turn into a warning since the json update is all or nothing.

[sjha4]

The latest commit should:

1. Allow content_counts to be updated even with presence of repositories not synced on capsule.
2. Use skip over pause as rescue strategy for failed content_count update task.

[sjha4]

[test katello]

[ianballou]

The updated content count logic seems to be messing up somewhere for me. I have a content view version with a yum repo and a python repo that is promoted to 5 LCEs including Library. All of the LCEs except Library are assigned to my capsule, and only one of those are actually synced.

What I'm seeing is this:

               "content_counts" => {
                    "content_view_versions" => {
                        "2" => {
                            "repositories" => {
                                "2" => {
                                        "rpm" => 32,
                                    "erratum" => 4
                                }
                            }
                        },
                        "8" => {
                            "repositories" => {
                                "62" => {
                                        "rpm" => 32,
                                    "erratum" => 4
                                },
                                "63" => {}
                            }
                        }
                    }

63 is my python repo. For some reason, the counts are completely blank even though the smart proxy repo has python packages. The yum content is being recorded, however.

[sjha4]

The updated content count logic seems to be messing up somewhere for me. I have a content view version with a yum repo and a python repo that is promoted to 5 LCEs including Library. All of the LCEs except Library are assigned to my capsule, and only one of those are actually synced.

What I'm seeing is this:

               "content_counts" => {
                    "content_view_versions" => {
                        "2" => {
                            "repositories" => {
                                "2" => {
                                        "rpm" => 32,
                                    "erratum" => 4
                                }
                            }
                        },
                        "8" => {
                            "repositories" => {
                                "62" => {
                                        "rpm" => 32,
                                    "erratum" => 4
                                },
                                "63" => {}
                            }
                        }
                    }

63 is my python repo. For some reason, the counts are completely blank even though the smart proxy repo has python packages. The yum content is being recorded, however.

What did I do now?! Let me look.. 😭 😄

[ianballou]

I think I see the issue, latest_content_counts is nil for a repo not yet synced on the smart proxy, so it's replacing the actual content counts that were calculated for a good repo earlier.

For example, it calculated the counts for my "Test" LCE first, which included the python repo. "Test" is synced to the smart proxy. Then, it calculated the counts for my "Prod" LCE, which is not yet synced. The counts for the python repo are {} since the latest_content_counts returned nil.

The fact that we loop through unarchived repositories might be making this difficult. Do you think we could be looping over archived repositories instead?
Never mind this crossed-out bit, we should be looping over the promoted repositories since they exist separately on the smart proxies.

[ianballou]

So it seems we keep overwriting the content counts as we loop along because we're storing the counts only for the archived repository. However, on the smart proxy, we do sync the promoted repositories separately.

Should we go back to showing counts for all promoted repositories? Those are the ones that users consume from at least... I know it confused something in the UI, but I wonder if now the counts aren't showing enough.

[sjha4]

Updated PR to:

1. Return env_repo id as key in content_counts.
2. Added metadata section to json to hold env_id of repo and library_instance_id of env_repo.
3. Updated UI/tests to handle the JSON change.

[sjha4]

[test katello]

[ianballou]

Overall this is looking good! Gonna do some more in-depth testing tomorrow, but I think it should be good soon.

[ianballou]

Looking good to me! Tested some more scenarios with removing LCEs from the smart proxy and the UI handled them well. Only caveat is the issue with the counts not updating if the repo list is completely empty, but that'll be taken care of in #10775