✔ Post upgrade testing
Completed by Robyn
- Assigned to
-
David M.
- Due on
- Notes
-
The DSI Drupal development environment is scheduled for a major infrastructure upgrade between 10pm Tuesday October 8th and 6am Wednesday October 9th.
What’s Changing
Development and staging environments on the umnd908 subscription will be upgraded to new Kubernetes-based auto-scaling infrastructure for improved performance, security, and resiliency.If you own multiple sites, you can determine which are impacted by using the subscription filter on the Drupal Management website homepage.
What’s Impacted
Non-production environments will be unavailable for up to 30 minutes during this upgrade window.
Action Required
Pre-Upgrade
To ensure your upgrade goes smoothly, any major development efforts will need to be paused, including code changes or large additions to your file system or database beginning at 10pm Monday October 7th until after the upgrade is complete. We will disable code deployments to these environments during this pre-upgrade window to prevent disruption from code changes.
Post-Upgrade Testing
This is a significant change and we recommend that you test as soon as possible in your lower environments. The vendor allows a 7 calendar day testing window after the dev and stage upgrade is complete. If you find any issues, please report them to ucm@umn.edu immediately.Based on our standard testing rubric, we recommend level 4 testing for this change. The vendor provides specific testing guidance for this upgrade that you should review as well. The OIT Drupal team will use test sites with standard configurations to perform our own testing. If you have site-specific code or customizations (i.e. you have configured image styles to use webp), you should test accordingly.
Production Upgrades
After the 7 day testing window, the vendor will schedule the production upgrade for approximately one week out, for a total of two weeks after dev/stg sites are upgraded. The vendor will select the specific dates and times based on their availability, but the upgrades will occur outside of business hours. We will communicate the specific date and time window for production as soon as we are informed by the vendor.If you have any questions or concerns, please contact the OIT Drupal Support team at ucm@umn.edu.
Noted Accessibility issues:
Some links open in a new tab - this is being flagged _ I fixed some to test but the work needs to happen on the production site ( I needed to edit and update stuff so chose that for testing) but not doing them all - The directory is one I am not sure how to fix as all the directory links open up in a new tab, something to consider for production / when we work on the next phase
Headings
Our prototype has larger text to emphasise certain aspects but our heading levels needed to make that happen throw out errors for two reasons - we start with a smaller heading and then go with the larger font (like the design) but that's flagged as not following a logical process.
The next flag is that we are using the heading feature to bold and size things and that's then being flagged a bad heading (too long and not in line with how headings should work)
What, if anything, is our plan for this.
Events calendar
It is a problem on production too but the mobile view of the events calendar is not right - the layout is weird and the options are teeny tiny - it actually works fine on my phone so maybe a couple of us can just check on the actual phone and move on
The one issue was the events menu was missing entirely from the site. as if it was an older version of the database. Something to keep an eye on