GitLab keeps showing an old broadcast message from last year after upgrade

Summary

GitLab keeps showing an old broadcast message from last year at the top of all pages after being upgraded from 11.8.0 directly to 11.10.4

Steps to reproduce

Not certain. Maybe upgrading from 11.8.0 directly to 11.10.4

Example Project

N/A

What is the current bug behavior?

An old message from last year is displayed at the top. The message is not listed in the Broadcast Messages and, what's more, the style of the message is quite different from that of the Broadcast Messages.

What is the expected correct behavior?

The message is not supposed to be there.

Relevant logs and/or screenshots

Screen_Shot_2019-05-12_at_1.23.27_AM

Output of checks

Results of GitLab environment info

Expand for output related to GitLab environment info 
System information
System:		Debian 9.5
Proxy:		no
Current User:	git
Using RVM:	no
Ruby Version:	2.5.3p105
Gem Version:	2.7.6
Bundler Version:1.17.3
Rake Version:	12.3.2
Redis Version:	3.2.12
Git Version:	2.18.1
Sidekiq Version:5.2.5
Go Version:	go1.7.4 linux/amd64


GitLab information
Version:	11.10.4-ee
Revision:	88a3c791734
Directory:	/opt/gitlab/embedded/service/gitlab-rails
DB Adapter:	PostgreSQL
DB Version:	9.6.11
Elasticsearch:	yes
Geo:		no
Using LDAP:	yes
Using Omniauth:	yes
Omniauth Providers:


GitLab Shell
Version:	9.0.0
Repository storage paths:
  • default: /var/opt/gitlab/git-data/repositories GitLab Shell path: /opt/gitlab/embedded/service/gitlab-shell Git: /opt/gitlab/embedded/bin/git

Results of GitLab application Check

Expand for output related to the GitLab application check 
all yeses


...
Redis version >= 2.8.0? ... yes
Ruby version >= 2.5.3 ? ... yes (2.5.3)
Git version >= 2.18.0 ? ... yes (2.18.1)
Git user has default SSH configuration? ... yes
Active users: ... 678
Elasticsearch version 5.6 - 6.x? ... yes (6.7.1)


Checking GitLab App ... Finished


Checking GitLab subtasks ... Finished

Possible fixes

N/A