Jameson McGhee

I was able to reproduce this issue on v2.6.2 (see v2.6.2 Screenshot and Repro Steps). I then upgraded Rancher to v2.6-head (Commit ID: 400e559), and the issue did not reproduce....

I attempted to reproduce this issue on both v2.6.7 and v2.6-head (Commit ID: 400e559), and I was unable to reproduce this issue on either version. Based on that fact, @nwmac's...

@aalves08, this issue is still reproducing on v2.6-head commit ID db2205a. Setting this ticket to Reopened. 

@aalves08 @richard-cox @gaktive I just spun up a brand new Rancher server on v2.6-head with Commit ID cd97f6f and did my testing on Google Chrome using the most recent version...

I have confirmed that the Namespace dropdown issue can be reproduced in v2.6.6. 

**Intended Test Setup** - Rancher version(s): v2.6-head - Browser type & version: Brave & Most Current - Rancher Host: EC2 (Jenkins Job) - Rancher Setup: o RANCHER_HA_CERT_OPTION: byo-valid o RKE_VERSION:...

/backport v2.6.9

I was able to reproduce this issue on v2.6.7 by following the Steps to Reproduce. However, following the Steps to Reproduce on v2.-7head (Commit ID: c567ef3), this issue was no...

During testing on v2.6-head (Commit ID: 2e00266) while following the Steps to Reproduce, I did not observe the timeout error (See Logs: [38916TestLogs.txt](https://zube.io/files/rancher/87123df2a61d746426fc1a41260b55cd-38916testlogs.txt)). Based on this, as well as the...

**jameson-mcghee said:** When testing v2.6.7 and on v2.7-head (Commit ID: 314e690) using the following Steps to Reproduce, I did not observe the issue. All clusters that I attempted to reproduce...