SaaS Trial Plan IDs Break Billing When Namespace is trial: false
Coming from a report mentioned here: https://gitlab.com/gitlab-org/customers-gitlab-com/-/issues/3378#note_705165325
Summary
If a namespace on GitLab.com loses trial status while on plan ultimate_trial
or premium_trial
, the group's billing page encounters an error
The GitLab subscription service (customers.gitlab.com) is currently experiencing an outage. You can monitor the status and get updates at status.gitlab.com.
As a generic example, the following will cause the billing page to break:
id 10198535
name trainspotting
path trainspotting2
members_count_with_descendants 1
extra_shared_runners_minutes_limit
shared_runners_minutes_limit
billable_members_count 1
plan premium_trial
trial_ends_on
trial false
plan: premium_trial
trial: false
Per @jagood this should not be a state that a namespace winds up in, and it seems not very widespread. But I did encounter a customer group that was in this state.
Customer is on trial Order id 210574
. Sales requested an extension on the end_date, which you can see I did in the paper trial. Before I made any changes, the namespace on GitLab was trial: false
, yet still linked to the ultimate_trial
plan, breaking billing page.
We should investigate how it may have happened.
Also, maybe we address the source of the error? Specifically, why does FetchSubscriptionPlansService#send_request end in error when ultimate_trial
/ premium_trial
and trial:false
?
Steps to reproduce
Via GitLab admin, set any group to either ultimate_trial
or premium_trial
.
What is the current bug behavior?
Namespace billing page returns an error
Workarounds
- Remove
ultimate_trial
orpremium_trial
plan from the namespace - set the namespace to
trial: true