Description of problem: there is no output of failed/succeed for openstack overcloud images upload command Version-Release number of selected component (if applicable): python-rdomanager-oscplugin-0.0.8-13.el7ost.noarch How reproducible: 100% Steps to Reproduce: 1.having undercloud installed and using pre-built images 2.upload the images using openstack client " openstack overcloud image upload" Actual results: no output. Expected results: expected output: table with listed images were uploaded to the glance. Additional info:
same for openstack baremetal import --json instackenv.json
(In reply to Ola Pavlenko from comment #3) > same for openstack baremetal import --json instackenv.json please file this separately
[stack@instack ~]$ rpm -qa | grep python-rdomanager-oscplugin python-rdomanager-oscplugin-0.0.10-3.el7ost.noarch [stack@instack ~]$ openstack overcloud image upload Image "overcloud-full-vmlinuz" was uploaded. +--------------------------------------+------------------------+-------------+---------+--------+ | ID | Name | Disk Format | Size | Status | +--------------------------------------+------------------------+-------------+---------+--------+ | 9bf4187d-0854-4653-9382-e1377af0a32f | overcloud-full-vmlinuz | aki | 5026624 | active | +--------------------------------------+------------------------+-------------+---------+--------+ Image "overcloud-full-initrd" was uploaded. +--------------------------------------+-----------------------+-------------+----------+--------+ | ID | Name | Disk Format | Size | Status | +--------------------------------------+-----------------------+-------------+----------+--------+ | 266a3e7a-61fc-48c7-a0a3-38bbe1331a55 | overcloud-full-initrd | ari | 33613984 | active | +--------------------------------------+-----------------------+-------------+----------+--------+ Image "overcloud-full" was uploaded. +--------------------------------------+----------------+-------------+-----------+--------+ | ID | Name | Disk Format | Size | Status | +--------------------------------------+----------------+-------------+-----------+--------+ | b751229b-3a64-4459-aee1-870c440f8d23 | overcloud-full | qcow2 | 980504064 | active | +--------------------------------------+----------------+-------------+-----------+--------+ Image "bm-deploy-kernel" was uploaded. +--------------------------------------+------------------+-------------+---------+--------+ | ID | Name | Disk Format | Size | Status | +--------------------------------------+------------------+-------------+---------+--------+ | 72683534-25a8-4022-8d41-c78e46f887a1 | bm-deploy-kernel | aki | 5026624 | active | +--------------------------------------+------------------+-------------+---------+--------+ Image "bm-deploy-ramdisk" was uploaded. +--------------------------------------+-------------------+-------------+----------+--------+ | ID | Name | Disk Format | Size | Status | +--------------------------------------+-------------------+-------------+----------+--------+ | 40316d41-ce9d-41ed-9e1c-312c153bf75d | bm-deploy-ramdisk | ari | 57998865 | active | +--------------------------------------+-------------------+-------------+----------+--------+
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, 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/RHSA-2015:1862