Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

34_deploy_controlplane_target.sh creates extra control plane #141

Closed
rkjain opened this issue May 10, 2021 · 5 comments
Closed

34_deploy_controlplane_target.sh creates extra control plane #141

rkjain opened this issue May 10, 2021 · 5 comments
Assignees
Labels
2-Manifests Relates to manifest/document set related issues bug Something isn't working size l 5-7+ days [multiple functional areas; complex function or capability, or multiple PSs]
Milestone

Comments

@rkjain
Copy link

rkjain commented May 10, 2021

Description
./tools/deployment/34_deploy_controlplane_target.sh creates an extra control plane node that remains in provisioning state.

Steps To Reproduce
use v2.0 branch of airshipctl and treasuremap, and followed the site authoring/deployment guide to create 6 node cluster in ericsson lab.

airship@as2-1-r:~$ sudo kubectl  --kubeconfig /home/airship/.airship/kubeconfig --context target-cluster get machines
NAME                         PROVIDERID                                      PHASE
cluster-controlplane-22977   metal3://dd33ef25-a348-462a-b125-e20c6a52f1bd   Running
cluster-controlplane-9dg7s                                                   Provisioning
cluster-controlplane-gjvvr   metal3://7365c9e8-8322-4969-8db7-916c0f00760b   Running
cluster-controlplane-nqv7p   metal3://136a085a-fae8-412d-a4bf-dd331a533437   Running
worker-1-5bc87ff868-2x5qz    metal3://534c9542-3250-4806-9f70-2552c75f964e   Running
worker-1-5bc87ff868-6tjhh    metal3://32292183-6617-450e-a230-ed4ac02369dd   Running
worker-1-5bc87ff868-dwg5z    metal3://fde274cb-cf6e-42ff-b5ca-32ca7310e9d0   Running

Expected behavior
There should only be 3 control planes

airship@as2-1-r:~$ sudo kubectl  --kubeconfig /home/airship/.airship/kubeconfig --context target-cluster get machines
NAME                         PROVIDERID                                      PHASE
cluster-controlplane-22977   metal3://dd33ef25-a348-462a-b125-e20c6a52f1bd   Running
cluster-controlplane-gjvvr   metal3://7365c9e8-8322-4969-8db7-916c0f00760b   Running
cluster-controlplane-nqv7p   metal3://136a085a-fae8-412d-a4bf-dd331a533437   Running
worker-1-5bc87ff868-2x5qz    metal3://534c9542-3250-4806-9f70-2552c75f964e   Running
worker-1-5bc87ff868-6tjhh    metal3://32292183-6617-450e-a230-ed4ac02369dd   Running
worker-1-5bc87ff868-dwg5z    metal3://fde274cb-cf6e-42ff-b5ca-32ca7310e9d0   Running
@rkjain rkjain added bug Something isn't working triage labels May 10, 2021
@jezogwza jezogwza added this to the Future milestone May 12, 2021
@jezogwza jezogwza added 2-Manifests Relates to manifest/document set related issues and removed triage labels May 12, 2021
@ermurugesanbe
Copy link
Contributor

Please assign to me

@eak13
Copy link

eak13 commented Jul 7, 2021

@ermurugesanbe all yours

@lb4368 lb4368 added the size l 5-7+ days [multiple functional areas; complex function or capability, or multiple PSs] label Jul 12, 2021
@ermurugesanbe
Copy link
Contributor

image
by changing given manifest to replicate only first control-plane instead of adding new control-plane its fixed.

@ermurugesanbe
Copy link
Contributor

Hi @rkjain,
kindly verify and close the issue.

@rkjain
Copy link
Author

rkjain commented Sep 13, 2021

Thank you murugesan for getting this fixed. I now understand that the reference manifests were creating an extra control plane, and that part had to be commented for this to work.

@rkjain rkjain closed this as completed Sep 13, 2021
@eak13 eak13 modified the milestones: Future, v2.1 Nov 3, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
2-Manifests Relates to manifest/document set related issues bug Something isn't working size l 5-7+ days [multiple functional areas; complex function or capability, or multiple PSs]
Projects
None yet
Development

No branches or pull requests

5 participants