Landscape Client

landscape-is-cloud-managed shouldn't take 30 seconds to time out on a non-EC2 machine

Bug #354558 reported by Christopher Armstrong
2
Affects Status Importance Assigned to Milestone
Landscape Client
Fix Released
Low
Christopher Armstrong
Landscape Client 1.0.30
Landscape Server
Fix Released
Low
Christopher Armstrong
Landscape Server mountainview

Bug Description

bug #350499 introduced the landscape-is-cloud-managed script which runs on startup if CLOUD=1. If CLOUD=1 and we're not actually on an EC2 instance then it takes a really long time to start. The timeout should be lowered.

Christopher Armstrong (radix)
tags: added: review
Revision history for this message
Thomas Herve (therve) wrote :

Great, +1.

Thomas Herve (therve)
Changed in landscape:
assignee: nobody → radix
importance: Undecided → Low
milestone: none → mountainview
status: New → In Progress
Changed in landscape-client:
assignee: nobody → radix
importance: Undecided → Low
milestone: none → 1.0.30
status: New → In Progress
Revision history for this message
Free Ekanayaka (free.ekanayaka) wrote :

Looks perfect thanks! +1

Revision history for this message
Christopher Armstrong (radix) wrote :

Merged to trunk.

tags: removed: review
Changed in landscape-client:
status: In Progress → Fix Committed
Changed in landscape:
status: In Progress → Fix Committed
Andreas Hasenack (ahasenack)
Changed in landscape-client:
status: Fix Committed → Fix Released
Changed in landscape:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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