Skip to content

Conversation

@zaneb
Copy link
Member

@zaneb zaneb commented Feb 4, 2022

Currently the IPA service is the only one that needs the proxy settings, but in the interests of future flexibility, do what the installer bootstrap does and set the proxy environment variables by default in all systemd services.

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 4, 2022

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: zaneb

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci bot requested review from andfasano and hardys February 4, 2022 17:58
@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Feb 4, 2022
@zaneb zaneb force-pushed the proxy-default-env branch 3 times, most recently from 1623245 to 6f22457 Compare February 4, 2022 18:37
@openshift-ci openshift-ci bot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Feb 15, 2022
@zaneb zaneb force-pushed the proxy-default-env branch from 6f22457 to f72735b Compare March 7, 2022 22:24
@openshift-ci openshift-ci bot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Mar 7, 2022
})
}

config.Storage.Files = append(config.Storage.Files, ignitionFileEmbed(
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's please only create this file if there are settings to apply. We're working on integration with the assisted service, I'd like to be able to minimize the impact on them (e.g. if they have their own default environment).

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If there is a conflict, better that we have to deal with it all the time IMHO. Test coverage for proxy variables is notoriously poor.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure I get it... why do we need to create this file when no proxy settings are provided?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We don't, but if creating it causes a bug then we don't want to find out only when it is used in the field, which is how we've found bugs with the proxy config in the past.

zaneb added 3 commits March 29, 2022 11:19
Currently the IPA service is the only one that needs the proxy settings,
but in the interests of future flexibility, do what the installer
bootstrap does and set the proxy environment variables by default in all
systemd services.

By default, podman containers will get passed any proxy environment
variables that exist in the environment when the container is started:
https://docs.podman.io/en/latest/markdown/podman-run.1.html#http-proxy
Too many strings make the ignition.New() method hard to read.
@zaneb zaneb force-pushed the proxy-default-env branch from f72735b to 4a0f6af Compare March 29, 2022 15:23
@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 lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. labels Jun 27, 2022
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jun 27, 2022

@zaneb: PR needs rebase.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@openshift-bot
Copy link

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

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

/lifecycle rotten
/remove-lifecycle stale

@openshift-ci openshift-ci bot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Jul 27, 2022
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Sep 8, 2022

@zaneb: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/e2e-metal-ipi-sdn 4a0f6af link true /test e2e-metal-ipi-sdn
ci/prow/e2e-metal-ipi-sdn-bm 4a0f6af link true /test e2e-metal-ipi-sdn-bm

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@openshift-bot
Copy link

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

@openshift-ci openshift-ci bot closed this Oct 9, 2022
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 9, 2022

@openshift-bot: Closed this PR.

Details

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants