Bug 1045858 - In some cases, packstack prints the wrong product kernel name
Summary: In some cases, packstack prints the wrong product kernel name
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-packstack
Version: 3.0
Hardware: Unspecified
OS: Linux
unspecified
medium
Target Milestone: ---
: 5.0 (RHEL 7)
Assignee: Ivan Chavero
QA Contact: Ami Jeain
URL:
Whiteboard:
Depends On:
Blocks: 1046324
TreeView+ depends on / blocked
 
Reported: 2013-12-22 16:09 UTC by Nir Magnezi
Modified: 2014-09-08 05:42 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 1046324 (view as bug list)
Environment:
Last Closed: 2014-06-24 20:34:38 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Nir Magnezi 2013-12-22 16:09:50 UTC
Description of problem:
=======================
Happened to me only when the installation fails, In my case due to "Command exceeded timeout" error (it took the server too long to download the new kernel).

Version-Release number of selected component (if applicable):
=============================================================
Grizzly 2013-12-20.1

How reproducible:
=================
1/1

Steps to Reproduce:
===================
1. run packstack but make sure it fails for something (I have no actual scenario for this).
2.
3.

Actual results:
===============
The RDO kernel that includes network namespace (netns) support has been installed on host <IP_ADDRESS>

Expected results:
=================
The RHOS kernel that includes network namespace (netns) support has been installed on host <IP_ADDRESS>

Additional info:
================
reproduced with RHEL6.4

When It fail:

<CONTROLLER_IP_ADDRESS>_nova.pp :                         [DONE]
                        [ERROR]

ERROR : Error appeared during Puppet run: <COMPUTE_2_IP_ADDRESS>_nova.pp
err: /Stage[main]//Exec[qemu-kvm]/returns: change from notrun to 0 failed: Command exceeded timeout at /var/tmp/packstack/e3a7b288eea54a98a0d842f07bf7c979/manifests/<COMPUTE_2_IP_ADDRESS>_nova.pp:36
You will find full trace in log /var/tmp/packstack/20131222-163228-7uERlB/manifests/<COMPUTE_2_IP_ADDRESS>_nova.pp.log
Please check log file /var/tmp/packstack/20131222-163228-7uERlB/openstack-setup.log for more information

Additional information:
 * File /root/keystonerc_admin has been created on OpenStack client host <CONTROLLER_IP_ADDRESS>. To use the command line tools you need to source the file.
 * To access the OpenStack Dashboard browse to http://<CONTROLLER_IP_ADDRESS>/dashboard.
Please, find your login credentials stored in the keystonerc_admin in your home directory.
 * To use Nagios, browse to http://<CONTROLLER_IP_ADDRESS>/nagios username : nagiosadmin, password : 123456
 * The RDO kernel that includes network namespace (netns) support has been installed on host <COMPUTE_1_IP_ADDRESS>.
 * The RDO kernel that includes network namespace (netns) support has been installed on host <COMPUTE_2_IP_ADDRESS>.
 * The RDO kernel that includes network namespace (netns) support has been installed on host <CONTROLLER_IP_ADDRESS>.
stderr:
rc: 1

When It does not fail:

 **** Installation completed successfully ****** 


Additional information: * To use the command line tools you need to source the file /root/keystonerc_admin created on <CONTROLLER_IP_ADDRESS> 
* To use the console, browse to http://<CONTROLLER_IP_ADDRESS> /dashboard 
* To use Nagios, browse to http://<CONTROLLER_IP_ADDRESS> /nagios username : nagiosadmin, password : 123456 
* Because of the kernel update the host <CONTROLLER_IP_ADDRESS> requires reboot. 
* Because of the kernel update the host <COMPUTE_1_IP_ADDRESS> requires reboot. 
* Because of the kernel update the host <COMPUTE_2_IP_ADDRESS> requires reboot. 
* The installation log file is available at: /var/tmp/packstack/20131222-134552-AcNPyG/openstack-setup.log

Comment 2 Ivan Chavero 2014-06-24 20:34:38 UTC
The timeout problems are fixed in current versions, so this problem shouldn't happen anymore.


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