Preview activities failing intermittantly

[tdcox]

Summary

I created a preview build with the intention of testing the changes I made to the setup for post preview jobs but I am instead hitting an unexpected error deriving from a part of the code that I didn't touch...

Updating PipelineActivities bootstrap-labs-test292-pr-1-1 which has status Running
error: error checking if preview application http://test292.jx-bootstrap-labs-test292-pr-1.kill-9.uk is available: Get http://test292.jx-bootstrap-labs-test292-pr-1.kill-9.uk: dial tcp: lookup test292.jx-bootstrap-labs-test292-pr-1.kill-9.uk on 10.31.240.10:53: no such host

This is the correct URL and the service is visible on that URL from outside the platform but it killed the build.

Restarting the build results in a successful deployment second time around.

Can someone confirm whether this code will have been executing in an environment that was recently moved to Alpine as part of #4481 activities, please?

I ask because this looks very much like the symptoms of the intermittant DNS resolution failure problem that we have had with Alpine in the past.

Jx version

The output of jx version is:

NAME               VERSION
jx                 2.0.450
Kubernetes cluster v1.12.8-gke.10
kubectl            v1.14.2
helm client        Client: v2.14.0+g05811b8
git                git version 2.21.0
Operating System   Mac OS X 10.13.6 build 17G6030

Jenkins type

• Serverless Jenkins X Pipelines (Tekton + Prow)
• Classic Jenkins

[hferentschik]

@tdcox, afaik we have not come out of the discussion phase regarding moving to a smaller base image.

[okgolove]

Having the same problem.

[jenkins-x-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://jenkins-x.io/community.
/lifecycle stale

[jenkins-x-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
Provide feedback via https://jenkins-x.io/community.
/lifecycle rotten

[jenkins-x-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Provide feedback via https://jenkins-x.io/community.
/close

[jenkins-x-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Provide feedback via https://jenkins-x.io/community.
/close

[jenkins-x-bot]

@jenkins-x-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Provide feedback via https://jenkins-x.io/community.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository.