Bug 1537411 - SEVERE: Warning: You're using an untyped slot!
Summary: SEVERE: Warning: You're using an untyped slot!
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: Frontend.WebAdmin
Version: 4.2.1.2
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ---
: ---
Assignee: Alexander Wels
QA Contact: Lucie Leistnerova
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-01-23 06:50 UTC by Sandro Bonazzola
Modified: 2022-06-27 07:24 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-12-10 01:21:02 UTC
oVirt Team: UX
Embargoed:
sbonazzo: ovirt-4.3-


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHV-46511 0 None None None 2022-06-27 07:24:06 UTC
oVirt gerrit 87368 0 master MERGED webadmin: GWTP slot mechanism update 2018-02-09 13:07:29 UTC
oVirt gerrit 88903 0 master MERGED webadmin: GWTP legacy slots 2018-03-14 12:47:37 UTC

Description Sandro Bonazzola 2018-01-23 06:50:29 UTC
Description of problem:
webadmin-0.js:19919 Tue Jan 23 07:46:13 GMT+100 2018 com.gwtplatform.mvp.client.presenter.slots.LegacySlotConvertor
SEVERE: Warning: You're using an untyped slot!
Untyped slots are dangerous! Please upgrade your slots using
the Arcbee's easy upgrade tool at
https://arcbees.github.io/gwtp-slot-upgrader
eGe @ webadmin-0.js:19919


Version-Release number of selected component (if applicable):
ovirt-engine-webadmin-portal-4.2.1.1-1.el7.centos.noarch

I was re-activating an host from maintenance after booting up my home lab.
The host disappeared from the list (I'll open a separate bug for this) so I checked the console of the browser and seen above message.

Comment 1 Sandro Bonazzola 2018-01-23 07:08:50 UTC
(In reply to Sandro Bonazzola from comment #0)

> The host disappeared from the list (I'll open a separate bug for this) so I
> checked the console of the browser and seen above message.

Ignore this, looks like a filter was on showing only hosts in maintenance and it disappeared because once activated it was obviously not in maintenance anymore.

Comment 2 Tomas Jelinek 2018-01-24 07:59:31 UTC
(In reply to Sandro Bonazzola from comment #0)
> Description of problem:
> webadmin-0.js:19919 Tue Jan 23 07:46:13 GMT+100 2018
> com.gwtplatform.mvp.client.presenter.slots.LegacySlotConvertor
> SEVERE: Warning: You're using an untyped slot!
> Untyped slots are dangerous! Please upgrade your slots using
> the Arcbee's easy upgrade tool at
> https://arcbees.github.io/gwtp-slot-upgrader
> eGe @ webadmin-0.js:19919

just to note the "dangerous" here does not refer to security vulnerability.

Anyway, it is an item we wanted to do after upgrading to GWT 2.8 - but we did not have a BZ to track it. So, will keep this BZ for tracking this refactoring.

> 
> 
> Version-Release number of selected component (if applicable):
> ovirt-engine-webadmin-portal-4.2.1.1-1.el7.centos.noarch
> 
> I was re-activating an host from maintenance after booting up my home lab.
> The host disappeared from the list (I'll open a separate bug for this) so I
> checked the console of the browser and seen above message.

Comment 3 Greg Sheremeta 2018-01-27 16:50:07 UTC
(In reply to Tomas Jelinek from comment #2)
> just to note the "dangerous" here does not refer to security vulnerability.
> 
I think untyped slots allow XSS, but don't quote me

Comment 4 Alexander Wels 2018-02-05 15:07:22 UTC
It doesn't allow security vulnerabilities, it allows untyped slots with allow for easier bugs in that area. All our slots are currently untyped.

Comment 5 Lucie Leistnerova 2018-10-01 09:27:42 UTC
Error SEVERE: Warning: You're using an untyped slot!
still visible in FF console log.

tested in ovirt-engine-webadmin-portal-4.3.0-0.0.master.20180928133328.git50c4de4.el7.noarch

Comment 7 Greg Sheremeta 2018-12-10 01:21:02 UTC
Unfortunately we do not have capacity to work on this. It's a cosmetic issue in the browser console.


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