Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Descriptionmxie@redhat.com
2023-02-21 12:13:05 UTC
Description of problem:
Modify virt-v2v-output-openstack man page to add cloud.yaml related information
Version-Release number of selected component (if applicable):
virt-v2v-2.2.0-5.el9.x86_64
How reproducible:
100%
Steps to Reproduce:
1.Check virt-v2v-output-openstack about overcloudrc file
# man virt-v2v-output-openstack |grep overcloudrc
Normally there is a file called "overcloudrc" or "keystonerc_admin" which you can simply "source" to set everything
2.Copy the overcloudrc file from OSP17.1 env to v2v appliance and source the overcloudrc file to authenticate with OpenStack.
# source /home/overcloudrc
# virt-v2v -ic vpx://root.213.207/data/10.73.212.38/?no_verify=1 -it vddk -io vddk-libdir=/home/vmware-vix-disklib-distrib -io vddk-thumbprint=09:9E:54:CF:C3:36:11:9D:7D:B6:45:E0:85:74:4D:DB:CE:24:7B:46 -ip /home/passwd -o openstack -oo server-id=v2v-appliance Auto-esx7.0-win11-x86_64-osp
[ 0.6] Setting up the source: -i libvirt -ic vpx://root.213.207/data/10.73.212.38/?no_verify=1 -it vddk Auto-esx7.0-win11-x86_64-osp
Cloud overcloud was not found.
virt-v2v: error: openstack: precheck failed, there may be a problem with
authentication, see earlier error messages
If reporting bugs, run virt-v2v with debugging enabled and include the
complete output:
virt-v2v -v -x [...]
3.Copy cloud.yaml to path '$HOME/.config/openstack/' of v2v appliance, then source overcloudrc file which contains 'export OS_CLOUD=overcloud'
# mkdir -p $HOME/.config/openstack/
# scp -r /home/clouds.yaml $HOME/.config/openstack/
# source /home/overcloudrc
# virt-v2v -ic vpx://root.212.149/data/10.73.212.36/?no_verify=1 -it vddk -io vddk-libdir=/home/vmware-vix-disklib-distrib -io vddk-thumbprint=D1:03:96:7E:11:3D:7C:4C:B6:50:28:1B:63:74:B5:40:5F:9D:9F:94 -ip /home/passwd esx8.0-rocky9-x86_64 -o openstack -oo server-id=v2v-appliance
[ 0.6] Setting up the source: -i libvirt -ic vpx://root.212.149/data/10.73.212.36/?no_verify=1 -it vddk esx8.0-rocky9-x86_64
[ 3.9] Opening the source
[ 11.1] Inspecting the source
[ 20.6] Checking for sufficient free disk space in the guest
[ 20.6] Converting Rocky Linux 9.1 (Blue Onyx) to run on KVM
.....
Actual results:
Need to copy cloud.yaml to path '$HOME/.config/openstack/' of v2v appliance to solve error 'Cloud overcloud was not found.', so virt-v2v-output-openstack man page should be updated
Expected results:
As above description
Additional info:
Comment 1Richard W.M. Jones
2023-02-21 12:27:45 UTC
Test the bug with virt-v2v-2.3.4-1.el9.x86_64
Steps:
1.Check virt-v2v-output-openstack about clouds.yaml file
# man virt-v2v-output-openstack |grep clouds.yaml -A 2 -B 1
If you need to copy overcloudrc to another machine, check if it references the "OS_CLOUD" environment variable. If so, you may have
to copy the clouds.yaml file from /etc/openstack/ or $HOME/.config/openstack/ to the other machine as well. See the section "CLOUD
CONFIGURATION" in the openstack CLI manual.
Result:
The bug has been fixed
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (virt-v2v bug fix and enhancement update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2023:6376
Description of problem: Modify virt-v2v-output-openstack man page to add cloud.yaml related information Version-Release number of selected component (if applicable): virt-v2v-2.2.0-5.el9.x86_64 How reproducible: 100% Steps to Reproduce: 1.Check virt-v2v-output-openstack about overcloudrc file # man virt-v2v-output-openstack |grep overcloudrc Normally there is a file called "overcloudrc" or "keystonerc_admin" which you can simply "source" to set everything 2.Copy the overcloudrc file from OSP17.1 env to v2v appliance and source the overcloudrc file to authenticate with OpenStack. # source /home/overcloudrc # virt-v2v -ic vpx://root.213.207/data/10.73.212.38/?no_verify=1 -it vddk -io vddk-libdir=/home/vmware-vix-disklib-distrib -io vddk-thumbprint=09:9E:54:CF:C3:36:11:9D:7D:B6:45:E0:85:74:4D:DB:CE:24:7B:46 -ip /home/passwd -o openstack -oo server-id=v2v-appliance Auto-esx7.0-win11-x86_64-osp [ 0.6] Setting up the source: -i libvirt -ic vpx://root.213.207/data/10.73.212.38/?no_verify=1 -it vddk Auto-esx7.0-win11-x86_64-osp Cloud overcloud was not found. virt-v2v: error: openstack: precheck failed, there may be a problem with authentication, see earlier error messages If reporting bugs, run virt-v2v with debugging enabled and include the complete output: virt-v2v -v -x [...] 3.Copy cloud.yaml to path '$HOME/.config/openstack/' of v2v appliance, then source overcloudrc file which contains 'export OS_CLOUD=overcloud' # mkdir -p $HOME/.config/openstack/ # scp -r /home/clouds.yaml $HOME/.config/openstack/ # source /home/overcloudrc # virt-v2v -ic vpx://root.212.149/data/10.73.212.36/?no_verify=1 -it vddk -io vddk-libdir=/home/vmware-vix-disklib-distrib -io vddk-thumbprint=D1:03:96:7E:11:3D:7C:4C:B6:50:28:1B:63:74:B5:40:5F:9D:9F:94 -ip /home/passwd esx8.0-rocky9-x86_64 -o openstack -oo server-id=v2v-appliance [ 0.6] Setting up the source: -i libvirt -ic vpx://root.212.149/data/10.73.212.36/?no_verify=1 -it vddk esx8.0-rocky9-x86_64 [ 3.9] Opening the source [ 11.1] Inspecting the source [ 20.6] Checking for sufficient free disk space in the guest [ 20.6] Converting Rocky Linux 9.1 (Blue Onyx) to run on KVM ..... Actual results: Need to copy cloud.yaml to path '$HOME/.config/openstack/' of v2v appliance to solve error 'Cloud overcloud was not found.', so virt-v2v-output-openstack man page should be updated Expected results: As above description Additional info: