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

pluto panics when specifying an https-proxy without a URL scheme #338

Open
ginglis13 opened this issue Jan 7, 2025 · 0 comments · May be fixed by #339
Open

pluto panics when specifying an https-proxy without a URL scheme #338

ginglis13 opened this issue Jan 7, 2025 · 0 comments · May be fixed by #339
Assignees
Labels
bug Something isn't working

Comments

@ginglis13
Copy link
Contributor

Related: bottlerocket-os/bottlerocket-project-website#499

What I expected to happen:

I can set settings.network.https-proxy without a URL scheme as per Bottlerocket documentation https://bottlerocket.dev/en/os/1.26.x/api/settings/network/#https-proxy

What actually happened:

Starting Generate additional settings for Kubernetes...
[    9.515344] pluto[1048]: thread 'main' panicked at aws-smithy-experimental/src/hyper_1_0.rs:259:49:
[FAILED] Failed to start Generate additional settings for Kubernetes.
See 'systemctl status pluto.service' for details.
[    9.570493] pluto[1048]: Unable to parse HTTPS proxy as URL: RelativeUrlWithoutBase
[DEPEND] Dependency failed for Applies settings to create config files.
[    9.690248] pluto[1048]: note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
[DEPEND] Dependency failed for Bootstrap Commands.
[DEPEND] Dependency failed for Bottlerocket initial configuration complete.
[DEPEND] Dependency failed for Isolates configured.target.
[DEPEND] Dependency failed for Sets the hostname.
[DEPEND] Dependency failed for Send signal to CloudFormation Stack.

How to reproduce the problem:

On any Bottlerocket node >= v1.17.0 (bug introduced in bottlerocket-os/bottlerocket@6a66851), launch a node with

  [settings.network]
    https-proxy = "10.0.5.67:8080"

and observe the error.

@ginglis13 ginglis13 added the bug Something isn't working label Jan 7, 2025
@ginglis13 ginglis13 self-assigned this Jan 7, 2025
@ginglis13 ginglis13 linked a pull request Jan 7, 2025 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant