Project

General

Profile

Bug #25712

Can't log into the New GUI after updating to FreeNAS-11.0-INTERNAL2-U3 (164236f50)

Added by Bonnie Follweiler over 3 years ago. Updated over 3 years ago.

Status:
Resolved
Priority:
Important
Assignee:
Vaibhav Chauhan
Category:
GUI (new)
Target version:
11.0-U3
Seen in:
11.0-U3
Severity:
New
Reason for Closing:
Reason for Blocked:
Needs QA:
No
Needs Doc:
Yes
Needs Merging:
Yes
Needs Automation:
No
Support Suite Ticket:
n/a
Hardware Configuration:
ChangeLog Required:
No

Description

After updating to FreeNAS-11.0-INTERNAL2-U3 (164236f50) I have no option to log in after selecting "Demo our Upcoming UI". It just continues to look like it is loading.

Screen Shot 2017-08-28 at 1.46.27 PM.png (139 KB) Screen Shot 2017-08-28 at 1.46.27 PM.png Bonnie Follweiler, 08/28/2017 10:49 AM
12314

History

#1 Updated by Bonnie Follweiler over 3 years ago

  • Assignee changed from Anonymous to Lola Yang

#2 Updated by Bonnie Follweiler over 3 years ago

Upgraded to FreeNAS-11.0-INTERNAL3-U3 (1a9dc159a) and I still can't access the login for the new GUI

#3 Updated by Lola Yang over 3 years ago

  • Status changed from Unscreened to Screened
  • Target version set to 11.1

#4 Updated by Lola Yang over 3 years ago

  • Assignee changed from Lola Yang to Vaibhav Chauhan
  • Target version changed from 11.1 to 11.0-U3

giving this to vb since this issue is related to release processes (need a full build before releasing a new version)...

#5 Updated by Vaibhav Chauhan over 3 years ago

so I am doing a completely new build, maybe this is related to stale npm_modules we will soon figure it out.

#6 Updated by Bonnie Follweiler over 3 years ago

Just keeping you updated: I installed FreeNAS-11.0-INTERNAL4-U3 (1a9dc159a) on a brand new VM and I also upgraded hardware and still can't access the new GUI

#7 Updated by Vaibhav Chauhan over 3 years ago

while we were able to fix the GUI build we were encountered with an entirely different issue

I am building new internal which should fix this ticket,

#8 Updated by Vaibhav Chauhan over 3 years ago

Nope last ISO did not, still working with erin and team on this issue.

#9 Updated by Vaibhav Chauhan over 3 years ago

  • Status changed from Screened to 47
  • Assignee changed from Vaibhav Chauhan to Bonnie Follweiler
  • Priority changed from No priority to Important

we have fixed the issue which was breaking the UI, please confirm on your end.

#10 Updated by Dru Lavigne over 3 years ago

  • Private changed from No to Yes

#11 Updated by Bonnie Follweiler over 3 years ago

  • Status changed from 47 to Ready For Release

#12 Updated by Dru Lavigne over 3 years ago

  • Status changed from Ready For Release to Resolved

#13 Updated by Vaibhav Chauhan over 3 years ago

  • Status changed from Resolved to Ready For Release

we set resolve only when we release the software update. release engineer generally sets it to reolve.

#14 Updated by Vaibhav Chauhan over 3 years ago

  • Status changed from Ready For Release to Resolved

#15 Updated by Bonnie Follweiler over 3 years ago

  • Needs QA changed from Yes to No
  • QA Status Test Passes added
  • QA Status deleted (Not Tested)

#16 Updated by Joe Maloney over 3 years ago

  • Assignee changed from Bonnie Follweiler to Vaibhav Chauhan

#17 Updated by Dru Lavigne over 3 years ago

  • Private changed from Yes to No

Also available in: Atom PDF