Troubleshooting for Continuous Delivery

Why are users added back to the authorized user list after I remove them?

Users or their accesses were not removed from all locations.

A user that you removed from the authorized user list was added to the list again.

You didn't remove the user or their access from all of the Continuous Delivery instances, toolchains, or the Git Repos and Issue Tracking repos that are attached to all of the toolchains in the resource group.

To remove authorized users and prevent them from being added again, complete the following steps:

• Remove the user's access in IAM to all toolchains in the resource group.
• Remove the user from the authorized user list in the Continuous Delivery instance.
• Remove Developer access from all Git Repos and Issue Tracking repos that are attached to all of the toolchains in the resource group.

You can maintain an activity log related to authorized users. For more information, see IBM Cloud Activity Tracker Event Routing events and Authorized users.

Why do I not have the option to enable consolidate billing for my Continuous Delivery instance?

The Consolidated billing tab isn't included in the Manage options for your Continuous Delivery instance.

The instance is not included in an enterprise account, and it is not using the Professional plan. You can enable consolidated billing only for instances with the Professional plan in an enterprise account.

If the instance is in an enterprise account, upgrade the instance to the Professional plan. If the instance is not included in an enterprise account, complete the following steps:

1. Switch to the enterprise account of the enterprise in which you want to manage consolidated billing.
2. Create or select an instance to configure consolidated billing. For more information, see Consolidated billing.

Even though you can't enable consolidated billing for instances that aren't included in an enterprise account, you can still take advantage of consolidate billing as long as the following conditions are true:

• The instance is included in a child account of the enterprise.
• The instance is in the same region as the instance in which consolidated billing is enabled at the enterprise account level.

Why do I get an error about Lite plan limits when I try to run a pipeline?

The pipeline that you started failed with an error message.

You exceeded the 500-step and job run limit that includes both pipeline steps for Tekton pipelines and pipeline job runs for Classic pipelines. If your pipeline has many steps within a single run, such as with the DevSecOps pipelines, you might reach this limit quickly.

Delivery pipeline failures, excluding skipped step runs and Classic job runs, are counted as part of the 500-step run limit per month. All of your toolchains and all of your pipelines within those toolchains that are in the same resource group contribute to the same limit of 500 Tekton step runs per month. The same limit is used because pipeline step runs and job runs are counted at the resource group level for a specific Continuous Delivery instance.

A five-day grace period is offered the first time that you reach the 500-step run limit. If you regularly exceed the 500-step run limit within a billing period, it is recommended that you update the Continuous Delivery instance for that resource group and region to use a Professional plan.