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.

Sign up for GitHub

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

Jump to bottom

kargo openstack fails when setting a cluster-name #64

Open
pcm32 opened this issue Aug 3, 2016 · 2 comments
Open

kargo openstack fails when setting a cluster-name #64

pcm32 opened this issue Aug 3, 2016 · 2 comments

Comments

@pcm32
Copy link
Contributor

pcm32 commented Aug 3, 2016 •
edited
Loading

Invoking

kargo openstack --nodes 3 --cluster-name k8s-phenomenal

fails trying to use a security group name that doesn't exist:

CLONING KARGO GIT REPO *********************************************************
Cloning into '/home/ubuntu/.kargo'...
kargo repo cloned
Create 3 instances on openstack ? [Y/n] Y

PLAY [localhost] ***************************************************************

TASK [Create security group] ***************************************************
changed: [localhost]

TASK [Add security rules] ******************************************************
changed: [localhost] => (item=tcp)
changed: [localhost] => (item=udp)
changed: [localhost] => (item=icmp)

TASK [Create nodes network ports] **********************************************
failed: [localhost] (item=k8s-phenomenal-ootp8f) => {"failed": true, "item": "k8s-phenomenal-ootp8f", "msg": "Security group: k8s-phenomenal-69k17f, was not found"}
failed: [localhost] (item=k8s-phenomenal-ystmto) => {"failed": true, "item": "k8s-phenomenal-ystmto", "msg": "Security group: k8s-phenomenal-69k17f, was not found"}
failed: [localhost] (item=k8s-phenomenal-k2f8sf) => {"failed": true, "item": "k8s-phenomenal-k2f8sf", "msg": "Security group: k8s-phenomenal-69k17f, was not found"}

NO MORE HOSTS LEFT *************************************************************
    to retry, use: --limit @/home/ubuntu/.kargo/local.retry

PLAY RECAP *********************************************************************
localhost                  : ok=2    changed=2    unreachable=0    failed=1

When running without --cluster-name it works fine.
jianzj pushed a commit to jianzj/kubespray-cli that referenced this issue Aug 31, 2017
Fix issue about setting customized cluster name when using kubespray
e8a4dcf 
openstack

When using `kubespray openstack` to initialize environment and deploy
kubernetes cluster, if you want to setup a cluster name with
`--cluster-name`, you will always receive errors like 

```
TASK [Create nodes network ports]
**********************************************
failed: [localhost] (item=k8s-phenomenal-ootp8f) => {"failed": true,
"item": "k8s-phenomenal-ootp8f", "msg": "Security group:
k8s-phenomenal-69k17f, was not found"}
failed: [localhost] (item=k8s-phenomenal-ystmto) => {"failed": true,
"item": "k8s-phenomenal-ystmto", "msg": "Security group:
k8s-phenomenal-69k17f, was not found"}
failed: [localhost] (item=k8s-phenomenal-k2f8sf) => {"failed": true,
"item": "k8s-phenomenal-k2f8sf", "msg": "Security group:
k8s-phenomenal-69k17f, was not found"}
```

That is because security group name is redefined and security group is
not created with these names. 

These is one issue existing,
kubespray#64

I did some code changes, which cluster_name will be changed at the first
place when customer set a new one.

Please help to review and let me know if anything that I could update or
improve.
@jianzj jianzj mentioned this issue Aug 31, 2017
Merged
@jianzj
Copy link

jianzj commented Aug 31, 2017

I did some code change for this issue , feel free to let me know anything that I could improve . #104

@jianzj
Copy link

jianzj commented Sep 1, 2017

As PR is merge, I think this issue should be fixed . Feel free to test and check

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@pcm32 @jianzj