Mailing-List: contact issues-help@aurora.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@aurora.apache.org
Date: Tue, 2 Feb 2016 18:54:40 +0000 (UTC)
From: "Maxim Khutornenko (JIRA)" <jira@apache.org>
To: issues@aurora.apache.org
Message-ID: <JIRA.12935031.1454049946000.279433.1454439280094@Atlassian.JIRA>
In-Reply-To: <JIRA.12935031.1454049946000@Atlassian.JIRA>
References: <JIRA.12935031.1454049946000@Atlassian.JIRA>
 <JIRA.12935031.1454049946544@arcas>
Subject: [jira] [Reopened] (AURORA-1604) Identity.role is still used in the
 UI leading to duplicate instances on job page
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/AURORA-1604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Maxim Khutornenko reopened AURORA-1604:
---------------------------------------

Reverting this patch as per AURORA-1603 to avoid merge conflicts.

> Identity.role is still used in the UI leading to duplicate instances on job page
> --------------------------------------------------------------------------------
>
>                 Key: AURORA-1604
>                 URL: https://issues.apache.org/jira/browse/AURORA-1604
>             Project: Aurora
>          Issue Type: Bug
>          Components: Scheduler
>            Reporter: Maxim Khutornenko
>            Assignee: Maxim Khutornenko
>            Priority: Blocker
>         Attachments: vagrant_instance_dupes.png
>
>
> While trying to investigate AURORA-1603, found a bug in the UI that results in duplicate instances under the job page. The below code is [now gone|https://reviews.apache.org/r/42811/] but the UI is still [relying on it|https://github.com/apache/aurora/blob/89fad5a8895482b6c3fa45356137aa250d766dfe/src/main/resources/scheduler/assets/js/services.js#L32-L35]:
> h6.Query.java
> {noformat}
>      if (query.isSetOwner()) {
>         query.setRole(query.getOwner().getRole());
>         query.unsetOwner();
>       }
> {noformat}
> I was able to repo this in vagrant by creating 2 prod/hello jobs with different roles: 'vagrant' and 'www-data' (see picture attached).


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)