-
Notifications
You must be signed in to change notification settings - Fork 1.5k
Bug 2039109: Fix image-customization-controller image pull failure #5513
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
Bug 2039109: Fix image-customization-controller image pull failure #5513
Conversation
Signed-off-by: Hu Shuai <[email protected]>
|
Hi @hs0210. Thanks for your PR. I'm waiting for a openshift member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. DetailsInstructions 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. |
|
/ok-to-test |
|
We'll need to open a bugzilla for this. /label platform/baremetal |
|
We're also using sudo for some iptables commands, it wouldn't hurt to get rid of those as well so that we're less likely to repeat the error. |
Signed-off-by: Hu Shuai <[email protected]>
Done. I removed sudo from iptables commands. |
Understood, we will do. |
|
/retest |
|
/retitle Bug 2039109: Fix image-customization-controller image pull failure |
|
@hs0210: An error was encountered searching for bug 2039109 on the Bugzilla server at https://bugzilla.redhat.com. No known errors were detected, please see the full error message for details. Full error message.
code 102: You are not authorized to access bug #2039109. Most likely the bug has been restricted for internal development processes and we cannot grant access. If you are a Red Hat customer with an active subscription, please visit the Red Hat Customer Portal for assistance with your issue If you are a Fedora Project user and require assistance, please consider using one of the mailing lists we host for the Fedora Project.
Please contact an administrator to resolve this issue, then request a bug refresh with DetailsIn response to this:
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. |
|
@hs0210 as you can see from the bot, private bugzillas cannot be attached to pull requests. Could you please open it or file a public one with limited information? In the latter case, please update the title again. |
|
/bugzilla refresh |
|
@hs0210: This pull request references Bugzilla bug 2039109, which is invalid:
Comment DetailsIn response to this:
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. |
|
/bugzilla refresh |
|
@rhjanders: This pull request references Bugzilla bug 2039109, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker. 3 validation(s) were run on this bug
No GitHub users were found matching the public email listed for the QA contact in Bugzilla ([email protected]), skipping review request. DetailsIn response to this:
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. |
|
/lgtm |
|
/approve |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: andfasano, zaneb The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
8 similar comments
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
|
/retest |
|
@hs0210: All pull requests linked via external trackers have merged: Bugzilla bug 2039109 has been moved to the MODIFIED state. DetailsIn response to this:
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. |
|
@hs0210: all tests passed! Full PR test history. Your PR dashboard. DetailsInstructions 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. |
startironic.sh itself is executed under the root user, so there is no need to use
sudo. And usingsudoleads to the loss of proxy env, which causes the failure of image-customization pull.Before #5473
sudohas been used to run Ironic related containers, but no error was reported because the ironic image had been downloaded to the local beofre. But the image-customization container newly added by #5473 did not pull the image locally before, so it triggered this long-standing error.This PR fix the first error in #5504
Signed-off-by: Hu Shuai [email protected]