GovCMS: Content management and website hosting for the Australian government. Managed by the Department of Finance with service delivery partners Salsa Digital and amazee.io
We are conducting regular maintenance on our systems.
This maintenance window will include activities for the GovCMS logs infrastructure. As such there will be intermittent interruptions to logs and dashboard access throughout this window. Posted on
Oct 15, 2024 - 07:00 AEDT
Completed -
The scheduled maintenance has been completed.
Oct 18, 17:10 AEDT
Update -
Deployment of D10 3.18.0 to production environments has been completed. The deployment block has now been lifted. We are now commencing deployments on non-production environments.
Oct 16, 13:32 AEDT
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Oct 16, 06:00 AEDT
Scheduled -
Advice - Who is affected: GovCMS Drupal 10 (D10) community. - Distribution was updated on Tuesday 15 October 2024 . - No modules were added/removed from the distribution - No outages are expected to websites during the deployment process. - The D10 distribution will continue to be supported after this update. - If you have any concerns, raise a ticket at https://www.govcms.support
Deployment schedule plan: - Commence from 6:00AM (AEDT) Wednesday 16 October 2024 - Production branches completed by 10:00 AM (AEDT) Thursday 17 October 2024 - Once production branches are completed, status page will be updated and Non-Production branches will kick off - Non-Production branches should be completed by 10:00 AM (AEDT) Friday 18 October 2024
❗ IMPORTANT NOTICE 1: Deployments during maintenance window - During the scheduled maintenance window, ALL D10 SaaS deployments will be blocked while we deploy to the D10 Production branches. - While the production block is on, you will still be able to develop and deploy to non-production feature branches. - PaaS deployments schedules are not impacted.
❗ IMPORTANT NOTICE 2: Update local environments - Ensure you update your local environments to the latest release. Not rebasing your codebase results in mismatched database configuration causing errors in forklifts and deployments.
❗ IMPORTANT NOTICE 3: For customers with configuration management enabled - The latest configuration from your production database has been created for you in GitLab in a branch called action-required/latest-config-export. - You need to review and test the changes in the merge request. Once you are satisfied, please check the “Delete source branch” box and click “Merge”. - This MUST be done before any new commits. - All subsequent deployments will be blocked in the CI pipeline until this merge request branch is deleted - Not merging the latest configuration provided could result in your new database configuration reverting to an older version when you next deploy, potentially causing issues for your website. - If no merge request is lodged after a release then no configuration has changed and no further action is required.
Information for PaaS customers Update your codebase to ensure you are running the latest platform base images and packages, and stay aligned to GovCMS best practice: GovCMS D10 distribution - includes a module update addressing Drupal security vulnerability - updated files will be released on Tuesday 15 October 2024 - available from https://github.com/govCMS/GovCMS/releases/tag/3.18.0. - you should aim to apply this update to your distribution as soon as possible.
Completed -
The scheduled maintenance has been completed.
Oct 16, 06:00 AEDT
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Oct 15, 23:00 AEDT
Scheduled -
We are conducting regular maintenance on our systems.
In addition to the regular maintenance, GovCMS will be updating the MySQL version for the production database clusters from MySQL 5.7 compatible to MySQL 8.0 compatible during this infrastructure maintenance window. This maintenance is being scheduled out of business hours to minimise the impact for your application.
During this time, there will be an impact of up to one hour to the production database services. Any content editing activities for production sites will be impacted and we advise that such work not be scheduled during this maintenance window.
Oct 8, 07:00 AEDT
Completed -
The scheduled maintenance has been completed.
Oct 15, 08:00 AEDT
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Oct 15, 06:00 AEDT
Scheduled -
Due to issues encountered outside of the release, introduction of Lagoon 2.21.0 was unable to occur during the maintenance window dated October 14th. It has instead been re-scheduled for this window.
During this window, we will be upgrading Lagoon to the latest version of 2.21.0. No disruptions to the sites running are expected. There may be delays to new builds, or partial outages in the GraphQL API to Lagoon during this time.
Oct 14, 14:10 AEDT
Completed -
The scheduled maintenance has been completed.
Oct 14, 08:00 AEDT
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Oct 14, 06:00 AEDT
Scheduled -
We will be upgrading Lagoon to the latest version of 2.21.0. No disruptions to the sites running are expected. There may be delays to new builds, or partial outages in the GraphQL API to Lagoon during this time.
Sep 26, 10:32 AEST
Completed -
The scheduled maintenance has been completed.
Oct 11, 15:21 AEDT
Update -
Deployment of D10 3.17.1 is complete for production sites and is now commencing on non-production sites. The deployment block has now been lifted.
Oct 10, 14:07 AEDT
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Oct 9, 06:00 AEDT
Scheduled -
Advice GovCMS will release the Drupal 10 (D10) distribution on Tuesday 8 October 2024. Deployment is scheduled to commence from 6:00am Wednesday 9 October 2024 and will be conducted throughout the day. No outages are expected to websites during the deployment process.
It addresses a recent security advisory issued by Drupal.org. GovCMS assessed the critical risk as they applied to D10 distribution, subsequently the security residual risk remained critical. The D10 distribution will continue to be supported after this update
Deployment schedule plan: - Production branches completed by 10:00am (AEST) Thursday 10 October 2024. - Non-Production branches completed by 10:00am (AEST) Friday 11 October 2024. - PaaS deployments schedules are not impacted.
PaaS Actions Update your codebase to ensure you are running the latest platform base images and packages and stay aligned to GovCMS best practice:
GovCMS D10 distribution: - includes module updates addressing Drupal security vulnerabilities. - updated files will be released on Tuesday 8 October 2024 - available from GitHub release tag 3.17.1 (https://github.com/govCMS/GovCMS/releases/tag/3.17.1)
SaaS Actions ❗ IMPORTANT NOTICE 1: Deployments during maintenance window - During the scheduled maintenance window, ALL D10 SaaS deployments will be blocked while we deploy to the D10 Production branches. - While the production block is on, you will still be able to develop and deploy to non-production feature branches. - PaaS deployments schedules are not impacted.
❗ IMPORTANT NOTICE 2: Update local environments - Ensure you update your local environments to the latest release. Not rebasing your codebase results in mismatched database configuration causing errors in forklifts and deployments.
❗ IMPORTANT NOTICE 3: For customers with configuration management enabled - The latest configuration from your production database has been created for you in GitLab in a branch called action-required/latest-config-export. - You need to review and test the changes in the merge request. Once you are satisfied, please check the “Delete source branch” box and click “Merge”. - This MUST be done before any new commits. - All subsequent deployments will be blocked in the CI pipeline until this merge request branch is deleted - Not merging the latest configuration provided could result in your new database configuration reverting to an older version when you next deploy, potentially causing issues for your website. - If no merge request is lodged after a release then no configuration has changed and no further action is required.
Oct 4, 12:26 AEST