Subscription certificate expires less than its contract period on Red Hat Satellite 6.

Issue

• There is a 4 or 5 hour gap in the time a subscription expires and the future dated one starts.
• Subscription Management issues a subscription certificate file from EST midnight to UTC midnight as the following available period:

example:
+-------------------------------------------+
        Entitlement Certificate
+-------------------------------------------+

Certificate:
        Path: 7100000000000000000.pem
        Version: 3.3
        Serial: 7100000000000000000
        Start Date: 2019-01-16 05:00:00+00:00  <== ***
        End Date: 2020-01-15 23:59:59+00:00   <== ***
        Pool ID: 8a850123012301230123012301230123

• This means that the old certificate will expires without waiting for the next new subscription to start provided if this subscription is renewed. Hence, this makes 5 hours downtime for Content Hosts registered with Red Hat Satellite 6 to again consume the correct renewed subscription.