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

WIP: AGENT-139: Get nmstate builtin #5961

Closed
wants to merge 3 commits into from

Conversation

celebdor
Copy link
Contributor

@celebdor celebdor commented Jun 3, 2022

No description provided.

@celebdor celebdor changed the title Get nmstate builtin WIP: Get nmstate builtin Jun 3, 2022
@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jun 3, 2022
@openshift-ci openshift-ci bot requested review from rna-afk and sadasu June 3, 2022 01:40
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jun 3, 2022

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
To complete the pull request process, please assign jhixson74 after the PR has been reviewed.
You can assign the PR to them by writing /assign @jhixson74 in a comment when ready.

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@celebdor
Copy link
Contributor Author

celebdor commented Jun 3, 2022

Still need to vendor the golang part

@celebdor celebdor force-pushed the go-nmstate branch 3 times, most recently from e3501c1 to 9d71a0e Compare June 3, 2022 09:09
@celebdor celebdor changed the title WIP: Get nmstate builtin WIP: AGENT-139: Get nmstate builtin Jun 3, 2022
@patrickdillon
Copy link
Contributor

Speaking with Toni on slack, I wanted to mention a few considerations:

  1. Our builds are very iffy right now (failing frequently due to hitting the hour long timeout limit) after our terraform implementation. Each build builds the installer for 3 different architectures, and building and zipping each terraform provider takes a long time; this is why we are frequently hitting timeouts. This limitation needs to be considered and the pattern is not sustainable (long term).
  2. It looks like some of the dependencies are not present in the builder image, so that would need to be worked out with ART.

/cc @jhixson74 who is working on profiling the installer build, but is out through early next week at a conference

@celebdor
Copy link
Contributor Author

celebdor commented Jun 3, 2022

@patrickdillon couldn't the builds be separated per architecture to avoid that particular problem?

@patrickdillon
Copy link
Contributor

@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

@bfournie
Copy link
Contributor

bfournie commented Jun 7, 2022

I found that I needed to make this change to build.sh when building on rhel/Centos

-CGO_LDFLAGS="${CGO_LDFLAGS:--L${REPO_ROOT_DIR}/nmstate/rust/lib}"
+CGO_LDFLAGS="${CGO_LDFLAGS:--L${REPO_ROOT_DIR}/nmstate/rust/lib} -ldl -lrt"

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jun 7, 2022

@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.

@openshift-ci openshift-ci bot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jun 7, 2022
Still need to change the nmstatectl usage to the library. For now it
just shows the ability to invoke the go bindings
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jun 7, 2022

@celebdor: 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/verify-codegen c0f9210 link true /test verify-codegen
ci/prow/golint c0f9210 link true /test golint
ci/prow/e2e-agent-compact c0f9210 link true /test e2e-agent-compact
ci/prow/unit c0f9210 link true /test unit
ci/prow/gofmt c0f9210 link true /test gofmt
ci/prow/govet c0f9210 link true /test govet
ci/prow/verify-vendor c0f9210 link true /test verify-vendor
ci/prow/images c0f9210 link true /test images
ci/prow/e2e-aws c0f9210 link false /test e2e-aws

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.

@openshift-bot
Copy link
Contributor

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 the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Sep 6, 2022
@openshift-bot
Copy link
Contributor

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 Oct 7, 2022
@openshift-bot
Copy link
Contributor

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 Nov 6, 2022
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 6, 2022

@openshift-bot: Closed this PR.

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
do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. 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.

None yet

4 participants