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

ROSA CLI 1.1.6 & 1.1.7 error "create_cluster_proxy" #551

Closed
IanScottIBM opened this issue Dec 8, 2021 · 4 comments
Closed

ROSA CLI 1.1.6 & 1.1.7 error "create_cluster_proxy" #551

IanScottIBM opened this issue Dec 8, 2021 · 4 comments
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@IanScottIBM
Copy link

IanScottIBM commented Dec 8, 2021

Description
What problem/issue/behavior are you having trouble with? What do you expect to see?
Downloaded ROSA CLI 1.1.6 to run on my mac (rosa-darwin-amd64 from https://github.com/openshift/rosa/releases)

I then tried to create a ROSA cluster using the new HTTP / HTTPS PROXY flags. This failed almost immediately with an error (see below):

Command:

./rosa-darwin-amd64 create cluster --private-link --multi-az --cluster-name=mydevrosa --machine-cidr=172.25.246.0/24 --subnet-ids=subnet-034f368cf97XXXXXX,subnet-0084b9e30c8XXXXXX,subnet-086ea2deeb2XXXXXX --enable-autoscaling --min-replicas 3 --max-replicas 6 --http-proxy http://proxy.ic.xxx.xxx:3128/ --https-proxy http://proxy.ic.xxx.xxx:3128/ --profile=my-dev-ocp

Output:

W: You are choosing to use AWS PrivateLink for your cluster. Once the cluster is created, this option cannot be changed.
? Are you sure you want to use AWS PrivateLink for cluster 'mydevrosa'? Yes
I: Creating cluster 'mydevrosa'
I: To view a list of clusters and their status, run 'rosa list clusters'

E: Failed to create cluster: 'create_cluster_proxy' capability is not set for this organization

I can't find any documentation on these new flag so I don't know what organization it is talking about. Also I am a bit worried that this new functionality is trying to create a new proxy rather than using the one specified in the command-line.

Please can you explain how these are intended to work and if there are any additional environment of AWS settings required to be set...

These are previous issues I've raised relating to the use of proxies that I was hoping these new flag were added to fix...

Red Hat - Case 03011961 - Can't configure the "rosa" CLI tool to use a proxy
Red Hat - Case 03031217 - Cluster Wide noProxy setting is being ignored

Where are you experiencing the behavior? What environment?
Running 1.1.6 ROSA CLI from my MacOS laptop (OS 12.0.1)
[update: Running 1.1.7 ROSA CLI from my MacOS laptop (OS 12.1)

When does the behavior occur? Frequency? Repeatedly? At certain times?
Always

@IanScottIBM IanScottIBM changed the title ROSA CLI 1.1.6 "create ROSA CLI 1.1.6 error "create_cluster_proxy" Dec 8, 2021
@IanScottIBM IanScottIBM changed the title ROSA CLI 1.1.6 error "create_cluster_proxy" ROSA CLI 1.1.6 & 1.1.7 error "create_cluster_proxy" Jan 18, 2022
@arendej
Copy link
Contributor

arendej commented Feb 10, 2022

That was a feature gate. ROSA CLI 1.1.9 has un-gated the cluster proxy feature.

@IanScottIBM
Copy link
Author

Hello @arendej is ROSA CLI 1.1.9 officially supported? I have just downloaded the CLI from the AWS console and it seems to still be 1.1.7...

@openshift-bot
Copy link

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci openshift-ci bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 11, 2022
@IanScottIBM
Copy link
Author

Closing this ticket: I see v1.2.2 is now officially released and available on the AWS Console, so I'll try on that version.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Development

No branches or pull requests

3 participants