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

Bug 1984576: baremetal: reinstate provisioningInterface for provisioning CR #5100

Merged
merged 1 commit into from
Jul 22, 2021

Conversation

hardys
Copy link
Contributor

@hardys hardys commented Jul 22, 2021

This was removed in #5015 but we should still include it if a user
provides a value - since it's now optional we'll pass an empty
string if no value is provided, which will trigger the new logic
that detects the interface name by MAC.

This was removed in openshift#5015 but we should still include it if a user
provides a value - since it's now optional we'll pass an empty
string if no value is provided, which will trigger the new logic
that detects the interface name by MAC.
@hardys
Copy link
Contributor Author

hardys commented Jul 22, 2021

/label platform/baremetal

@openshift-ci openshift-ci bot added the platform/baremetal IPI bare metal hosts platform label Jul 22, 2021
@openshift-ci openshift-ci bot requested review from mtnbikenc and rna-afk July 22, 2021 10:53
@hardys
Copy link
Contributor Author

hardys commented Jul 22, 2021

/cc @asalkeld @stbenjam

@derekhiggins
Copy link
Contributor

lgtm

@hardys
Copy link
Contributor Author

hardys commented Jul 22, 2021

I tested with and without the optional provisioningNetworkInterface and can see the templating results in an empty string when it's not provided which I think should work fine with the related https://github.com/metal3-io/ironic-image/pull/272/files changes:

$ cat ocp/ostest/openshift/99_baremetal-provisioning-config.yaml 
apiVersion: metal3.io/v1alpha1
kind: Provisioning
metadata:
  name: provisioning-configuration
spec:
  provisioningInterface: ""

@hardys
Copy link
Contributor Author

hardys commented Jul 22, 2021

/retitle Bug 1984576: baremetal: reinstate provisioningInterface for provisioning CR

@openshift-ci openshift-ci bot changed the title baremetal: reinstate provisioningInterface for provisioning CR Bug 1984576: baremetal: reinstate provisioningInterface for provisioning CR Jul 22, 2021
@openshift-ci openshift-ci bot added bugzilla/severity-high Referenced Bugzilla bug's severity is high for the branch this PR is targeting. bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. labels Jul 22, 2021
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jul 22, 2021

@hardys: This pull request references Bugzilla bug 1984576, which is valid.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target release (4.9.0) matches configured target release for branch (4.9.0)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)

No GitHub users were found matching the public email listed for the QA contact in Bugzilla (augol@redhat.com), skipping review request.

In response to this:

Bug 1984576: baremetal: reinstate provisioningInterface for provisioning CR

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.

@dtantsur
Copy link
Member

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jul 22, 2021
@patrickdillon
Copy link
Contributor

/approve

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jul 22, 2021

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: patrickdillon

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

The pull request process is described 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

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jul 22, 2021
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jul 22, 2021

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

Test name Commit Details Rerun command
ci/prow/e2e-openstack-kuryr 29dddd0 link /test e2e-openstack-kuryr
ci/prow/e2e-crc 29dddd0 link /test e2e-crc
ci/prow/e2e-libvirt 29dddd0 link /test e2e-libvirt
ci/prow/e2e-aws-workers-rhel7 29dddd0 link /test e2e-aws-workers-rhel7
ci/prow/e2e-metal-ipi-ovn-ipv6 29dddd0 link /test e2e-metal-ipi-ovn-ipv6

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-merge-robot openshift-merge-robot merged commit 14b6d30 into openshift:master Jul 22, 2021
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jul 22, 2021

@hardys: All pull requests linked via external trackers have merged:

Bugzilla bug 1984576 has been moved to the MODIFIED state.

In response to this:

Bug 1984576: baremetal: reinstate provisioningInterface for provisioning CR

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.

@derekhiggins
Copy link
Contributor

e2e-metal-ipi-ovn-ipv6 failed for a different reason (BMO failed to start)

{"level":"error","ts":1626958012.7065668,"logger":"setup","msg":"unable to start manager","error":"error listening on :9440: listen tcp :9440: bind: address already in use","stacktrace":"main.main\n\t/go/src/github.com/metal3-io/baremetal-operator/main.go:134\nruntime.main\n\t/usr/lib/golang/src/runtime/proc.go:225"}

Looks like the bug is fixed, static-ip-manager did its job

  • /usr/sbin/ip addr add fd00:1101::3/64 dev enp1s0 valid_lft 10 preferred_lft 10

@hardys
Copy link
Contributor Author

hardys commented Jul 23, 2021

e2e-metal-ipi-ovn-ipv6 failed for a different reason (BMO failed to start)

{"level":"error","ts":1626958012.7065668,"logger":"setup","msg":"unable to start manager","error":"error listening on :9440: listen tcp :9440: bind: address already in use","stacktrace":"main.main\n\t/go/src/github.com/metal3-io/baremetal-operator/main.go:134\nruntime.main\n\t/usr/lib/golang/src/runtime/proc.go:225"}

Ack, that is https://bugzilla.redhat.com/show_bug.cgi?id=1983975 which I believe @andfasano is looking into

Looks like the bug is fixed, static-ip-manager did its job

  • /usr/sbin/ip addr add fd00:1101::3/64 dev enp1s0 valid_lft 10 preferred_lft 10

\o/

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. bugzilla/severity-high Referenced Bugzilla bug's severity is high for the branch this PR is targeting. bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. lgtm Indicates that a PR is ready to be merged. platform/baremetal IPI bare metal hosts platform
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants