Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Changed directory of slave image to /tmp #11041

Merged
merged 1 commit into from
Sep 26, 2016
Merged

Changed directory of slave image to /tmp #11041

merged 1 commit into from
Sep 26, 2016

Conversation

oatmealraisin
Copy link

Fixes #10914

@bparees @mfojtik ptal?

@bparees
Copy link
Contributor

bparees commented Sep 21, 2016

does the master-slave readme need to be updated also, to indicate the need to instantiate the sample template? i seem to recall you ran into issues with missing that step.

@bparees bparees self-assigned this Sep 21, 2016
@mfojtik
Copy link
Contributor

mfojtik commented Sep 21, 2016

@oatmealraisin @bparees did you find the root cause for why we need to do this? it used to work :-)

@bparees
Copy link
Contributor

bparees commented Sep 21, 2016

@mfojtik i'm satisfied to assume something about some permissions changed in the image or the uid the slave is getting launched as.

@mfojtik
Copy link
Contributor

mfojtik commented Sep 21, 2016

@bparees @oatmealraisin can we at least use /tmp/workspace or something similar?

@oatmealraisin
Copy link
Author

I'm working on the README, testing my changes now

@mfojtik @bparees Whatever you all think is best for the directory. I'll also test /tmp/workspace

@bparees
Copy link
Contributor

bparees commented Sep 21, 2016

@mfojtik any particular reason you think it matters? we're specifying the image, we know /tmp is safe to use.

@mfojtik
Copy link
Contributor

mfojtik commented Sep 21, 2016

@bparees during the build the /tmp might be used for temporary artifacts.. i would feel safe if we can isolate the workdir ;-)

@bparees
Copy link
Contributor

bparees commented Sep 21, 2016

@mfojtik i'm pretty sure jenkins creates a subdir anyway for the workspace.

but if @oatmealraisin finds that "/tmp/workspace" works, we can update it to that.

@oatmealraisin
Copy link
Author

@mfojtik @bparees I've changed the tutorial but left it as /tmp. Jenkins automatically creates a workspace directory, and the app breaks with the additional /tmp/workspace. Jenkins breaks trying to mkdir /tmp/workspace/workspace/jenkins

Copy link
Contributor

@bparees bparees left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

one minor issue w/ the instructions and then lgtm.

```
```
# Ruby application template
$ oc new-app https://raw.githubusercontent.com/openshift/origin/master/examples/jenkins/application-template.json
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this is installing/instantiating a template which is different from installing a template (as the other 2 commands do), so i think this needs to be broken out as a separate step so it's not under "install the provided templates"

@oatmealraisin
Copy link
Author

@bparees Made oc new-app its own step, ptal?

@bparees
Copy link
Contributor

bparees commented Sep 22, 2016

@oatmealraisin squash and lgtm.

Added step to Master->Slave tutorial

This directs the user to create the ruby application template, which is
critical to the success of the tutorial.

Also fixed a bug with ordered list
@oatmealraisin
Copy link
Author

@bparees squashed, merge?

@bparees
Copy link
Contributor

bparees commented Sep 22, 2016

[merge]

@openshift-bot
Copy link
Contributor

[Test]ing while waiting on the merge queue

@oatmealraisin
Copy link
Author

[test]

@oatmealraisin
Copy link
Author

oatmealraisin commented Sep 23, 2016

Flake #11074 , [test]

@oatmealraisin
Copy link
Author

Flake #11079, [test]

@bparees
Copy link
Contributor

bparees commented Sep 24, 2016

[merge]

Ben Parees | OpenShift

On Sep 24, 2016 04:32, "OpenShift Bot" notifications@github.com wrote:

continuous-integration/openshift-jenkins/merge FAILURE (
https://ci.openshift.redhat.com/jenkins/job/test_pr_origin/9237/)


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#11041 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEvl3g9CBXolr6P36aCvFqqAyG9pYfPdks5qtIvEgaJpZM4KC4iH
.

@bparees
Copy link
Contributor

bparees commented Sep 24, 2016

[merge]

Ben Parees | OpenShift

On Sep 24, 2016 07:37, "OpenShift Bot" notifications@github.com wrote:

continuous-integration/openshift-jenkins/merge FAILURE (
https://ci.openshift.redhat.com/jenkins/job/test_pr_origin/9241/)


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#11041 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEvl3gNFtbO72jtxmIJCE1YeIFdIMgGoks5qtLcegaJpZM4KC4iH
.

@oatmealraisin
Copy link
Author

@bparees Any idea how I could be causing this failure? I keep getting the same one.

@bparees
Copy link
Contributor

bparees commented Sep 24, 2016

@oatmealraisin the deployments flake is a known flake #11016

The flake here is more concerning but still not due to your changes that i can see:
https://ci.openshift.redhat.com/jenkins/job/test_pull_requests_origin_integration/6320/console

@stevekuznetsov did compilation memory requirements go up again? not sure why everyone wouldn't be seeing this:

++ Building go targets for linux/amd64: cmd/openshift cmd/oc
# github.com/openshift/origin/cmd/openshift
/usr/local/go/pkg/tool/linux_amd64/link: running gcc failed: fork/exec /usr/bin/gcc: cannot allocate memory
[ERROR] PID 7: hack/common.sh:244: `local -a binaries=("$@")` exited with status 1.
[INFO]      Stack Trace: 
[INFO]        1: hack/common.sh:244: `local -a binaries=("$@")`
[INFO]        2: hack/build-cross.sh:20: os::build::build_binaries
[INFO]   Exiting with code 1.
make: *** [build-cross] Error 1

[test]

@bparees
Copy link
Contributor

bparees commented Sep 25, 2016

flake #11016
[test]

memory error seems to have gone away this run, so that's a flake too.

On Sat, Sep 24, 2016 at 7:22 PM, OpenShift Bot notifications@github.com
wrote:

continuous-integration/openshift-jenkins/test FAILURE (
https://ci.openshift.redhat.com/jenkins/job/test_pr_origin/9251/)


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#11041 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEvl3j4R-AdD6jNbuVcBgbcnKYwyI_ltks5qtbC4gaJpZM4KC4iH
.

Ben Parees | OpenShift

@oatmealraisin
Copy link
Author

Flake #11016, [test]

@oatmealraisin
Copy link
Author

@bparees Thanks :) was really scratching my head with this one

@openshift-bot
Copy link
Contributor

Evaluated for origin test up to a1f3537

@openshift-bot
Copy link
Contributor

continuous-integration/openshift-jenkins/test SUCCESS (https://ci.openshift.redhat.com/jenkins/job/test_pr_origin/9265/)

@bparees
Copy link
Contributor

bparees commented Sep 26, 2016

[merge]

@stevekuznetsov
Copy link
Contributor

@bparees yeah, they're slowly creeping up still after the rebase.

@openshift-bot
Copy link
Contributor

openshift-bot commented Sep 26, 2016

continuous-integration/openshift-jenkins/merge SUCCESS (https://ci.openshift.redhat.com/jenkins/job/test_pr_origin/9265/) (Image: devenv-rhel7_5076)

@bparees
Copy link
Contributor

bparees commented Sep 26, 2016

#10162
[merge]

@openshift-bot
Copy link
Contributor

Evaluated for origin merge up to a1f3537

@openshift-bot openshift-bot merged commit 46146b0 into openshift:master Sep 26, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants