Request timeout error while provisioning host in foreman using hammer cli

Abhijeet_Joshi · April 9, 2014, 1:50am

Hello,

I am using the following cli to provision a vm on ec2 -
hammer -v --show-ids host create --compute-resource-id=1
–compute-attributes="flavor_id=t1.micro,managed_ip=public,image_id=ami-75342c01"
–volume="capacity=1G" --name="ec28432" --environment-id=1
–architecture-id=1 --domain-id=1 --puppet-proxy-id=1
–operatingsystem-id=2 --partition-table-id=
–interface="type=network,network=default" --provision-method="build"

The VMis getting provisioned properly. I am providing the correct templates
because it works without displaying any errors via foreman user interface.

However, the cli prints the following request time out error and returns
even before the machine is fully configured.
Warning: Legacy config paths detected, move the following files
/etc/foreman/cli_config.yml -> /etc/hammer/cli_config.yml
[ERROR 2014-04-08 12:58:27 Exception] Error: Request Timeout
Could not create the host:
Error: Request Timeout
[ERROR 2014-04-08 12:58:27 Exception]

RestClient::RequestTimeout (Request Timeout):

/usr/lib/ruby/gems/1.8/gems/rest-client-1.6.1/lib/restclient/request.rb:174:in
`transmit'

/usr/lib/ruby/gems/1.8/gems/rest-client-1.6.1/lib/restclient/request.rb:60:in
`execute'

/usr/lib/ruby/gems/1.8/gems/rest-client-1.6.1/lib/restclient/request.rb:31:in
`execute'

/usr/lib/ruby/gems/1.8/gems/rest-client-1.6.1/lib/restclient/resource.rb:63:in
`post'

/usr/lib/ruby/gems/1.8/gems/apipie-bindings-0.0.6/lib/apipie_bindings/api.rb:196:in
`send'

/usr/lib/ruby/gems/1.8/gems/apipie-bindings-0.0.6/lib/apipie_bindings/api.rb:196:in
`http_call'

/usr/lib/ruby/gems/1.8/gems/apipie-bindings-0.0.6/lib/apipie_bindings/api.rb:155:in
`call'

/usr/lib/ruby/gems/1.8/gems/apipie-bindings-0.0.6/lib/apipie_bindings/resource.rb:14:in
`call'

/usr/lib/ruby/gems/1.8/gems/hammer_cli-0.1.0/lib/hammer_cli/./apipie/write_command.rb:31:in
`send_request'

/usr/lib/ruby/gems/1.8/gems/hammer_cli_foreman-0.1.0/lib/hammer_cli_foreman/commands.rb:79:in
`send_request'

/usr/lib/ruby/gems/1.8/gems/hammer_cli-0.1.0/lib/hammer_cli/./apipie/write_command.rb:10:in
execute' /usr/lib/ruby/gems/1.8/gems/clamp-0.6.2/lib/clamp/command.rb:67:inrun'

/usr/lib/ruby/gems/1.8/gems/hammer_cli-0.1.0/lib/hammer_cli/./apipie/…/abstract.rb:22:in
`run'

/usr/lib/ruby/gems/1.8/gems/clamp-0.6.2/lib/clamp/subcommand/execution.rb:11:in
execute' /usr/lib/ruby/gems/1.8/gems/clamp-0.6.2/lib/clamp/command.rb:67:inrun'

/usr/lib/ruby/gems/1.8/gems/hammer_cli-0.1.0/lib/hammer_cli/./apipie/…/abstract.rb:22:in
`run'

/usr/lib/ruby/gems/1.8/gems/clamp-0.6.2/lib/clamp/subcommand/execution.rb:11:in
execute' /usr/lib/ruby/gems/1.8/gems/clamp-0.6.2/lib/clamp/command.rb:67:inrun'

/usr/lib/ruby/gems/1.8/gems/hammer_cli-0.1.0/lib/hammer_cli/./apipie/…/abstract.rb:22:in
run' /usr/lib/ruby/gems/1.8/gems/clamp-0.6.2/lib/clamp/command.rb:125:inrun'
/usr/lib/ruby/gems/1.8/gems/hammer_cli-0.1.0/bin/hammer:100
/usr/bin/hammer:19:in `load'
/usr/bin/hammer:19

I tried to look for any timeout parameter in hammer, but didnt find one.
Is there any way to set timeout duration? How to resolve this error?

Best regards,
Abhijeet

Tomas_Strachota · April 9, 2014, 8:05am

Hello,
there's request_timeout setting in the config file since hammer 0.1.0.
Please check your version and settings.

You can compare your setting with the default config file of
hammer-cli-foreman:

github.com

theforeman/hammer-cli-foreman/blob/master/config/foreman.yml

:foreman:
  # Enable/disable foreman commands
  :enable_module: true

  # Your foreman server address
  :host: 'https://localhost/'

  # Credentials. You'll be asked for them interactively if you leave them blank here
  :username: 'admin'
  #:password: 'example'

  # Enable using sessions
  # When sessions are enabled, hammer ignores credentials stored in the config file
  # and asks for them interactively at the begining of each session.
  :use_sessions: false

  # Check API documentation cache status on each request
  #:refresh_cache: false

  # API request timeout. Set to -1 for no timeout

This file has been truncated. show original

Timeouts can be disable completely by setting -1 there.

Btw according to the log you sent you're using old config file location.
Please follow the instructions from the log and do:
mv /etc/foreman/cli_config.yml /etc/hammer/cli_config.yml

The old locations are still working as we wanted to keep it backward
compatible for some time but it's better to fix it sooner than later.
There's more about the new way of plugin configuration here:

github.com

theforeman/hammer-cli/blob/master/doc/installation.md#plugins

Installation
------------

Hammer CLI is packaged for the following RPM based distributions:

 - RHEL and derivatives, version 6
 - Fedora 18, 19
 - Debian Wheezy, Squeezy
 - Ubuntu Precise

### Select your way of installation
- [Installation from RPMs](installation_rpm.md#installation-from-rpms)
- [Installation from DEBs](installation_deb.md#installation-from-debs)
- [Installation from GEMs](installation_gem.md#installation-from-gems)
- [Installation from source](installation_source.md#installation-from-source)


Configuration
-------------

This file has been truncated. show original

Regards
Tomas Strachota

···

On 04/09/2014 03:50 AM, Abhijeet Joshi wrote: > Hello, > > I am using the following cli to provision a vm on ec2 - > hammer -v --show-ids host create --compute-resource-id=1 > --compute-attributes="flavor_id=t1.micro,managed_ip=public,image_id=ami-75342c01" --volume="capacity=1G" --name="ec28432" --environment-id=1 --architecture-id=1 --domain-id=1 --puppet-proxy-id=1 --operatingsystem-id=2 --partition-table-id= --interface="type=network,network=default" --provision-method="build" > > The VMis getting provisioned properly. I am providing the correct > templates because it works without displaying any errors via foreman > user interface. > > However, the cli prints the following request time out error and returns > even before the machine is fully configured. > Warning: Legacy config paths detected, move the following files > /etc/foreman/cli_config.yml -> /etc/hammer/cli_config.yml > [ERROR 2014-04-08 12:58:27 Exception] Error: Request Timeout > Could not create the host: > Error: Request Timeout > [ERROR 2014-04-08 12:58:27 Exception] > > RestClient::RequestTimeout (Request Timeout): > > /usr/lib/ruby/gems/1.8/gems/rest-client-1.6.1/lib/restclient/request.rb:174:in > `transmit' > > /usr/lib/ruby/gems/1.8/gems/rest-client-1.6.1/lib/restclient/request.rb:60:in > `execute' > > /usr/lib/ruby/gems/1.8/gems/rest-client-1.6.1/lib/restclient/request.rb:31:in > `execute' > > /usr/lib/ruby/gems/1.8/gems/rest-client-1.6.1/lib/restclient/resource.rb:63:in > `post' > > /usr/lib/ruby/gems/1.8/gems/apipie-bindings-0.0.6/lib/apipie_bindings/api.rb:196:in > `send' > > /usr/lib/ruby/gems/1.8/gems/apipie-bindings-0.0.6/lib/apipie_bindings/api.rb:196:in > `http_call' > > /usr/lib/ruby/gems/1.8/gems/apipie-bindings-0.0.6/lib/apipie_bindings/api.rb:155:in > `call' > > /usr/lib/ruby/gems/1.8/gems/apipie-bindings-0.0.6/lib/apipie_bindings/resource.rb:14:in > `call' > > /usr/lib/ruby/gems/1.8/gems/hammer_cli-0.1.0/lib/hammer_cli/./apipie/write_command.rb:31:in > `send_request' > > /usr/lib/ruby/gems/1.8/gems/hammer_cli_foreman-0.1.0/lib/hammer_cli_foreman/commands.rb:79:in > `send_request' > > /usr/lib/ruby/gems/1.8/gems/hammer_cli-0.1.0/lib/hammer_cli/./apipie/write_command.rb:10:in > `execute' > /usr/lib/ruby/gems/1.8/gems/clamp-0.6.2/lib/clamp/command.rb:67:in > `run' > > /usr/lib/ruby/gems/1.8/gems/hammer_cli-0.1.0/lib/hammer_cli/./apipie/../abstract.rb:22:in > `run' > > /usr/lib/ruby/gems/1.8/gems/clamp-0.6.2/lib/clamp/subcommand/execution.rb:11:in > `execute' > /usr/lib/ruby/gems/1.8/gems/clamp-0.6.2/lib/clamp/command.rb:67:in > `run' > > /usr/lib/ruby/gems/1.8/gems/hammer_cli-0.1.0/lib/hammer_cli/./apipie/../abstract.rb:22:in > `run' > > /usr/lib/ruby/gems/1.8/gems/clamp-0.6.2/lib/clamp/subcommand/execution.rb:11:in > `execute' > /usr/lib/ruby/gems/1.8/gems/clamp-0.6.2/lib/clamp/command.rb:67:in > `run' > > /usr/lib/ruby/gems/1.8/gems/hammer_cli-0.1.0/lib/hammer_cli/./apipie/../abstract.rb:22:in > `run' > /usr/lib/ruby/gems/1.8/gems/clamp-0.6.2/lib/clamp/command.rb:125:in > `run' > /usr/lib/ruby/gems/1.8/gems/hammer_cli-0.1.0/bin/hammer:100 > /usr/bin/hammer:19:in `load' > /usr/bin/hammer:19 > > I tried to look for any timeout parameter in hammer, but didnt find one. > Is there any way to set timeout duration? How to resolve this error? > > Best regards, > Abhijeet >

Abhijeet_Joshi · April 10, 2014, 6:56am

Hello Tomas,

Tried that. But getting error. Looks like a bug?
hammer -v --show-ids host create --compute-resource-id=1
–compute-attributes="flavor_id=t1.micro,managed_ip=public,image_id=ami-8aa3a8fe"
–volume="capacity=1G" --name="ec21041" --environment-id=1
–architecture-id=1 --domain-id=1 --puppet-proxy-id=1
–operatingsystem-id=1 --partition-table-id=
–interface="type=network,network=default" --provision-method="build"
–puppetclass-ids="2,3"
[ERROR 2014-04-10 02:27:22 Exception] time interval must be positive
Could not create the host:
time interval must be positive
[ERROR 2014-04-10 02:27:22 Exception]

ArgumentError (time interval must be positive):
/usr/lib/ruby/1.8/timeout.rb:60:in sleep' /usr/lib/ruby/1.8/timeout.rb:60:intimeout'

/usr/lib/ruby/gems/1.8/gems/logging-1.8.1/lib/logging/diagnostic_context.rb:323:in
`call'

/usr/lib/ruby/gems/1.8/gems/logging-1.8.1/lib/logging/diagnostic_context.rb:323:in
`create_with_logging_context'

/usr/lib/ruby/gems/1.8/gems/logging-1.8.1/lib/logging/diagnostic_context.rb:320:in
`_orig_start'

/usr/lib/ruby/gems/1.8/gems/logging-1.8.1/lib/logging/diagnostic_context.rb:320:in
`send'

/usr/lib/ruby/gems/1.8/gems/logging-1.8.1/lib/logging/diagnostic_context.rb:320:in
`create_with_logging_context'

/usr/lib/ruby/gems/1.8/gems/logging-1.8.1/lib/logging/diagnostic_context.rb:288:in
`start'

Hammer is at 0.1.0
hammer --version
hammer (0.1.0)

hammer_cli_foreman (0.1.0)

The contents of /etc/hammer/cli_config.yml file
:modules:

hammer_cli_foreman

- hammer_cli_katello_bridge

:foreman:
:host: 'https://localhost/'
:username: 'admin'
:password: 'changeme'

:request_timeout: -1

:log_dir: '~/.foreman/log'
:log_level: 'error'
:log_api_calls: false

Regards,
Abhijeet

mbacovsky · April 15, 2014, 9:56am

> Hello Tomas,
>
> Tried that. But getting error. Looks like a bug?

It seems that somewhere during 1.8.7 ruby stopped accepting negative
timeouts. (more on that https://projects.puppetlabs.com/issues/4769)
And it seems that later RestClient was improved to cope with that as I
can not reproduce your error.
I assume you have Ruby not accepting negative timeout and version of
restclient that can't handle that. Proper fix would be to update
dependency on rest-client with the fix included, but I need to
investigate more on that.

As a workaround you can set unreasonably big number for the timeout (it
is in seconds)

HTH, Martin

···

On 04/10/2014 08:56 AM, Abhijeet Joshi wrote:

hammer -v --show-ids host create --compute-resource-id=1
–compute-attributes=“flavor_id=t1.micro,managed_ip=public,image_id=ami-8aa3a8fe”
–volume=“capacity=1G” --name=“ec21041” --environment-id=1
–architecture-id=1 --domain-id=1 --puppet-proxy-id=1
–operatingsystem-id=1 --partition-table-id=
–interface=“type=network,network=default” --provision-method=“build”
–puppetclass-ids=“2,3”
[ERROR 2014-04-10 02:27:22 Exception] time interval must be positive
Could not create the host:
time interval must be positive
[ERROR 2014-04-10 02:27:22 Exception]

ArgumentError (time interval must be positive):
/usr/lib/ruby/1.8/timeout.rb:60:in sleep' /usr/lib/ruby/1.8/timeout.rb:60:intimeout’
/usr/lib/ruby/gems/1.8/gems/logging-1.8.1/lib/logging/diagnostic_context.rb:323:in
call' /usr/lib/ruby/gems/1.8/gems/logging-1.8.1/lib/logging/diagnostic_context.rb:323:increate_with_logging_context’
/usr/lib/ruby/gems/1.8/gems/logging-1.8.1/lib/logging/diagnostic_context.rb:320:in
_orig_start' /usr/lib/ruby/gems/1.8/gems/logging-1.8.1/lib/logging/diagnostic_context.rb:320:insend’
/usr/lib/ruby/gems/1.8/gems/logging-1.8.1/lib/logging/diagnostic_context.rb:320:in
create_with_logging_context' /usr/lib/ruby/gems/1.8/gems/logging-1.8.1/lib/logging/diagnostic_context.rb:288:instart’

Hammer is at 0.1.0
hammer --version
hammer (0.1.0)

hammer_cli_foreman (0.1.0)

The contents of /etc/hammer/cli_config.yml file
:modules:

hammer_cli_foreman

- hammer_cli_katello_bridge

:foreman:
:host: ‘https://localhost/’
:username: ‘admin’
:password: ‘changeme’
:request_timeout: -1
:log_dir: ‘~/.foreman/log’
:log_level: ‘error’
:log_api_calls: false

Regards,
Abhijeet

You received this message because you are subscribed to the Google
Groups “Foreman users” group.
To unsubscribe from this group and stop receiving emails from it, send
an email to foreman-users+unsubscribe@googlegroups.com
mailto:foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com
mailto:foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

Abhijeet_Joshi · April 15, 2014, 11:20am

@Martin,

Gave a timeout of 1800 seconds, that worked perfectly.
Thanks a lot.

Regards,
Abhijeet

···

On Tuesday, April 15, 2014 3:26:20 PM UTC+5:30, Martin Bačovský wrote: > > On 04/10/2014 08:56 AM, Abhijeet Joshi wrote: > > Hello Tomas, > > Tried that. But getting error. Looks like a bug? > > > It seems that somewhere during 1.8.7 ruby stopped accepting negative > timeouts. (more on that https://projects.puppetlabs.com/issues/4769) > And it seems that later RestClient was improved to cope with that as I can > not reproduce your error. > I assume you have Ruby not accepting negative timeout and version of > restclient that can't handle that. Proper fix would be to update dependency > on rest-client with the fix included, but I need to investigate more on > that. > > As a workaround you can set unreasonably big number for the timeout (it is > in seconds) > > HTH, Martin > > hammer -v --show-ids host create --compute-resource-id=1 > --compute-attributes="flavor_id=t1.micro,managed_ip=public,image_id=ami-8aa3a8fe" > --volume="capacity=1G" --name="ec21041" --environment-id=1 > --architecture-id=1 --domain-id=1 --puppet-proxy-id=1 > --operatingsystem-id=1 --partition-table-id= > --interface="type=network,network=default" --provision-method="build" > --puppetclass-ids="2,3" > [ERROR 2014-04-10 02:27:22 Exception] time interval must be positive > Could not create the host: > time interval must be positive > [ERROR 2014-04-10 02:27:22 Exception] > > ArgumentError (time interval must be positive): > /usr/lib/ruby/1.8/timeout.rb:60:in `sleep' > /usr/lib/ruby/1.8/timeout.rb:60:in `timeout' > > /usr/lib/ruby/gems/1.8/gems/logging-1.8.1/lib/logging/diagnostic_context.rb:323:in > `call' > > /usr/lib/ruby/gems/1.8/gems/logging-1.8.1/lib/logging/diagnostic_context.rb:323:in > `create_with_logging_context' > > /usr/lib/ruby/gems/1.8/gems/logging-1.8.1/lib/logging/diagnostic_context.rb:320:in > `_orig_start' > > /usr/lib/ruby/gems/1.8/gems/logging-1.8.1/lib/logging/diagnostic_context.rb:320:in > `send' > > /usr/lib/ruby/gems/1.8/gems/logging-1.8.1/lib/logging/diagnostic_context.rb:320:in > `create_with_logging_context' > > /usr/lib/ruby/gems/1.8/gems/logging-1.8.1/lib/logging/diagnostic_context.rb:288:in > `start' > > Hammer is at 0.1.0 > hammer --version > hammer (0.1.0) > * hammer_cli_foreman (0.1.0) > > The contents of /etc/hammer/cli_config.yml file > :modules: > - hammer_cli_foreman > # - hammer_cli_katello_bridge > > :foreman: > :host: 'https://localhost/' > :username: 'admin' > :password: 'changeme' > > :request_timeout: -1 > > :log_dir: '~/.foreman/log' > :log_level: 'error' > :log_api_calls: false > > > Regards, > Abhijeet > -- > You received this message because you are subscribed to the Google Groups > "Foreman users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to foreman-user...@googlegroups.com . > To post to this group, send email to forema...@googlegroups.com > . > Visit this group at http://groups.google.com/group/foreman-users. > For more options, visit https://groups.google.com/d/optout. > > >

Tomas_Strachota · April 16, 2014, 7:01am

> @Martin,
>
> Gave a timeout of 1800 seconds, that worked perfectly.
> Thanks a lot.
>
> Regards,
> Abhijeet

FYI I looked into the issue and setting timeout to 0 should give you
infinite timeouts reliably.
http://projects.theforeman.org/issues/5209

···

On 04/15/2014 01:20 PM, Abhijeet Joshi wrote:

On Tuesday, April 15, 2014 3:26:20 PM UTC+5:30, Martin Bačovský wrote:

On 04/10/2014 08:56 AM, Abhijeet Joshi wrote:

Hello Tomas,

Tried that. But getting error. Looks like a bug?

It seems that somewhere during 1.8.7 ruby stopped accepting negative
timeouts. (more on that https://projects.puppetlabs.com/issues/4769
<https://projects.puppetlabs.com/issues/4769>)
And it seems that later RestClient was improved to cope with that as
I can not reproduce your error.
I assume you have Ruby not accepting negative timeout and version of
restclient that can't handle that. Proper fix would be to update
dependency on rest-client with the fix included, but I need to
investigate more on that.

As a workaround you can set unreasonably big number for the timeout
(it is in seconds)

HTH, Martin

 hammer -v --show-ids host create  --compute-resource-id=1
 --compute-attributes="flavor_id=t1.micro,managed_ip=public,image_id=ami-8aa3a8fe"
--volume="capacity=1G" --name="ec21041" --environment-id=1
--architecture-id=1 --domain-id=1 --puppet-proxy-id=1
--operatingsystem-id=1 --partition-table-id=
--interface="type=network,network=default"
 --provision-method="build"  --puppetclass-ids="2,3"
[ERROR 2014-04-10 02:27:22 Exception] time interval must be positive
Could not create the host:
  time interval must be positive
[ERROR 2014-04-10 02:27:22 Exception]

ArgumentError (time interval must be positive):
    /usr/lib/ruby/1.8/timeout.rb:60:in `sleep'
    /usr/lib/ruby/1.8/timeout.rb:60:in `timeout'
/usr/lib/ruby/gems/1.8/gems/logging-1.8.1/lib/logging/diagnostic_context.rb:323:in
`call'
/usr/lib/ruby/gems/1.8/gems/logging-1.8.1/lib/logging/diagnostic_context.rb:323:in
`create_with_logging_context'
/usr/lib/ruby/gems/1.8/gems/logging-1.8.1/lib/logging/diagnostic_context.rb:320:in
`_orig_start'
/usr/lib/ruby/gems/1.8/gems/logging-1.8.1/lib/logging/diagnostic_context.rb:320:in
`send'
/usr/lib/ruby/gems/1.8/gems/logging-1.8.1/lib/logging/diagnostic_context.rb:320:in
`create_with_logging_context'
/usr/lib/ruby/gems/1.8/gems/logging-1.8.1/lib/logging/diagnostic_context.rb:288:in
`start'

Hammer is at 0.1.0
 hammer --version
hammer (0.1.0)
 * hammer_cli_foreman (0.1.0)

The contents of  /etc/hammer/cli_config.yml file
:modules:
  - hammer_cli_foreman
#  - hammer_cli_katello_bridge

:foreman:
    :host: 'https://localhost/'
    :username: 'admin'
    :password: 'changeme'

    :request_timeout: -1

:log_dir: '~/.foreman/log'
:log_level: 'error'
:log_api_calls: false


Regards,
Abhijeet
--
You received this message because you are subscribed to the Google
Groups "Foreman users" group.
To unsubscribe from this group and stop receiving emails from it,
send an email to foreman-user...@googlegroups.com <javascript:>.
To post to this group, send email to forema...@googlegroups.com
<javascript:>.
Visit this group at http://groups.google.com/group/foreman-users
<http://groups.google.com/group/foreman-users>.
For more options, visit https://groups.google.com/d/optout
<https://groups.google.com/d/optout>.

–
You received this message because you are subscribed to the Google
Groups “Foreman users” group.
To unsubscribe from this group and stop receiving emails from it, send
an email to foreman-users+unsubscribe@googlegroups.com
mailto:foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com
mailto:foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

Abhijeet_Joshi · April 16, 2014, 1:07pm

Thanks a lot Tomas for following this up.
Is this change in hammer 0.1.0? Will I be able to test this if I update
hammer only?

-Abhijeet

Bryan_Kearney · April 16, 2014, 1:22pm

In some docs some place?

– bk

···

Sent with thumbs

On Apr 16, 2014, at 12:01 AM, Tomas Strachota tstrachota@redhat.com wrote:

On 04/15/2014 01:20 PM, Abhijeet Joshi wrote:
@Martin,

Gave a timeout of 1800 seconds, that worked perfectly.
Thanks a lot.

Regards,
Abhijeet

FYI I looked into the issue and setting timeout to 0 should give you infinite timeouts reliably.
Bug #5209: Negative timeout config value causes errors - Hammer CLI - Foreman
On Tuesday, April 15, 2014 3:26:20 PM UTC+5:30, Martin Bačovský wrote:

On 04/10/2014 08:56 AM, Abhijeet Joshi wrote:

Hello Tomas,

Tried that. But getting error. Looks like a bug?

It seems that somewhere during 1.8.7 ruby stopped accepting negative
timeouts. (more on that https://projects.puppetlabs.com/issues/4769
https://projects.puppetlabs.com/issues/4769)
And it seems that later RestClient was improved to cope with that as
I can not reproduce your error.
I assume you have Ruby not accepting negative timeout and version of
restclient that can’t handle that. Proper fix would be to update
dependency on rest-client with the fix included, but I need to
investigate more on that.

As a workaround you can set unreasonably big number for the timeout
(it is in seconds)

HTH, Martin
hammer -v --show-ids host create  --compute-resource-id=1
--compute-attributes="flavor_id=t1.micro,managed_ip=public,image_id=ami-8aa3a8fe"
–volume=“capacity=1G” --name=“ec21041” --environment-id=1
–architecture-id=1 --domain-id=1 --puppet-proxy-id=1
–operatingsystem-id=1 --partition-table-id=
–interface=“type=network,network=default”
–provision-method=“build” --puppetclass-ids=“2,3”
[ERROR 2014-04-10 02:27:22 Exception] time interval must be positive
Could not create the host:
time interval must be positive
[ERROR 2014-04-10 02:27:22 Exception]

ArgumentError (time interval must be positive):
/usr/lib/ruby/1.8/timeout.rb:60:in sleep' /usr/lib/ruby/1.8/timeout.rb:60:intimeout’
/usr/lib/ruby/gems/1.8/gems/logging-1.8.1/lib/logging/diagnostic_context.rb:323:in
call' /usr/lib/ruby/gems/1.8/gems/logging-1.8.1/lib/logging/diagnostic_context.rb:323:increate_with_logging_context’
/usr/lib/ruby/gems/1.8/gems/logging-1.8.1/lib/logging/diagnostic_context.rb:320:in
_orig_start' /usr/lib/ruby/gems/1.8/gems/logging-1.8.1/lib/logging/diagnostic_context.rb:320:insend’
/usr/lib/ruby/gems/1.8/gems/logging-1.8.1/lib/logging/diagnostic_context.rb:320:in
create_with_logging_context' /usr/lib/ruby/gems/1.8/gems/logging-1.8.1/lib/logging/diagnostic_context.rb:288:instart’

Hammer is at 0.1.0
hammer --version
hammer (0.1.0)
* hammer_cli_foreman (0.1.0)

The contents of /etc/hammer/cli_config.yml file
:modules:
- hammer_cli_foreman

- hammer_cli_katello_bridge

:foreman:
:host: ‘https://localhost/’
:username: ‘admin’
:password: ‘changeme’
   :request_timeout: -1
:log_dir: ‘~/.foreman/log’
:log_level: ‘error’
:log_api_calls: false

Regards,
Abhijeet

You received this message because you are subscribed to the Google
Groups “Foreman users” group.
To unsubscribe from this group and stop receiving emails from it,
send an email to foreman-user...@googlegroups.com <javascript:>.
To post to this group, send email to forema...@googlegroups.com
<javascript:>.
Visit this group at http://groups.google.com/group/foreman-users
http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout
https://groups.google.com/d/optout.
–
You received this message because you are subscribed to the Google
Groups “Foreman users” group.
To unsubscribe from this group and stop receiving emails from it, send
an email to foreman-users+unsubscribe@googlegroups.com
mailto:foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com
mailto:foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.
–
You received this message because you are subscribed to the Google Groups “Foreman users” group.
To unsubscribe from this group and stop receiving emails from it, send an email to foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

Tomas_Strachota · April 17, 2014, 7:59am

Yes, hammer 0.1.0 will allow you to set 0. You can already test it if
you have the latest version.

T.

···

On 04/16/2014 03:07 PM, Abhijeet Joshi wrote: > Thanks a lot Tomas for following this up. > Is this change in hammer 0.1.0? Will I be able to test this if I update > hammer only? > > -Abhijeet >

Request timeout error while provisioning host in foreman using hammer cli

- hammer_cli_katello_bridge

- hammer_cli_katello_bridge

Regards, Abhijeet

- hammer_cli_katello_bridge

Regards, Abhijeet

Regards,
Abhijeet

Regards,
Abhijeet