Prepare cifmw to run with ZIronic#3505
Prepare cifmw to run with ZIronic#3505danpawlik merged 6 commits intoopenstack-k8s-operators:mainfrom
Conversation
|
Skipping CI for Draft Pull Request. |
|
Build failed (check pipeline). Post https://softwarefactory-project.io/zuul/t/rdoproject.org/buildset/189b934b700044f3bda13641b2aad34b ✔️ openstack-k8s-operators-content-provider SUCCESS in 1h 53m 17s |
danpawlik
force-pushed
the
poc-zironic
branch
2 times, most recently
from
0cc183e to
04bb19b
Compare
|
Build failed (check pipeline). Post https://softwarefactory-project.io/zuul/t/rdoproject.org/buildset/d82a46fe901b4ac6b31d905a4f72965e ❌ openstack-k8s-operators-content-provider FAILURE in 5m 47s |
danpawlik
force-pushed
the
poc-zironic
branch
from
04bb19b to
1f0dbfa
Compare
|
Build failed (check pipeline). Post https://softwarefactory-project.io/zuul/t/rdoproject.org/buildset/c0a79539bc5a4c4daa61e899fe05df2a ✔️ openstack-k8s-operators-content-provider SUCCESS in 1h 35m 45s |
danpawlik
force-pushed
the
poc-zironic
branch
4 times, most recently
from
edf50ab to
aecb718
Compare
danpawlik
force-pushed
the
poc-zironic
branch
from
aecb718 to
48e1843
Compare
danpawlik
force-pushed
the
poc-zironic
branch
4 times, most recently
from
91087e3 to
027c701
Compare
|
Build failed (check pipeline). Post https://softwarefactory-project.io/zuul/t/rdoproject.org/buildset/6bd9648e591946998c4051294b4e437e ✔️ openstack-k8s-operators-content-provider SUCCESS in 1h 57m 16s |
danpawlik
force-pushed
the
poc-zironic
branch
from
027c701 to
b4f2ed6
Compare
|
Build failed (check pipeline). Post https://softwarefactory-project.io/zuul/t/rdoproject.org/buildset/cdcf666e6e5044fb81389ea41616d604 ❌ openstack-k8s-operators-content-provider FAILURE in 4m 11s |
danpawlik
force-pushed
the
poc-zironic
branch
4 times, most recently
from
f5a6ed3 to
913b4ce
Compare
|
Build failed (check pipeline). Post https://softwarefactory-project.io/zuul/t/rdoproject.org/buildset/ae0591df2b6c4f1f9b2117dea2932ac1 ✔️ openstack-k8s-operators-content-provider SUCCESS in 1h 43m 07s |
danpawlik
force-pushed
the
poc-zironic
branch
from
913b4ce to
807b4ef
Compare
|
Build failed (check pipeline). Post https://softwarefactory-project.io/zuul/t/rdoproject.org/buildset/0ca00602c8c146aa8b58f4a0f5123107 ✔️ openstack-k8s-operators-content-provider SUCCESS in 3h 17m 59s |
danpawlik
force-pushed
the
poc-zironic
branch
from
807b4ef to
27043dd
Compare
|
Build failed (check pipeline). Post https://softwarefactory-project.io/zuul/t/rdoproject.org/buildset/f14532aad6564a23aff60af2dec8a2c3 ✔️ openstack-k8s-operators-content-provider SUCCESS in 2h 22m 06s |
danpawlik
force-pushed
the
poc-zironic
branch
from
d42c099 to
8287f37
Compare
|
LGTM in general! |
danpawlik
force-pushed
the
poc-zironic
branch
from
8287f37 to
fe9836c
Compare
|
Build failed (check pipeline). Post https://softwarefactory-project.io/zuul/t/rdoproject.org/buildset/c6488c8b99bc46c4b76833a3500c0a2d ✔️ openstack-k8s-operators-content-provider SUCCESS in 2h 08m 42s |
|
recheck |
|
Build failed (check pipeline). Post https://softwarefactory-project.io/zuul/t/rdoproject.org/buildset/2856e32111a540c598f7cc485d69b25b ✔️ openstack-k8s-operators-content-provider SUCCESS in 46m 21s |
The Zironic tool would pre-deploy OCP cluster before CI job will "pick" the baremetal host. Signed-off-by: Daniel Pawlik <dpawlik@redhat.com>
Without gathering facts here, on executing reproducer playbook via Zironic or locally, the /etc/ci/env/networking-environment-definition.yml in later stage will not contain: "hostname" and "interface_name" keys, which would fail on generating network-values using ci_gen_kustomize_values. Signed-off-by: Daniel Pawlik <dpawlik@redhat.com>
The libvirt_manager is adding the VMs into the inventory during the playbook execution. It means, if Zironic would bootstrap the host, later the CI job will continue running the CI job, but it would not be able to reach the VMs, like controller-0. Add a feature that dump the VMs groups into the inventory file. Signed-off-by: Daniel Pawlik <dpawlik@redhat.com>
By moving the bootstrap procedure from job execution to ZIronic, we changed the way, what is configuring the baremetal host (BM). Normally in CI job execution, Zuul is spawning a controller, then the controller is configuring the baremetal host, then the job continuation is done on controller-0 via baremetal host. With Zironic, to avoid creating additional VM - controller - we moved the procedure to be done directly on the baremetal host. It means, that the ansible-core package needs to be available, otherwise bootstrap procedure would fail because of missing modules, libraries etc. Signed-off-by: Daniel Pawlik <dpawlik@redhat.com>
On busy host, if the restart is performed, Ansible is not waiting enough of time to continue. Sometimes it happens that the service was configured few seconds after the Ansible task that require it was executed. Retry and wait for dnsmasq to be restarted before continuation. Signed-off-by: Daniel Pawlik <dpawlik@redhat.com>
In some cases, we need to be able to resolve short host names like controller-0 and not always relay on ssh configuration file. Normally on executing the reproducer playbook, we are reading the libvirt_inventory file, that contains most of the host on which we want to connect. That feature gives just developers to connect to VMs using other tools than SSH. Signed-off-by: Daniel Pawlik <dpawlik@redhat.com>
danpawlik
force-pushed
the
poc-zironic
branch
from
fe9836c to
7be7df1
Compare
|
/approve |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: evallesp The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
3 participants
The Zironic tool would pre-deploy OCP cluster before CI job will "pick" the baremetal host.
Depends-On: #3523