Closed EmilienM closed 1 month ago
Thanks for your PR, To run vendors CIs, Maintainers can use one of:
/test-all
: To run all tests for all vendors./test-e2e-all
: To run all E2E tests for all vendors./test-e2e-nvidia-all
: To run all E2E tests for NVIDIA vendor.
To skip the vendors CIs, Maintainers can use one of:
/skip-all
: To skip all tests for all vendors./skip-e2e-all
: To skip all E2E tests for all vendors./skip-e2e-nvidia-all
: To skip all E2E tests for NVIDIA vendor.
Best regards.Changes Missing Coverage | Covered Lines | Changed/Added Lines | % | ||
---|---|---|---|---|---|
pkg/platforms/openstack/openstack.go | 5 | 67 | 7.46% | ||
<!-- | Total: | 5 | 67 | 7.46% | --> |
Totals | |
---|---|
Change from base Build 10979758277: | -0.1% |
Covered Lines: | 6628 |
Relevant Lines: | 14763 |
It's open for review but I haven't tested it yet.
/hold
/lgtm thanks
Just an update on this, the current patch doesn't work yet, I'm reworking it here: https://github.com/openshift/sriov-network-operator/pull/1004 so I can get CI feedback fairly quickly. I'll update this PR as soon as I have satisfying results and ask for reviews here.
I got a successful CI run:
2024-09-12T22:31:21.02913626Z INFO daemon/writer.go:65 CreateOpenstackDevicesInfo()
2024-09-12T22:31:21.029146361Z INFO openstack/openstack.go:118 reading OpenStack meta_data from config-drive
2024-09-12T22:31:21.057448323Z INFO openstack/openstack.go:225 found config drive device {"device": "/dev/sr0"}
2024-09-12T22:31:21.065428364Z INFO openstack/openstack.go:229 mounted config drive %s into %s {"/dev/sr0": "/tmp/sriov-configdrive2821721804"}
2024-09-12T22:31:21.066344839Z INFO openstack/openstack.go:118 reading OpenStack network_data from config-drive
2024-09-12T22:31:21.079312593Z INFO openstack/openstack.go:234 umounted config drive {"path": "/tmp/sriov-configdrive2821721804"}
@SchSeba @zeeke please review :)
Hi @EmilienM can you check the unit tests please
@SchSeba done, and sorry for the typo.
/hold cancel
When we want to use config-drive in immutable systems, very often the config-drive is only used at boot and then umounted (e.g. ignition does this).
Later when we want to fetch Metadata from the config drive, we actually have to mount it.
In this PR, I'm adding similar code than coreos/ignition where we dynamically mount the config-drive is the device was found with the right label (config-2 or CONFIG-2 as documented in OpenStack). If the device is found, we mount it, fetch the data and umount it.