Bug Report
What did you do?
When running operator-sdk run bundle and specifying an index image via the --index-image flag the command will stall when attempting to generate the extra FBC here:
|
|
|
reg, err := containerdregistry.NewRegistry( |
|
containerdregistry.WithLog(fbcutil.NullLogger()), |
|
containerdregistry.SkipTLSVerify(skipTLSVerify), |
|
containerdregistry.WithPlainHTTP(useHTTP)) |
|
|
|
if err != nil { |
|
return nil, fmt.Errorf("error creating new image registry: %v", err) |
|
} |
The same thing occurs when running operator-sdk run bundle-upgrade and it attempts to render the refs for generating an upgraded FBC here:
|
reg, err := containerdregistry.NewRegistry( |
|
containerdregistry.WithLog(NullLogger()), |
|
containerdregistry.SkipTLSVerify(skipTLSVerify), |
|
containerdregistry.WithPlainHTTP(useHTTP)) |
|
|
|
if err != nil { |
|
return nil, fmt.Errorf("error creating new image registry: %v", err) |
|
} |
The stalling seems to happen due to a file lock not being able to be established and no timeout being specified.
What did you expect to see?
operator-sdk run bundle(-upgrade) commands either fail with a timeout error or succeed and the bundle is installed properly.
What did you see instead? Under which circumstances?
operator-sdk run bundle(-upgrade) commands stall and hang forever
Environment
Operator type:
Kubernetes cluster type:
KinD
$ operator-sdk version
$ go version (if language is Go)
$ kubectl version
Possible Solution
Add a timeout and make the directory used by the containerdregistry being created be unique. The registry should also be properly torn down with the Destroy() function.
Additional context
Bug Report
What did you do?
When running
operator-sdk run bundleand specifying an index image via the--index-imageflag the command will stall when attempting to generate the extra FBC here:operator-sdk/internal/olm/operator/bundle/install.go
Lines 195 to 203 in 79afd93
The same thing occurs when running
operator-sdk run bundle-upgradeand it attempts to render the refs for generating an upgraded FBC here:operator-sdk/internal/olm/fbcutil/util.go
Lines 136 to 143 in 79afd93
The stalling seems to happen due to a file lock not being able to be established and no timeout being specified.
What did you expect to see?
operator-sdk run bundle(-upgrade)commands either fail with a timeout error or succeed and the bundle is installed properly.What did you see instead? Under which circumstances?
operator-sdk run bundle(-upgrade)commands stall and hang foreverEnvironment
Operator type:
Kubernetes cluster type:
KinD
$ operator-sdk version$ go version(if language is Go)$ kubectl versionPossible Solution
Add a timeout and make the directory used by the containerdregistry being created be unique. The registry should also be properly torn down with the
Destroy()function.Additional context