error "sh: /etc/puppet/modules/osnailyfacter/modular/astute/generate_haproxy_keys.sh: No such file or directory"

Bug #1620435 reported by Peter Wang
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Invalid
High
Peter Wang

Bug Description

When I tried to deploy fuel-7.0, I met folllowing error:

type: shell
uids:
- master
parameters:
  retries: 3
  cmd: sh /etc/puppet/modules/osnailyfacter/modular/astute/generate_haproxy_keys.sh
    -i 3 -h public.fuel.local -o 'haproxy' -p /var/lib/fuel/keys/
  cwd: "/"
  timeout: 180
  interval: 1

2016-09-05T10:32:35 debug: [551] 2bc16093-2e4e-4e10-87ac-0b04792cd774: MC agent 'execute_shell_command', method 'execute', results: {:send
2016-09-05T10:32:35 debug: [551] 2bc16093-2e4e-4e10-87ac-0b04792cd774: cmd: cd / && sh /etc/puppet/modules/osnailyfacter/modular/astute/ge
cwd: /
stdout:
stderr: sh: /etc/puppet/modules/osnailyfacter/modular/astute/generate_haproxy_keys.sh: No such file or directory

exit code: 127

==================================
but when i executed this command, it succeeded.

[root@fuel-master docker-logs]# sh /etc/puppet/modules/osnailyfacter/modular/astute/generate_haproxy_keys.sh -i 3 -h public.fuel.local -o
'haproxy' -p /var/lib/fuel/keys/
Generating a 2048 bit RSA private key
..........................+++
.......+++
writing new private key to '/var/lib/fuel/keys//3/haproxy/public_haproxy.key'
-----

Can anyone help me out?

ENVIRONMENT:
fuel-7.0(kilo) on virtualbox

Thanks
Peter

Revision history for this message
Peter Wang (peter.wang) wrote :

more logs from astute.log

2016-09-05T15:58:47 debug: [572] 3c22e3cd-7921-450a-9e53-91e425461db0: MC agent 'execute_shell_command', method 'execute', results: {:sender=>"master", :statuscode=>0, :statusmsg=>"OK", :data=>{:stdout=>"", :stderr=>"sh: /etc/puppet/modules/osnailyfacter/modular/astute/generate_haproxy_keys.sh: No such file or directory\n", :exit_code=>127}}
2016-09-05T15:58:47 debug: [572] 3c22e3cd-7921-450a-9e53-91e425461db0: cmd: cd / && sh /etc/puppet/modules/osnailyfacter/modular/astute/generate_haproxy_keys.sh -i 1 -h public.fuel.local -o 'haproxy' -p /var/lib/fuel/keys/
cwd: /
stdout:
stderr: sh: /etc/puppet/modules/osnailyfacter/modular/astute/generate_haproxy_keys.sh: No such file or directory

exit code: 127

Revision history for this message
Peter Wang (peter.wang) wrote :

priority: 300
type: shell
uids:
- master
parameters:
  retries: 3
  cmd: sh /etc/puppet/modules/osnailyfacter/modular/astute/generate_haproxy_keys.sh
    -i 1 -h public.fuel.local -o 'haproxy' -p /var/lib/fuel/keys/
  cwd: "/"
  timeout: 180
  interval: 1
 traceback
["/usr/lib64/ruby/gems/2.1.0/gems/astute-7.0.0/lib/astute/nailgun_hooks.rb:59:in `block in process'",
 "/usr/lib64/ruby/gems/2.1.0/gems/astute-7.0.0/lib/astute/nailgun_hooks.rb:26:in `each'",
 "/usr/lib64/ruby/gems/2.1.0/gems/astute-7.0.0/lib/astute/nailgun_hooks.rb:26:in `process'",
 "/usr/lib64/ruby/gems/2.1.0/gems/astute-7.0.0/lib/astute/deployment_engine/granular_deployment.rb:203:in `pre_deployment_actions'",
 "/usr/lib64/ruby/gems/2.1.0/gems/astute-7.0.0/lib/astute/deployment_engine.rb:36:in `deploy'",
 "/usr/lib64/ruby/gems/2.1.0/gems/astute-7.0.0/lib/astute/orchestrator.rb:179:in `deploy_cluster'",
 "/usr/lib64/ruby/gems/2.1.0/gems/astute-7.0.0/lib/astute/orchestrator.rb:45:in `granular_deploy'",
 "/usr/lib64/ruby/gems/2.1.0/gems/astute-7.0.0/lib/astute/server/dispatcher.rb:91:in `granular_deploy'",
 "/usr/lib64/ruby/gems/2.1.0/gems/astute-7.0.0/lib/astute/server/server.rb:146:in `dispatch_message'",
 "/usr/lib64/ruby/gems/2.1.0/gems/astute-7.0.0/lib/astute/server/server.rb:107:in `block in dispatch'",
 "/usr/lib64/ruby/gems/2.1.0/gems/astute-7.0.0/lib/astute/server/task_queue.rb:64:in `call'",
 "/usr/lib64/ruby/gems/2.1.0/gems/astute-7.0.0/lib/astute/server/task_queue.rb:64:in `block in each'",
 "/usr/lib64/ruby/gems/2.1.0/gems/astute-7.0.0/lib/astute/server/task_queue.rb:56:in `each'",
 "/usr/lib64/ruby/gems/2.1.0/gems/astute-7.0.0/lib/astute/server/task_queue.rb:56:in `each'",
 "/usr/lib64/ruby/gems/2.1.0/gems/astute-7.0.0/lib/astute/server/server.rb:105:in `each_with_index'",
 "/usr/lib64/ruby/gems/2.1.0/gems/astute-7.0.0/lib/astute/server/server.rb:105:in `dispatch'",
 "/usr/lib64/ruby/gems/2.1.0/gems/astute-7.0.0/lib/astute/server/server.rb:89:in `block in perform_main_job'"]

Changed in fuel:
assignee: nobody → MOS Maintenance (mos-maintenance)
importance: Undecided → High
status: New → Confirmed
milestone: none → 7.0-updates
Revision history for this message
Peter Wang (peter.wang) wrote :

Hi Alexey

Thanks for the confirmation.
while you are fixing this, could you please provide me a workaround so that I can proceed with mos 7.0 installation?

Thanks
Peter

Changed in fuel:
assignee: MOS Maintenance (mos-maintenance) → Alexey Stupnikov (astupnikov)
Revision history for this message
Alexey Stupnikov (astupnikov) wrote :

I was unable to reproduce this issue on KVM and QEMU hypervisors. Since it affects 1 person, I assume that it is not a general virtualbox problem. We have to have exact information about physical host OS, virtualbox version, and other specific parameters (like virtual storage type and its configuration). It will also be nice to have and archive with log files attached.

This issue looks incomplete to me, we need to clarify it. Moving to Incomplete and assigning back to reporter.

Changed in fuel:
status: Confirmed → Incomplete
assignee: Alexey Stupnikov (astupnikov) → Peter Wang (peter.wang)
Revision history for this message
Peter Wang (peter.wang) wrote :

I haven't meet this issue again, Will open it it occurs again.

Changed in fuel:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.