Bug 1634179 - Deployment with custom stack name fails during ssh admin enablement workflow with: get_blacklisted_ip_addresses task - ERROR: The Stack (overcloud) could not be found.
Summary: Deployment with custom stack name fails during ssh admin enablement workflow ...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: python-tripleoclient
Version: 14.0 (Rocky)
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: beta
: 14.0 (Rocky)
Assignee: RHOS Maint
QA Contact: Gurenko Alex
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-09-28 21:06 UTC by Marius Cornea
Modified: 2023-09-14 04:39 UTC (History)
8 users (show)

Fixed In Version: python-tripleoclient-10.5.1-0.20180906012843.el7ost
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-01-11 11:53:25 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Launchpad 1795417 0 None None None 2018-10-01 14:39:12 UTC
OpenStack gerrit 606964 0 'None' MERGED Pass stack name to enable_ssh_admin workflow 2020-07-16 09:00:20 UTC
Red Hat Product Errata RHEA-2019:0045 0 None None None 2019-01-11 11:53:30 UTC

Description Marius Cornea 2018-09-28 21:06:11 UTC
Description of problem:
Deployment with custom stack name fails during ssh admin enablement workflow with: get_blacklisted_ip_addresses task:


2018-09-28 19:56:10Z [qe-Cloud-0]: CREATE_COMPLETE  Stack CREATE completed successfully

 Stack qe-Cloud-0/918449b3-262b-4266-8433-977ebe2e191f CREATE_COMPLETE 

Deploying overcloud configuration
Enabling ssh admin (tripleo-admin) for hosts:
192.168.24.9 192.168.24.20 192.168.24.15 192.168.24.8 192.168.24.12 192.168.24.6 192.168.24.7 192.168.24.16
Using ssh user heat-admin for initial connection.
Using ssh key at /home/stack/.ssh/id_rsa for initial connection.
Generating public/private rsa key pair.
Your identification has been saved in /tmp/tmpHGR9Fx/id_rsa.
Your public key has been saved in /tmp/tmpHGR9Fx/id_rsa.pub.
The key fingerprint is:
SHA256:diGpa4o6dN8pl6ZP2qLQDAvOcPbSMC6hG1A9UldbqFA TripleO split stack short term key
The key's randomart image is:
+---[RSA 4096]----+
|    ..E....      |
|   o..  .+       |
|  o o. .+ .      |
| . . ... . .     |
|=.=   . S .      |
|B*=*   o .       |
|==+o+ +.o        |
|.+.o *+*         |
|oo..ooBo         |
+----[SHA256]-----+
Inserting TripleO short term key for 192.168.24.9
Warning: Permanently added '192.168.24.9' (ECDSA) to the list of known hosts.
Inserting TripleO short term key for 192.168.24.20
Warning: Permanently added '192.168.24.20' (ECDSA) to the list of known hosts.
Inserting TripleO short term key for 192.168.24.15
Warning: Permanently added '192.168.24.15' (ECDSA) to the list of known hosts.
Inserting TripleO short term key for 192.168.24.8
Warning: Permanently added '192.168.24.8' (ECDSA) to the list of known hosts.
Inserting TripleO short term key for 192.168.24.12
Warning: Permanently added '192.168.24.12' (ECDSA) to the list of known hosts.
Inserting TripleO short term key for 192.168.24.6
Warning: Permanently added '192.168.24.6' (ECDSA) to the list of known hosts.
Inserting TripleO short term key for 192.168.24.7
Warning: Permanently added '192.168.24.7' (ECDSA) to the list of known hosts.
Inserting TripleO short term key for 192.168.24.16
Warning: Permanently added '192.168.24.16' (ECDSA) to the list of known hosts.
Starting ssh admin enablement workflow
Removing short term keys locally
ssh admin enablement workflow - FAILED.
Failure caused by error in tasks: get_blacklisted_ip_addresses

  get_blacklisted_ip_addresses [task_ex_id=9f129a50-b6fd-4696-a35e-fda118a95e34] -> The action raised an exception [action_ex_id=ccf58805-442c-4e13-9cce-2560a8ff9636, action_cls='<class 'mistral.actions.action_factory.HeatAction'>', attri
butes='{u'client_method_name': u'stacks.output_show'}', params='{u'stack_id': u'overcloud', u'output_key': u'BlacklistedIpAddresses'}']
 HeatAction.stacks.output_show failed: ERROR: The Stack (overcloud) could not be found.
    [action_ex_id=ccf58805-442c-4e13-9cce-2560a8ff9636, idx=0]: The action raised an exception [action_ex_id=ccf58805-442c-4e13-9cce-2560a8ff9636, action_cls='<class 'mistral.actions.action_factory.HeatAction'>', attributes='{u'client_met
hod_name': u'stacks.output_show'}', params='{u'stack_id': u'overcloud', u'output_key': u'BlacklistedIpAddresses'}']
 HeatAction.stacks.output_show failed: ERROR: The Stack (overcloud) could not be found.


Version-Release number of selected component (if applicable):
openstack-tripleo-common-9.3.1-0.20180920204842.el7ost.noarch
openstack-tripleo-heat-templates-9.0.0-0.20180919080941.0rc1.0rc1.el7ost.noarch

How reproducible:
100%

Steps to Reproduce:
1. Deploy overcloud with custom stack name:

openstack overcloud deploy \
--timeout 100 \
--templates /usr/share/openstack-tripleo-heat-templates \
--stack qe-Cloud-0 \
--libvirt-type kvm \
--ntp-server clock.redhat.com \
-e /home/stack/virt/internal.yaml \
-e /usr/share/openstack-tripleo-heat-templates/environments/network-isolation.yaml \
-e /home/stack/virt/predictable_ips_rr.yml \
-e /home/stack/virt/network/predictable-ips.yaml \
-e /home/stack/virt/network/network-environment.yaml \
-e /home/stack/virt/enable-tls.yaml \
-e /home/stack/virt/inject-trust-anchor.yaml \
-e /home/stack/virt/public_vip.yaml \
-e /usr/share/openstack-tripleo-heat-templates/environments/ssl/tls-endpoints-public-ip.yaml \
-e /home/stack/virt/hostnames.yml \
-e /usr/share/openstack-tripleo-heat-templates/environments/ceph-ansible/ceph-ansible.yaml \
-e /home/stack/virt/debug.yaml \
-e /home/stack/virt/custom_hostnames.yaml \
-e /home/stack/virt/nodes_data.yaml \
-e /home/stack/virt/docker-images.yaml \


Actual results:
Fails with ERROR: The Stack (overcloud) could not be found.

Expected results:
No failure.

Additional info:

Comment 8 errata-xmlrpc 2019-01-11 11:53:25 UTC
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/RHEA-2019:0045

Comment 9 Red Hat Bugzilla 2023-09-14 04:39:11 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days


Note You need to log in before you can comment on or make changes to this bug.