Did you try to increase the timeout value eg: from 300 to 600 and try again to see if this issue is gone?

I am unable to figure out as to where I can modify the time out value in the script.

It is not the timeout... see below.

++ glance image-create --name user --public --disk-format qcow2 --container-format bare --file /root/tripleo/user.qcow2
+------------------+--------------------------------------+
| Property         | Value                                |
+------------------+--------------------------------------+
| checksum         | ba56450f1d7e13e7bbf492e77a1bfdf1     |
| container_format | bare                                 |
| created_at       | 2014-05-19T20:50:15                  |
| deleted          | False                                |
| deleted_at       | None                                 |
| disk_format      | qcow2                                |
| id               | bee49368-97f0-465d-8b62-f8838663475f |
| is_public        | True                                 |
| min_disk         | 0                                    |
| min_ram          | 0                                    |
| name             | user                                 |
| owner            | 9218c546b1d7445cb653289a37b4b957     |
| protected        | False                                |
| size             | 245010944                            |
| status           | active                               |
| updated_at       | 2014-05-19T20:51:23                  |
| virtual_size     | None                                 |
+------------------+--------------------------------------+
++ '[' 0 -eq 0 ']'
++ break
++ set -e
**++ wait_for 300 10 nova service-list --binary nova-compute '2>/dev/null' '|' grep 'enabled.*\ up\ '
Timing out after 3000 seconds:**
COMMAND=nova service-list --binary nova-compute 2>/dev/null | grep enabled.*\ up\
OUTPUT=
root@hLinux:~#

ok, from your comment, the nova service-list command has been timeout, could you try again and login the seed vm then execute the command "nova --debug service-list --binary nova-compute" manually to see what happened? I guess it might be the proxy issue that blocks the keystone interaction, just make a check.

Hmm... weird.

    root@hLinux:~# nova --debug service-list --binary nova-compute
DEBUG (shell:792) You must provide a username or user id via --os-username, --os-user-id, env[OS_U          SERNAME] or env[OS_USER_ID]
Traceback (most recent call last):
  File "/opt/stack/python-novaclient/novaclient/shell.py", line 789, in main
    OpenStackComputeShell().main(argv)
  File "/opt/stack/python-novaclient/novaclient/shell.py", line 616, in main
    raise exc.CommandError(_("You must provide a username "
CommandError: You must provide a username or user id via --os-username, --os-user-id, env[OS_USERN          AME] or env[OS_USER_ID]
ERROR (CommandError): You must provide a username or user id via --os-username, --os-user-id, env[          OS_USERNAME] or env[OS_USER_ID]
root@hLinux:~#