Skip to content

Commit 302bdda

Browse files
dustymabeopenshift-merge-robot
authored andcommitted
mantle: bump timeout for aws console
The m5.large instance types seem to consistently take longer for their console logs to get updated.
1 parent e3a815e commit 302bdda

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

mantle/platform/machine/aws/machine.go

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -106,22 +106,22 @@ func (am *machine) saveConsole(origConsole string) error {
106106
// returned output will be non-empty but won't necessarily include
107107
// the most recent log messages. So we loop until the post-termination
108108
// logs are different from the pre-termination logs.
109-
err := util.WaitUntilReady(5*time.Minute, 5*time.Second, func() (bool, error) {
109+
err := util.WaitUntilReady(10*time.Minute, 10*time.Second, func() (bool, error) {
110110
var err error
111111
am.console, err = am.cluster.flight.api.GetConsoleOutput(am.ID())
112112
if err != nil {
113113
return false, err
114114
}
115115

116116
if am.console == origConsole {
117-
plog.Debugf("waiting for console for %v", am.ID())
117+
plog.Debugf("waiting for post-terminate console for %v", am.ID())
118118
return false, nil
119119
}
120120

121121
return true, nil
122122
})
123123
if err != nil {
124-
err = fmt.Errorf("retrieving console output of %v: %v", am.ID(), err)
124+
err = fmt.Errorf("retrieving post-terminate console output of %v: %v", am.ID(), err)
125125
if origConsole != "" {
126126
plog.Warning(err)
127127
} else {

0 commit comments

Comments
 (0)