Common problems with Deployments

On a component, or on the Deployments page

What you see	What to do
No Deployments tab, no Deployments card, no key Deployments in Add a card	Turn on Deployments in Administration › Plugins.
shop-web shows no Argo CD deployment: its argocd/app-selector annotation ("env=prod") does not contain its name. Remove this annotation to use the label backstage.io/component (the applications that carry backstage.io/component=shop-web), or write: argocd/app-selector: backstage.io/component=shop-web. in the Deployments card of the Overview	Remove the argocd/app-selector annotation from the catalog-info.yaml of the component. The component is then linked to the applications that carry the component label with its name.
The Argo CD application shop-pay-recette belongs to shop-pay but appears in no environment. In Argo CD, add the label environment to this application, with the name of its environment as the value (for example environment=prod). The label to look for is the "Environment label" setting of Administration › Deployments. in the Deployments card of the Overview	In Argo CD, add the environment label named in the message to the application named in the message, with the name of its environment as the value, for example environment: prod.
No Argo CD application of admin-api was found. In Argo CD, add the label backstage.io/component with the value admin-api to each of its applications. The label to look for is the "Component label" setting of Administration › Deployments. in the Deployments card of the Overview	In Argo CD, add the label named in the message, with the name of the component as the value, to each application of the component, for example backstage.io/component: admin-api. Check that the label named in the message is the one your applications carry: it is the Component label setting of Administration › Plugins › Deployments.
Argo CD (argocd-prod) refuses the connection.	Check the host and port of that Argo CD in Administration › Company connections, and that it runs. The other Argo CD keep showing their versions.
Argo CD is not connected to Astrolabe yet.	Add your Argo CD in Administration › Company connections: click Open the Argo CD integration.
Nothing here yet and No deployment is recorded yet for a component of the catalog. in the Deployments card of My Dashboards	No pipeline has reported a deployment yet. Report one: see Report deployments from your pipelines.
Nothing deployed yet	With Argo CD: read the message above the card, it names the label to add. With a pipeline: no deployment has been reported under the name of the component.
Astrolabe's server failed to answer (503).	Try again in a moment. If it lasts, tell your company's Astrolabe administrator what you were doing.
No deployment has been reported yet. on the Deployments page	No pipeline has reported a deployment. As an administrator, click Report deployments from your pipelines under the sentence and follow Report deployments from your pipelines. Anyone else asks an administrator: the page says An administrator generates the token your pipelines report deployments with.
No results with these filters on the Deployments page	Clear Search a component, or click Clear filters.

In the Deployments settings

What you see	What to do
"mon env" is not accepted. under Environment label or Component label	A label is written without spaces or accents, for example env or app.kubernetes.io/environment.
Still waiting for: integrations.argocd	No Argo CD is connected yet: add one in Administration › Company connections.

When a pipeline reports a deployment

The pipeline's call answers with one of these messages; read them in the log of the job.

What you see	What to do
A pipeline token is required: generate one in Administration › Plugins › Deployments › Configure › Pipeline token and send it as « Authorization: Bearer <token> ».	The call carries no token. Check that the job sees the ASTROLABE_PIPELINE_TOKEN secret (protected branches, environments of your CI), and that the call sends the Authorization line.
This pipeline token is not valid: it was replaced or revoked. Generate a new one in Administration › Plugins › Deployments › Configure › Pipeline token.	The token was replaced or revoked. Generate a new one and put it in the ASTROLABE_PIPELINE_TOKEN secret: see Report deployments from your pipelines.
No component named shop-api in the catalog: COMPONENT must be the name of a component of the catalog.	COMPONENT holds a name the catalog doesn't know. Use the name of the component, as in metadata.name of its catalog-info.yaml.
version is required	VERSION is empty in the job: give it the version deployed.
The call succeeds but the component shows Nothing deployed yet	Check that COMPONENT is the name of the component, as in metadata.name of its catalog-info.yaml, and that you look at the same environment.

When you add an Argo CD

What you see	What to do
argocd.example.com refused the credentials (401). Check the token, and that it has not expired.	Create a new Argo CD API token: see Create an Argo CD API token.

Still stuck?

Write to support@forgeit.fr with the name of the component.