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

Bug 1141955

Summary: HA: Unable to deploy HA. Getting deployment error relating to fencing params.
Product: Red Hat OpenStack Reporter: Leonid Natapov <lnatapov>
Component: rubygem-staypuftAssignee: Scott Seago <sseago>
Status: CLOSED ERRATA QA Contact: Leonid Natapov <lnatapov>
Severity: unspecified Docs Contact:
Priority: high    
Version: 5.0 (RHEL 7)CC: aberezin, ajeain, bjayavel, mburns, morazi, rhos-maint, sasha, sseago, yeylon
Target Milestone: z1Keywords: ZStream
Target Release: Installer   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ruby193-rubygem-staypuft-0.3.5-1.el6ost Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-10-02 12:56:34 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:
Bug Depends On:    
Bug Blocks: 1142873    
Attachments:
Description Flags
screen none

Description Leonid Natapov 2014-09-15 20:48:23 UTC
Created attachment 937720 [details]
screen

While trying to deploy HA getting the following error:

look at attached screen shot. Reproduced on 3 different environments.

Production log:
---------------
/opt/rh/ruby193/root/usr/share/gems/gems/rack-1.4.1/lib/rack/urlmap.rb:49:in `call'
/usr/lib/ruby/gems/1.8/gems/passenger-4.0.18/lib/phusion_passenger/rack/thread_handler_extension.rb:77:in `process_request'
/usr/lib/ruby/gems/1.8/gems/passenger-4.0.18/lib/phusion_passenger/request_handler/thread_handler.rb:140:in `accept_and_process_next_request'
/usr/lib/ruby/gems/1.8/gems/passenger-4.0.18/lib/phusion_passenger/request_handler/thread_handler.rb:108:in `main_loop'
/usr/lib/ruby/gems/1.8/gems/passenger-4.0.18/lib/phusion_passenger/request_handler.rb:441:in `block (3 levels) in start_threads'
  Rendered inline template (541.6ms)
  Rendered text template (0.0ms)
Completed 500 Internal Server Error in 1727ms (Views: 0.4ms | ActiveRecord: 15.6ms)


Started GET "/unattended/provision?token=c4fa34cb-5d33-453a-a9ca-1681e57e6e3a" for 192.168.0.3 at 2014-09-15 19:24:06 +0300
Processing by UnattendedController#provision as */*
  Parameters: {"token"=>"c4fa34cb-5d33-453a-a9ca-1681e57e6e3a"}
Found mac848f69fbc643.example.com
Remove puppet certificate for mac848f69fbc643.example.com
Adding autosign entry for mac848f69fbc643.example.com
There was error rendering string: "<%={key_id:3047}; [] if @host.bmc_nic && @host.bmc_nic.fencing_enabled? %>"
TypeError (TypeError)
/opt/rh/ruby193/root/usr/share/gems/gems/staypuft-0.3.4/app/models/staypuft/concerns/lookup_key_extensions.rb:30:in `rescue in cast_validate_value_after_erb'
/opt/rh/ruby193/root/usr/share/gems/gems/staypuft-0.3.4/app/models/staypuft/concerns/lookup_key_extensions.rb:30:in `cast_validate_value_after_erb'
/opt/rh/ruby193/root/usr/share/gems/gems/staypuft-0.3.4/app/models/staypuft/concerns/lookup_key_extensions.rb:76:in `parse_string'
/usr/share/foreman/app/services/safe_render.rb:19:in `parse'

--------------

ruby193-rubygem-foreman_openstack_simplify-0.0.6-8.el6ost.noarch
openstack-puppet-modules-2014.1-21.8.el6ost.noarch
rhel-osp-installer-0.3.4-3.el6ost.noarch
openstack-foreman-installer-2.0.23-1.el6ost.noarch

Comment 1 Scott Seago 2014-09-15 20:50:37 UTC
Fix is here (pushed to master): https://github.com/theforeman/staypuft/pull/304

THis has not been cherry-picked to the 0.3.0 (A1) branch yet.

Comment 2 Alexander Chuzhoy 2014-09-15 20:59:59 UTC
Noticed that the kickstart provision template doesn't render right - get the following:
There was an error rendering the Kickstart RHEL default template: TypeError

Comment 4 Alexander Chuzhoy 2014-09-16 18:50:42 UTC
Re-produced in another setup.
Noticed that while the kickstart provision template doesn't render right for the HA controllers, it renders with no issues for the computes under the same deployment.

Comment 5 Alexander Chuzhoy 2014-09-16 19:49:15 UTC
Setting the "fence_ipmilan_host_to_address" parameter on the "HA Controller" hostgroup to [] - causes the kickstart to be rendered with no issues, so the deployment passes the OS installation phase.

Comment 7 Scott Seago 2014-09-17 11:22:31 UTC
*** Bug 1139869 has been marked as a duplicate of this bug. ***

Comment 8 Leonid Natapov 2014-09-23 12:37:02 UTC
ruby193-rubygem-staypuft-0.3.5-1.el6ost.noarch. 

The "fence_ipmilan_host_to_address" parameter on the "HA Controller" hostgroup set to [] by default.

Comment 9 Scott Lewis 2014-10-02 12:56:34 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. http://rhn.redhat.com/errata/RHBA-2014-1350.html