If we end up reconciling the Host again after starting an inspection in
Ironic, but before the IntrospectionStatus is available in
ironic-inspector, we don't want to attempt to start another inspection.
Check if the host is already in the correct state in Ironic before
trying to change the state to 'inspecting'.

This issue was identified in metal3-io#393, but may not be the cause.

the fix was merged upstream and is in the tripleO package:
https://opendev.org/openstack/ironic/commit/7f1f79ac25e270c3585dd23c042a037431b97718

Enable fasttrack for ironic

InvolvedObject APIVersion is expected to be SchemeGroupVersion string

Co-authored-by: Xenwar <anwar.hassen@est.tech>

Restructure kustomization and Add Ironic-Endpoint using Keepalived

The example path is a bit confusing to users, so replace it with an
actual working value from real hardware. Also add an example from the
ironic documentation at
https://docs.openstack.org/ironic/latest/admin/drivers/redfish.html

Signed-off-by: Doug Hellmann <dhellmann@redhat.com>

Removing the privileged security context to have a more
fine-grained control with capabilities. NET_ADMIN set for
dnsmasq and httpd (in case the user specifies a low port)

Remove container privileges and add NET_ADMIN capability

Change ironic endpoint keepalived image

Add verify ca

…xample

update example URL for redfish driver

There is a typo for DisableCertificateVerification that
causes the e2e tests to fail.

Signed-off-by: Yolanda Robla <yroblamo@redhat.com>

…en up date PR 140 in baremetal

Add available ProvisioningState  , so CAPBM is aware of this state

Add support to reconcile concurrently

Avoid starting inspection twice

This is to comply with CAPI secrets

Look for userData or value in the userdata secret

Add a Pause annotation for pivoting

Update Configuration with Kustomize info

…shif

Remove unused Kustomization File + Update documentation

add local-hostname in ironic metadata

Our goal is to upgrade operator-sdk to 0.15.2 which is the latest
released version right now.  Version 0.12.0 makes a breaking change
where we are required to start using go modules.  In order for the
automatic conversion to work, we have to downgrade: 0.12.0 will use go
modules.

https://github.com/operator-framework/operator-sdk/blob/master/doc/migration/version-upgrade-guide.md

No dependecies have been upgraded.

We ran "git mod init", and then manually entered the overrides from the
operator-sdk documentation.[1]

This means that we can now remove all of the dep files, and the vendor
directory.

[1]: https://github.com/operator-framework/operator-sdk/blob/master/doc/migration/version-upgrade-guide.md#v011x

To 0.15

https://github.com/operator-framework/operator-sdk/blob/master/doc/migration/version-upgrade-guide.md#v015x

BareMetalHost resource is extended with NetworkData property which
contains a reference to Secret resource. It's considered that network
data specified in the referenced Secret under "networkData" key.

Change-Id: I7dcd160ca5d3cd220f45923c4a109b3baa129782

hosConfigData object should be reconciler-agnostic and not depend on
implementation details

Change-Id: I7abe532d6181f7c969b2a74d0964b610b179683b

Change-Id: I2aaa02d6ee98a77475fd052bc192db063b2d4b3a

Change-Id: I3dc50b089ccf9ab0b04d3a090a47ae522f0f1905

Change-Id: I6df87c165c4a26789af1701a7035301b5b7b1947

Change-Id: Iae27e2b54eec7fb708a42f2f4eb8274584b7a620

UserData and NetworkData should have same types for the sake of
unification

Change-Id: I534ff70e25301f314c28021601fe7bff14419862

Change-Id: Ic97fa0e510fc0051a8a874c04c4a9f1d10112ec4

Go modules, take 2

Fallback to value key in a user data or network data secret

Change-Id: I90eced8df8a7679c8f34c6cdfabaaed958021cf4

Introduce network_data for host

Fix typo in e2e testing in certificate test

Signed-off-by: Nir <niry@redhat.com>

Signed-off-by: Nir <niry@redhat.com>

Signed-off-by: Nir <niry@redhat.com>

Signed-off-by: Nir <nyehia@redhat.com>

Signed-off-by: Nir <niry@redhat.com>

Signed-off-by: Nir <niry@redhat.com>

Signed-off-by: Nir <niry@redhat.com>

…o use empty object before updating it

…t only if it's non-zero to avoid multiple writes (per review comments)

…R comments

We did not update the documentation for BMC URLs when we added the
virtual media variants.

Signed-off-by: Doug Hellmann <dhellmann@redhat.com>

…quired

Signed-off-by: Nir <niry@redhat.com>

Signed-off-by: Nir <niry@redhat.com>

…ments

Signed-off-by: Nir <niry@redhat.com>

Signed-off-by: Nir <niry@redhat.com>

Signed-off-by: Nir <niry@redhat.com>

…sult() method

Signed-off-by: Nir <niry@redhat.com>

expand BMC URL documentation to include virtual media support

Replace v1a1 CI status badge with v1a3

Reboot API Implementation

This can be one of two keys, depending on whether the host
got an ipv4 or ipv6 address, so use the ipv6 key in the case
where the ipv4 one is unset.

Currently in a single-stack ipv6 deployment the IP ends up
empty like:

Hostname:     worker-0.ostest.test.metalkube.org
    Nics:
      Ip:

But with this change Ip should be correctly populated.

Don't assume IPv4 in introspection data

…readme

Update pause annotation description

Empty namespaces in userdata and networkdata object references
now default to the baremetalhost namespace

…tion

Fix bmh pause annotation key in api.md

Update dev-setup.md

Default user and network data namespace to BMH namespace

… outside cluster

Completes metal3-io#472

Add --namespace cli argument support for BMO

Remove v1alpha2 CI status badges

Fix make test phony to remove dep-check call

New kustomize config for BMO standalone, needed with kind when ironic…

…variables

Default missing variables

Fix Ironic fast-track for local BMO deployment