-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
WIP: AGENT-139: Get nmstate builtin #5961
Conversation
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Still need to vendor the golang part |
e3501c1
to
9d71a0e
Compare
Speaking with Toni on slack, I wanted to mention a few considerations:
/cc @jhixson74 who is working on profiling the installer build, but is out through early next week at a conference |
@patrickdillon couldn't the builds be separated per architecture to avoid that particular problem? |
I don't think so. Also I misspoke: for each architecture we're making three builds but it varies by os & arch: mac arm64, mac amd64, and linux amd64. But this discussion and the links should give more context: https://coreos.slack.com/archives/C68TNFWA2/p1648044301526129 |
I found that I needed to make this change to build.sh when building on rhel/Centos
|
@celebdor: PR needs rebase. 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. |
Still need to change the nmstatectl usage to the library. For now it just shows the ability to invoke the go bindings
@celebdor: The following tests failed, say
Full PR test history. Your PR dashboard. 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. |
Issues go stale after 90d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle stale |
Stale issues rot after 30d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle rotten |
Rotten issues close after 30d of inactivity. Reopen the issue by commenting /close |
@openshift-bot: Closed this PR. In 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. |
No description provided.