Commit afc76744 authored by Nick Thomas's avatar Nick Thomas

Fix reading the status of a secondary Geo node from the primary

parent bd7ba308
...@@ -11,8 +11,10 @@ module Geo ...@@ -11,8 +11,10 @@ module Geo
repositories_failed_count repositories_failed_count
lfs_objects_count lfs_objects_count
lfs_objects_synced_count lfs_objects_synced_count
lfs_objects_failed_count
attachments_count attachments_count
attachments_synced_count attachments_synced_count
attachments_failed_count
last_event_id last_event_id
last_event_date last_event_date
cursor_last_event_id cursor_last_event_id
......
---
title: Fix reading the status of a secondary Geo node from the primary
merge_request: 3140
author:
type: fixed
...@@ -6,6 +6,26 @@ describe Geo::NodeStatusService do ...@@ -6,6 +6,26 @@ describe Geo::NodeStatusService do
subject { described_class.new } subject { described_class.new }
describe 'KEYS' do
it 'matches the serializer keys' do
exceptions = %w[
id
healthy
repositories_synced_in_percentage
lfs_objects_synced_in_percentage
attachments_synced_in_percentage
]
expected = GeoNodeStatusEntity
.new(GeoNodeStatus.new)
.as_json
.keys
.map(&:to_s) - exceptions
expect(described_class::KEYS).to match_array(expected)
end
end
describe '#call' do describe '#call' do
it 'parses a 401 response' do it 'parses a 401 response' do
request = double(success?: false, request = double(success?: false,
...@@ -27,8 +47,10 @@ describe Geo::NodeStatusService do ...@@ -27,8 +47,10 @@ describe Geo::NodeStatusService do
repositories_failed_count: 2, repositories_failed_count: 2,
lfs_objects_count: 100, lfs_objects_count: 100,
lfs_objects_synced_count: 50, lfs_objects_synced_count: 50,
lfs_objects_failed_count: 12,
attachments_count: 30, attachments_count: 30,
attachments_synced_count: 30, attachments_synced_count: 30,
attachments_failed_count: 25,
last_event_id: 2, last_event_id: 2,
last_event_date: Time.now, last_event_date: Time.now,
cursor_last_event_id: 1, cursor_last_event_id: 1,
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment