Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1232845

Summary: no progress status in overcloud deployment
Product: Red Hat OpenStack Reporter: Ofer Blaut <oblaut>
Component: python-rdomanager-oscpluginAssignee: Brad P. Crochet <brad>
Status: CLOSED DUPLICATE QA Contact: yeylon <yeylon>
Severity: high Docs Contact:
Priority: low    
Version: DirectorCC: akrivoka, calfonso, jslagle, mburns, rhel-osp-director-maint, srevivo
Target Milestone: z1Keywords: UserExperience
Target Release: Director   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-06-24 17:19:28 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Ofer Blaut 2015-06-17 15:53:19 UTC
Description of problem:

no progress status in overcloud deployment , we can't tell if the deployment  is stuck, 35% ...... or other 

example: 

[stack@puma33 ~]$ openstack overcloud deploy --plan-uuid 7665f6ea-79a8-477c-9b34-face64943192
The following templates will be written:
/tmp/tmprnuPkG/puppet/manifests/overcloud_volume.pp
/tmp/tmprnuPkG/hieradata/object.yaml
/tmp/tmprnuPkG/puppet/hieradata/common.yaml
/tmp/tmprnuPkG/provider-Swift-Storage-1.yaml
/tmp/tmprnuPkG/network/ports/net_ip_map.yaml
/tmp/tmprnuPkG/provider-Cinder-Storage-1.yaml
/tmp/tmprnuPkG/provider-Compute-1.yaml
/tmp/tmprnuPkG/network/noop.yaml
/tmp/tmprnuPkG/puppet/bootstrap-config.yaml
/tmp/tmprnuPkG/puppet/cinder-storage-post.yaml
/tmp/tmprnuPkG/provider-Ceph-Storage-1.yaml
/tmp/tmprnuPkG/puppet/controller-post-puppet.yaml
/tmp/tmprnuPkG/puppet/cinder-storage-puppet.yaml
/tmp/tmprnuPkG/puppet/manifests/overcloud_cephstorage.pp
/tmp/tmprnuPkG/puppet/hieradata/object.yaml
/tmp/tmprnuPkG/puppet/controller-puppet.yaml
/tmp/tmprnuPkG/puppet/manifests/overcloud_controller_pacemaker.pp
/tmp/tmprnuPkG/net-config-bridge.yaml
/tmp/tmprnuPkG/puppet/swift-storage-post.yaml
/tmp/tmprnuPkG/provider-Controller-1.yaml
/tmp/tmprnuPkG/network/networks.yaml
/tmp/tmprnuPkG/puppet/manifests/overcloud_object.pp
/tmp/tmprnuPkG/hieradata/controller.yaml
/tmp/tmprnuPkG/network/ports/ctlplane_vip.yaml
/tmp/tmprnuPkG/hieradata/volume.yaml
/tmp/tmprnuPkG/puppet/compute-post-puppet.yaml
/tmp/tmprnuPkG/extraconfig/tasks/yum_update.yaml
/tmp/tmprnuPkG/puppet/swift-storage-puppet.yaml
/tmp/tmprnuPkG/extraconfig/tasks/yum_update.sh
/tmp/tmprnuPkG/puppet/swift-devices-and-proxy-config.yaml
/tmp/tmprnuPkG/puppet/controller-config-pacemaker.yaml
/tmp/tmprnuPkG/puppet/compute-puppet.yaml
/tmp/tmprnuPkG/puppet/hieradata/volume.yaml
/tmp/tmprnuPkG/puppet/ceph-storage-post-puppet.yaml
/tmp/tmprnuPkG/extraconfig/controller/noop.yaml
/tmp/tmprnuPkG/network/ports/noop.yaml
/tmp/tmprnuPkG/network/ports/net_ip_list_map.yaml
/tmp/tmprnuPkG/puppet/hieradata/ceph.yaml
/tmp/tmprnuPkG/puppet/vip-config.yaml
/tmp/tmprnuPkG/puppet/hieradata/controller.yaml
/tmp/tmprnuPkG/plan.yaml
/tmp/tmprnuPkG/environment.yaml
/tmp/tmprnuPkG/puppet/ceph-storage-puppet.yaml
/tmp/tmprnuPkG/hieradata/compute.yaml
/tmp/tmprnuPkG/puppet/hieradata/compute.yaml
/tmp/tmprnuPkG/hieradata/ceph.yaml
/tmp/tmprnuPkG/puppet/manifests/overcloud_compute.pp
/tmp/tmprnuPkG/hieradata/common.yaml
/tmp/tmprnuPkG/puppet/manifests/ringbuilder.pp
/tmp/tmprnuPkG/extraconfig/post_deploy/default.yaml
/tmp/tmprnuPkG/net-config-noop.yaml
/tmp/tmprnuPkG/puppet/ceph-cluster-config.yaml
/tmp/tmprnuPkG/firstboot/userdata_default.yaml
/tmp/tmprnuPkG/puppet/all-nodes-config.yaml


Overcloud Endpoint: http://192.0.2.6:5000/v2.0/
Overcloud Deployed





Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.deploy over cloud and try to get its progress status 
2.
3.

Actual results:
no status 

Expected results:


Additional info:

Comment 1 Ana Krivokapic 2015-06-24 17:19:28 UTC

*** This bug has been marked as a duplicate of bug 1234764 ***