Project

Profile

Help

Task #7433

Key errors during aws config up

Added by Mark Zaslavskiy over 4 years ago. Updated over 4 years ago.

Status:
Closed
Priority:
Normal
Category:
mdbci features
Sprint/Milestone:
Start date:
22.08.2016
Due date:
% Done:

0%

Estimated time:
Target branch:
Test scenario:

https://dev.osll.ru/projects/mdbci/wiki/_Wrong_time_on_server
https://dev.osll.ru/projects/mdbci/wiki/Wiki

./mdbci --template confs/aws_lite.json generate aws
./mdbci up aws

Expect: no errors


Description

Steps to reproduce:

login on maxscale-jenkins
./mdbci --template confs/aws_lite.json generate aw
./mdbci up aws/ 2>&1 | less

Expected result:

ERROR: /home/vagranttest/.vagrant.d/gems/gems/vagrant-aws-0.7.0/lib/vagrant-aws/action/run_instance.rb:98: warning: duplicated key at l
ine 100 ignored: :associate_public_ip
ERROR: /home/vagranttest/.vagrant.d/gems/gems/excon-0.49.0/lib/excon/middlewares/expects.rb:6:in `response_call': AuthFailure => AWS wa
s not able to validate the provided access credentials (Fog::Compute::AWS::Error)
ERROR: from /home/vagranttest/.vagrant.d/gems/gems/excon-0.49.0/lib/excon/middlewares/response_parser.rb:8:in `response_call'
ERROR: from /home/vagranttest/.vagrant.d/gems/gems/excon-0.49.0/lib/excon/connection.rb:389:in `response'
ERROR: from /home/vagranttest/.vagrant.d/gems/gems/excon-0.49.0/lib/excon/connection.rb:253:in `request'
ERROR: from /home/vagranttest/.vagrant.d/gems/gems/excon-0.49.0/lib/excon/middlewares/idempotent.rb:26:in `error_call'
ERROR: from /home/vagranttest/.vagrant.d/gems/gems/excon-0.49.0/lib/excon/middlewares/base.rb:10:in `error_call'
ERROR: from /home/vagranttest/.vagrant.d/gems/gems/excon-0.49.0/lib/excon/middlewares/base.rb:10:in `error_call'
ERROR: from /home/vagranttest/.vagrant.d/gems/gems/excon-0.49.0/lib/excon/connection.rb:273:in `rescue in request'
ERROR: from /home/vagranttest/.vagrant.d/gems/gems/excon-0.49.0/lib/excon/connection.rb:221:in `request'
ERROR: from /home/vagranttest/.vagrant.d/gems/gems/excon-0.49.0/lib/excon/middlewares/idempotent.rb:26:in `error_call'
ERROR: from /home/vagranttest/.vagrant.d/gems/gems/excon-0.49.0/lib/excon/middlewares/base.rb:10:in `error_call'
ERROR: from /home/vagranttest/.vagrant.d/gems/gems/excon-0.49.0/lib/excon/middlewares/base.rb:10:in `error_call'
ERROR: from /home/vagranttest/.vagrant.d/gems/gems/excon-0.49.0/lib/excon/middlewares/base.rb:10:in `error_call'
ERROR: from /home/vagranttest/.vagrant.d/gems/gems/excon-0.49.0/lib/excon/connection.rb:273:in `rescue in request'
ERROR: from /home/vagranttest/.vagrant.d/gems/gems/excon-0.49.0/lib/excon/connection.rb:221:in `request'
ERROR: from /home/vagranttest/.vagrant.d/gems/gems/excon-0.49.0/lib/excon/middlewares/idempotent.rb:26:in `error_call'
ERROR: from /home/vagranttest/.vagrant.d/gems/gems/excon-0.49.0/lib/excon/middlewares/base.rb:10:in `error_call'
ERROR: from /home/vagranttest/.vagrant.d/gems/gems/excon-0.49.0/lib/excon/middlewares/base.rb:10:in `error_call'
ERROR: from /home/vagranttest/.vagrant.d/gems/gems/excon-0.49.0/lib/excon/connection.rb:273:in `rescue in request'
ERROR: from /home/vagranttest/.vagrant.d/gems/gems/excon-0.49.0/lib/excon/connection.rb:221:in `request'
ERROR: from /home/vagranttest/.vagrant.d/gems/gems/fog-xml-0.1.2/lib/fog/xml/sax_parser_connection.rb:35:in `request'
ERROR: from /home/vagranttest/.vagrant.d/gems/gems/fog-xml-0.1.2/lib/fog/xml/connection.rb:7:in `request'
ERROR: from /home/vagranttest/.vagrant.d/gems/gems/fog-aws-0.9.2/lib/fog/aws/compute.rb:525:in `_request'
ERROR: from /home/vagranttest/.vagrant.d/gems/gems/fog-aws-0.9.2/lib/fog/aws/compute.rb:520:in `request'
ERROR: from /home/vagranttest/.vagrant.d/gems/gems/fog-aws-0.9.2/lib/fog/aws/requests/compute/describe_security_groups.rb:38:in `describe_security_groups'
ERROR: from /home/vagranttest/.vagrant.d/gems/gems/fog-aws-0.9.2/lib/fog/aws/models/compute/security_groups.rb:63:in `all'
ERROR: from /home/vagranttest/.vagrant.d/gems/gems/vagrant-aws-0.7.0/lib/vagrant-aws/action/run_instance.rb:230:in `block in allows_ssh_port?'
ERROR: from /home/vagranttest/.vagrant.d/gems/gems/vagrant-aws-0.7.0/lib/vagrant-aws/action/run_instance.rb:229:in `map'
ERROR: from /home/vagranttest/.vagrant.d/gems/gems/vagrant-aws-0.7.0/lib/vagrant-aws/action/run_instance.rb:229:in `allows_ssh_port?'
ERROR: from /home/vagranttest/.vagrant.d/gems/gems/vagrant-aws-0.7.0/lib/vagrant-aws/action/run_instance.rb:107:in `call'
ERROR: from /opt/vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/action/warden.rb:34:in `call'
ERROR: from /home/vagranttest/.vagrant.d/gems/gems/vagrant-aws-0.7.0/lib/vagrant-aws/action/elb_register_instance.rb:16:in `cal

History

#1 Updated by Alexander Kaluzhny over 4 years ago

  • Status changed from New to Active / In progress

#2 Updated by Alexander Kaluzhny over 4 years ago

  • Status changed from Active / In progress to New

#3 Updated by Alexander Kaluzhny over 4 years ago

  • Status changed from New to Active / In progress

#4 Updated by Alexander Kaluzhny over 4 years ago

  • Status changed from Active / In progress to Review
  • Assignee changed from Alexander Kaluzhny to Mark Zaslavskiy
  • Test scenario updated (diff)

Fixed time on server with command from post http://unix.stackexchange.com/a/251575
Actual command: sudo date -s "$(curl -s --head http://google.com | grep ^Date: | sed 's/Date: //g')"

https://dev.osll.ru/projects/mdbci/wiki/_Wrong_time_on_server

#5 Updated by Mark Zaslavskiy over 4 years ago

  • Status changed from Review to New
  • Assignee changed from Mark Zaslavskiy to Ilfat Kinyaev

Please rename wikipage to better describe related problem
Please also describe shortly related problem and provide link to this task in the Introduction section at https://dev.osll.ru/projects/mdbci/wiki/_Wrong_time_on_server

#6 Updated by Mark Zaslavskiy over 4 years ago

  • Assignee changed from Ilfat Kinyaev to Alexander Kaluzhny

#7 Updated by Alexander Kaluzhny over 4 years ago

  • Status changed from New to Active / In progress

#8 Updated by Alexander Kaluzhny over 4 years ago

  • Test scenario updated (diff)

#9 Updated by Alexander Kaluzhny over 4 years ago

  • Status changed from Active / In progress to Review
  • Assignee changed from Alexander Kaluzhny to Mark Zaslavskiy

#10 Updated by Mark Zaslavskiy over 4 years ago

  • Status changed from Review to Closed

#11 Updated by Mark Zaslavskiy over 4 years ago

  • Status changed from Closed to Review

#12 Updated by Mark Zaslavskiy over 4 years ago

  • Status changed from Review to Closed

Also available in: Atom PDF