diff --git a/doc/source/_extra/.htaccess b/doc/source/_extra/.htaccess
index c277bb51..69bab3d7 100644
--- a/doc/source/_extra/.htaccess
+++ b/doc/source/_extra/.htaccess
@@ -9,3 +9,4 @@ Redirect 301 /specs/queens/approved/glance/remove-registry-v1.html /specs/rocky/
 Redirect 301 /specs/queens/approved/glance/remove-v1.html /specs/rocky/approved/glance/remove-v1.html
 Redirect 301 /specs/mitaka/approved/image-import/image-import-refactor.html /specs/rocky/approved/glance/image-import/image-import-refactor.html
 Redirect 301 /specs/queens/approved/python-glanceclient/no-schema-validation.html /specs/untargeted/python-glanceclient/no-schema-validation.html
+Redirect 301 /specs/untargeted/glance/lite-spec-db-sync-check.html /specs/queens/implemented/glance/lite-spec-db-sync-check.html
diff --git a/doc/test/redirect-tests.txt b/doc/test/redirect-tests.txt
index bbe1f03a..2f4505cd 100644
--- a/doc/test/redirect-tests.txt
+++ b/doc/test/redirect-tests.txt
@@ -10,3 +10,4 @@
 /specs/queens/approved/glance/remove-v1.html 301 /specs/rocky/approved/glance/remove-v1.html
 /specs/mitaka/approved/image-import/image-import-refactor.html 301 /specs/rocky/approved/glance/image-import/image-import-refactor.html
 /specs/queens/approved/python-glanceclient/no-schema-validation.html 301 /specs/untargeted/python-glanceclient/no-schema-validation.html
+/specs/untargeted/glance/lite-spec-db-sync-check.html 301 /specs/queens/implemented/glance/lite-spec-db-sync-check.html
diff --git a/specs/untargeted/glance/lite-spec-db-sync-check.rst b/specs/queens/implemented/glance/lite-spec-db-sync-check.rst
similarity index 56%
rename from specs/untargeted/glance/lite-spec-db-sync-check.rst
rename to specs/queens/implemented/glance/lite-spec-db-sync-check.rst
index eff9c9a5..5c97bcb1 100644
--- a/specs/untargeted/glance/lite-spec-db-sync-check.rst
+++ b/specs/queens/implemented/glance/lite-spec-db-sync-check.rst
@@ -1,26 +1,30 @@
-Lite Spec: Introduce db sync --check feature
---------------------------------------------
-
-:problem: It is very hard for automation of deploy and upgrade operations to
-          know if there are db migrations pending. It requires the automation
-          to know what the latest version is, and compare that to the output
-          of a command to check the current version, then interpret the
-          potential difference somehow.
-
-:solution: Similar to the linked feature added to Keystone's manage command,
-           Glance should support an operation which enumerates any outstanding
-           db upgrade operations and provide a distinct return code based on
-           that status. Each expand, migrate, and contract operation required
-           to upgrade the db should be listed in the proper order of execution
-           in the response. For consistency with Keystone, this may be
-           implemented by using a ``--check`` option. When this option is
-           present no db upgrades would be performed but potential operations
-           would be reported, acting similar to the pattern of a dry-run.
-
-:impacts: Introduces new option to the db sync operation in glance-manage.
-
-:timeline: Expected to be merged within the Pike time frame.
-
-:link: https://bugs.launchpad.net/keystone/+bug/1642212
-
-:assignee: Open
+==========================================
+Spec Lite: Introduce db sync check feature
+==========================================
+
+:problem: It is very hard for automation of deploy and upgrade operations to
+          know if there are db migrations pending. It requires the automation
+          to know what the latest version is, and compare that to the output
+          of a command to check the current version, then interpret the
+          potential difference somehow.
+
+:solution: Similar to the linked feature added to Keystone's manage command,
+           Glance should support an operation which enumerates any outstanding
+           db upgrade operations and provide user friendly message based on
+           that status. Each expand, migrate, and contract operation required
+           to upgrade the db should be listed in the proper order of execution
+           in the response.
+           This may be implemented by using a ``glance-manage db check`` option.
+           When this option is present no db upgrades would be performed
+           but potential operations would be reported, acting similar to the
+           pattern of a dry-run.
+
+:impacts: Introduces new option to the db sync operation in glance-manage.
+
+:timeline: Queens RC-1
+
+:link: https://bugs.launchpad.net/keystone/+bug/1642212
+
+:reviewers: rosmaita, abhishekk, jokke
+
+:assignee: bhagyashris
\ No newline at end of file