Bug 1565177
Summary: | update from 6.2 -> 6.3 results in no content views shown from webui | ||
---|---|---|---|
Product: | Red Hat Satellite | Reporter: | Reartes Guillermo <greartes> |
Component: | Upgrades | Assignee: | satellite6-bugs <satellite6-bugs> |
Status: | CLOSED WORKSFORME | QA Contact: | Katello QA List <katello-qa-list> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 6.3.0 | CC: | greartes, inecas, mbacovsk |
Target Milestone: | Unspecified | ||
Target Release: | Unused | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2018-04-20 15:54:10 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Attachments: |
Description
Reartes Guillermo
2018-04-09 14:34:21 UTC
Created attachment 1419345 [details]
sat 6.3.0 upgraded from 6.2.14 with empty content views from web ui
Created attachment 1419346 [details]
hammer output, content views are shown (but it did not perform any operation yet)
hammer> content-view list --organization-id 3
----------------|---------------------------|--------------------------------------|-----------|---------------------|-----------------------------------------------
CONTENT VIEW ID | NOMBRE | LABEL | COMPOSITE | LAST PUBLISHED | REPOSITORY IDS
----------------|---------------------------|--------------------------------------|-----------|---------------------|-----------------------------------------------
14 | C_RHEL7 | C_RHEL7 | true | 2018/01/18 12:59:22 | 1082, 1083, 1084, 1085, 1086, 1087, 1088, 1089
2 | Default Organization View | 28d36378-fa4b-4294-81f6-c2bce5688736 | | 2016/09/10 01:12:44 |
9 | PLUS RHEL7 | PLUS_RHEL7 | | 2018/04/07 12:24:31 | 1, 3, 6, 5, 4, 1155, 1156, 96, 411
6 | RH-VIRT4-RHEL7 | RH-VIRT4-RHEL7 | | 2018/04/07 12:44:15 | 1, 6, 5, 552, 551, 1155, 68, 67, 1156
13 | S_3PARTY7 | S_3PARTY7 | | 2018/01/18 11:05:00 | 411
11 | S_PUPPET | S_PUPPET | | 2017/08/18 20:38:43 |
12 | S_RHEL7 | S_RHEL7 | | 2018/01/18 11:14:51 | 1, 3, 6, 5, 4, 46, 96
----------------|---------------------------|--------------------------------------|-----------|---------------------|-----------------------------------------------
From Web-UI: No content views.
Created attachment 1419347 [details]
sosreport empty cviews from webui but not from hammer
Created attachment 1419348 [details]
foreman-debug missing cviews from webui but not from hammer
Hi Reartes, Do you have an internal reproducer? Do you see any errors in the browser console? > Do you have an internal reproducer? I did perform the upgrade only once. > Do you see any errors in the browser console? Interesting question, i did test also with chrome and it works. It seems specific to Firefox. I will upload both images. Created attachment 1420112 [details]
working content views (Chromium 59.0)
Created attachment 1420113 [details]
empty content views with firefox 54.0
Hi, After updating to 6.3.1 it is working correclty. Thanks. Reartes, Thanks for the update. Unfortunately, I have not been able to reproduce this issue. I do not see anything in the logs that indicate why it may have occurred. I am also not seeing anything in 6.3.1 that should have specifically resolved it. In the screenshot in comment 8 for firefox, the 404 that is shown for nutupane.html is suspicious. The reason being nutupane is no longer used in 6.3; therefore, I am wondering if perhaps there was a browser caching issue. I lean towards closing this for now and re-opening if we additional reports. Thoughts? Hi, Since this Sat6 is la lab environment, it is not on 7x24 and the desktop from i access it was also powered off some time in between i really doubt that it was a caching issue (or an improper excessive caching/bug in Firefox). I also remember to ran the installer and the issue remained. Only after errata 6.3.1 did it went away. Closing is the right thing to do, of course. Cheers. Closing for now. If someone re-encounters this issue, feel free to re-open with additional details. Thanks! |