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

[ISSUE] Supervisor not completely honor --listen-ctl or HAB_LISTEN_CTL #7699

Open
sam1el opened this issue May 18, 2020 · 4 comments
Open

[ISSUE] Supervisor not completely honor --listen-ctl or HAB_LISTEN_CTL #7699

sam1el opened this issue May 18, 2020 · 4 comments
Labels
Epic Focus:Habitat Team:Habitat All issues tied to Chef habitat team

Comments

@sam1el
Copy link

sam1el commented May 18, 2020

When setting --listen-ctl or HAB_LISTEN_CTL on a system. The supervisor will use it however, any subsequent commands to the supervisor including hab svc load my/service
This behavior happens wether it is set in the supervisor, the system env or directly in the command line.

We also looked at the API for Census and Butterfly and the port setting is not persisted there no matter where it is set either.
We tested on Red Hat Linux 6, 7, 8 Windows 2008r2, 2012r2, 2016 and 2019

For ease of use it would make sense for the supervisor to take the port change as it new default rather than having to type hab svc load my/service -r 127.0.0.1:19632 with every new command to the supervisor. It seems counter-intuitive to have to add extra arguments to existing automation or cookbooks to account for something the supervisor you would think the supervisor to know already

Aha! Link: https://chef.aha.io/features/APPDL-24

@sam1el sam1el added the C-bug label May 18, 2020
@christophermaier
Copy link
Contributor

Just for clarification, this is only for interacting with a Supervisor running on the same machine, but where that Supervisor has been configured for a non-standard control gateway port, correct?

Given that the CLI looks for /hab/sup/default/CTL_SECRET locally to get the shared secret, it makes sense that it should have a corresponding way to access the port, as well.

@sam1el
Copy link
Author

sam1el commented Jul 21, 2020

yes that is correct

@christophermaier christophermaier added Type: Bug Issues that describe broken functionality and removed C-bug labels Jul 24, 2020
@rahulgoel1 rahulgoel1 reopened this Apr 14, 2021
@trevorghess trevorghess added Epic and removed Type: Bug Issues that describe broken functionality labels May 24, 2021
@rahulgoel1 rahulgoel1 added Focus:Habitat Team:Habitat All issues tied to Chef habitat team labels Jul 30, 2021
@stale
Copy link

stale bot commented Jul 31, 2022

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. We value your input and contribution. Please leave a comment if this issue still affects you.

1 similar comment
@stale
Copy link

stale bot commented Aug 12, 2023

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. We value your input and contribution. Please leave a comment if this issue still affects you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Epic Focus:Habitat Team:Habitat All issues tied to Chef habitat team
Projects
None yet
Development

No branches or pull requests

4 participants