[STCOR-504] Cannot get to folio-testing Created: 18/Jan/21  Updated: 25/Feb/21  Resolved: 20/Jan/21

Status: Closed
Project: stripes-core
Components: None
Affects versions: None
Fix versions: 7.0.0

Type: Bug Priority: P1
Reporter: Ann-Marie Breaux (Inactive) Assignee: Michal Kuklis
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Relates
relates to STCOR-505 restore ProfileDropdown.createLink Closed
Sprint:
Story Points: 8
Development Team: FOLIO DevOps

 Description   

Please resolve ASAP so that final testing for last sprint and prep for Tuesday sprint demo can proceed. Note that most US community members have a holiday on Monday 18 Jan.

Overview: Cannot get to folio-testing homepage

Steps to Reproduce:

  1. Log into https://folio-testing.dev.folio.org/ as diku_admin

Expected Results: After login the homepage is displayed
Actual Results: Page is blank

Additional Information: Per David Crossley: "I can get to the login screen. However after providing the credentials, there is a blank page. The web browser JavaScript console shows errors which seem to be related to “ProfileDropdown component”. Dunno - out of my depth."



 Comments   
Comment by Zak Burke [ 18/Jan/21 ]

I tried to cram in some API changes on Friday before the (original) Iris API freeze date. They were tested successfully in local workspaces but failed in all sorts of interesting ways when I started committing the PRs.

Comment by Ann-Marie Breaux (Inactive) [ 19/Jan/21 ]

can you roll them back Zak Burke? Would that also fix the settings and other problems we're seeing on snapshot? (mentioned by Darcy Branchini and Khalilah Gambrell)

Comment by Zak Burke [ 19/Jan/21 ]

Ann-Marie Breaux, I can roll them back but it won't likely fix the UI glitches we are seeing elsewhere. Those, I believe, are related to specific stripes-components changes and folks are working on them separately.

I'm trying to figure out the best way forward here. I realize the timing is extremely poor and I own that. The combination of Friday being the last day (in the original schedule) to commit API changes, plus Monday being a holiday, plus Tuesday being sprint-demo day was a triple-whammy I was ill-prepared for.

Comment by Ann-Marie Breaux (Inactive) [ 19/Jan/21 ]

I guess folks can demo from their rancher or local environments if unable in the hosted ref envs. I'll send a note to the POs.

Comment by Zak Burke [ 19/Jan/21 ]

Ann-Marie Breaux, folio-testing is back in full. We can rebuild folio-snapshot with the same changes if folks want.

Comment by Zak Burke [ 19/Jan/21 ]

FTR, I am trying to roll this back but I am seeing test failures on the old branches with the old yarn.lock files. In theory, this is exactly what lock files are designed to prevent, so I'm kinda stumped because I can't seem to move either forward or backward. I will continue to update this ticket if/when there is real progress to report.

Comment by Zak Burke [ 20/Jan/21 ]

Roll back complete. Hat tip to Aditya matukumalli and Michal Kuklis who actually did the hard part and figured out what the problem was (details at STRIPES-722 Closed ). All I did was revert some PRs.

Comment by Ann-Marie Breaux (Inactive) [ 20/Jan/21 ]

Thanks to all of you @zak Aditya matukumalliMichal Kuklis - glad that it was in decent shape for the demo. Hopefully the next updates will go more smoothly!

Comment by md331 (Inactive) [ 20/Jan/21 ]

Spurned on by today's discussion in #stripes, I'm gonna take this opportunity to mention for posterity that outages like this happen because we have nobody allocated to keeping Stripes and our infrastructure on the rails. Large, important upgrades seem to happen only when devs are annoyed enough and manage to sneak work into days/hours that were somehow freed up for them.

We can expect more cases like this as long as the status quo remains.

Generated at Thu Feb 08 23:24:36 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.