Skip to content

Merge upstream 2021-03-30#139

Merged
openshift-merge-robot merged 37 commits intoopenshift:masterfrom
honza:merge-upstream-2021-03-30
Apr 6, 2021
Merged

Merge upstream 2021-03-30#139
openshift-merge-robot merged 37 commits intoopenshift:masterfrom
honza:merge-upstream-2021-03-30

Conversation

@honza
Copy link
Copy Markdown
Member

@honza honza commented Mar 30, 2021

No description provided.

s3rj1k and others added 30 commits February 15, 2021 15:19
… options.

Signed-off-by: s3rj1k <evasive.gyron@gmail.com>
After following the process described in our community documentation
[1], there were no objections to adding Dmitry as an approver.

[1] https://github.com/metal3-io/metal3-docs/tree/master/maintainers

Signed-off-by: Doug Hellmann <dhellmann@redhat.com>
The idrac BMCs have partiular handling of boot mode as configuration
change requests which need to be honored only at power state changes
as opposed to immediately, because this can conflict and over-write
existing configuration jobs.

While we shouldn't be in this state without more advanced bmc
features being leveraged, it is best to use the vendor supported
hardware type and interfaces for using redfish with their hardware.

This boot interface defaults to using iPXE, as opposed to virtual
media. A separate idrac specific redfish virtual media interface
already existed in the baremetal-operator.
Use separate methods for setting update node options.
…-ipxe

Add idrac-redfish url type (continue)
Use the correct version of tools (from go.mod)
Add option to let Apache web server handle TLS on Ironic and Ironic-inspector sides

Force the use of WSGI and remove the httpd container


Remove the option to use reverse proxy for inspector


Add option to use reverse proxy on ironic inspector
…oxy-nam

Apache webserver handles TLS on Ironic
Any host which lacks BMC details should reach the Unmanaged
state regardless of whether it is externally provisioned or not.

Currently in this case we encounter an error creating the ironic
provisioner, because it expects BMC details to exist.
Decouple Unmanaged state from externallyProvisioned
Instead of using `""` we will be using `no-raid`.
The support for RAID was considering  RAIDInterface defaul value as `""`
to generate the clean steps, this is causing errors in vmedia
deployments with idrac because it uses `no-raid`:

"Node failed to start the first cleaning step. Error: node does not support
this clean step: {'interface': 'raid', 'step': 'delete_configuration'}"
Review registration log traces for Provisioner
Signed-off-by: s3rj1k <evasive.gyron@gmail.com>
Add a unit test for unsupported secure boot
The empty provisioner is a workaround for the fact that the ironic
provisioner cannot handle instantiation when there are no BMC details
available. The change cadeb28 that
added it also had the effect of logging provisioner information on every
reconcile when it was intended to be logged only once, at startup.

Make it the ironic provisioner factory's responsibility to return an
empty Provisioner at runtime when it cannot create an ironic
Provisioner, and do only one-time startup configuration in main.go.

Fixes metal3-io#819
Not every provisioner operation requires BMC access details, so only
create them when needed. This allows us to reach the unmanaged state
using the ironic provisioner when there are no BMC details specified.

This also means that if the BMC details cannot be parsed correctly,
rather than an error that causes constant requeues and is recorded only
in the logs, we will record a registration failure that will be visible
in the UI.
zaneb and others added 7 commits March 26, 2021 22:09
Now that the ironic provisioner only requires BMC details when
registering (which does not occur in the unmanaged state), remove the
empty provisioner workaround.
Eliminate need for "empty" provisioner
Pass go tests flags via env.
- Don't search by nodename if it has "~" in it
- if POD_NAMESPACE is "" then use watchNamespace for the leader
Prepend the namespace to ironic nodenames to avoid conflicts
$ go mod tidy
$ go mod vendor
@openshift-ci-robot openshift-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Mar 30, 2021
@hardys
Copy link
Copy Markdown

hardys commented Apr 1, 2021

@honza would you mind rebasing this on the latest BMO again?

Several important PRs landed yesterday (for example metal3-io#784 which is important to the iso based flow and there were several bugfixes)

@hardys
Copy link
Copy Markdown

hardys commented Apr 6, 2021

/retest

@hardys
Copy link
Copy Markdown

hardys commented Apr 6, 2021

/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Apr 6, 2021
@openshift-ci-robot
Copy link
Copy Markdown

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: hardys, honza

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-merge-robot openshift-merge-robot merged commit 1780c51 into openshift:master Apr 6, 2021
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. lgtm Indicates that a PR is ready to be merged.

Projects

None yet

Development

Successfully merging this pull request may close these issues.