0.28.x UI is working for you even when you click into an agent? Can you show us which requests are being made in the old UI vs the new UI and which ones do not work for you? (use chrome's built-in debugging tools)
On Mon, Sep 25, 2017 at 3:38 PM, Aaron Wood <aaronjw...@gmail.com> wrote: > I just built Mesos 0.28.x and tried out this scenario. It seems that this > issue presents itself only in 1.0.x and up. I also found out that DCOS > hides this issue if someone uses https://github.com/dcos/adminrouter > > I have not dug through the 0.28.x code enough to pinpoint the exact area > for where the logic is different. Maybe someone that has worked on the UI > in the past can shed more light on this...? > > On Wed, Sep 13, 2017 at 8:03 PM, Benjamin Mahler <bmah...@apache.org> > wrote: > > > +haosdent, vinod > > > > Blaming the lines you pointed to gives me: > > > > https://github.com/apache/mesos/commit/b2fc58883e2cd0ca144fd1b0e10cad > > 4235a50223 > > > > I've added vinod and haosdent since they were involved in the change, it > > looks like this makes the master talk directly to a different master > > host:port. Is this what breaks for you? > > > > If so, I'm not sure why pre-1.0.x would work for you if you were to click > > into an agent, as that will also make a request directly to an agent > > host:port. > > > > Ben > > > > On Mon, Sep 11, 2017 at 7:44 PM, Aaron Wood <aaronjw...@gmail.com> > wrote: > > > > > Hey Ben, > > > > > > There was a change sometime after Mesos 1.0.x (I think) that altered > how > > > the leader state was obtained > > > https://github.com/apache/mesos/blob/master/src/webui/ > > > master/static/js/controllers.js#L362-L364 > > > > > > This seems to be an intended change but this causes UI error modals to > > > continually pop up stating that the leader could not be reached when > > > accessing the UI over a tunnel. The errors also show when you try to > > access > > > agent info among other things throughout the angular app. > > > > > > I'm curious, how many people using Mesos access the UI over a tunnel? > Is > > > there any harm in reverting this functionality to how it was in the > 1.0.x > > > days? I'm sure there was some important reason as to why this change > was > > > made, I'm just not aware of it. From my understanding many of the ops > > folks > > > in our org use the UI but almost always over a tunnel. Once more groups > > in > > > the org upgrade to newer versions of Mesos they will be facing this > issue > > > almost on a daily basis. > > > > > > Thanks, > > > Aaron > > > > > > On Mon, Sep 11, 2017 at 2:59 PM, Benjamin Mahler <bmah...@apache.org> > > > wrote: > > > > > > > Hi folks, > > > > > > > > Over time the webui has lagged behind for some of the features that > > have > > > > been added. I'm currently tracking what's required to catch it up > here: > > > > > > > > https://issues.apache.org/jira/browse/MESOS-6440 > > > > > > > > If you know of other features that make sense to display in the > webui, > > > feel > > > > free to file a ticket under this epic (or link it as related if it > > falls > > > > under a different epic) and let me know. For example, I just filed > > > another > > > > one within it for displaying task health information. > > > > > > > > Also feel free to make contributions to the webui even if you don't > > feel > > > > that you're knowledgable on the frontend side of things. The majority > > of > > > > webui changes are very easy and provide a lot of value to users who > > > > interact with it on a regular basis! > > > > > > > > If you'd like to contribute to the webui, there are a lot of easy > > tickets > > > > to get started with, here is one example that I would be happy to > > assist > > > > with: https://issues.apache.org/jira/browse/MESOS-7962 > > > > > > > > Thanks! > > > > Ben > > > > > > > > > >
