Update PCF release

Update to the latest release.

Currently this is 9.3.2

/cc @WarheadsSE @marin

changed the description

Documentation stated that I needed access to the gitlab-pivotal project in Google Cloud.

@WarheadsSE granted me access, but it might not actually be necessary, as @balasankarc was able to do a release without access.

The docker run command provided in the documentation specifies using -n as the option. My version of docker has no such option. It looks like the intention was for it to be --name.

I'm running

docker --version
Docker version 17.06.0-ce, build 02c1d87

Inside the container, running ci/package_release 9.3.2-ee.0 errors with

...
2017-06-30 14:12:26 (6.15 MB/s) - ‘gitlab-ee_9.3.2-ee.0_amd64.deb’ saved [389868536/389868536]

Adding a new GitLab blob...
mkdir /.bosh: permission denied

Exit code 1

Running export HOME=/tmp works around this.

Running bosh create-release --name $BOSH_RELEASE_NAME --force I get

Blob download 'debian_nfs_server/nfs-kernel-server_1.2.5-3ubuntu3_amd64.deb' (124 kB) (id: 39ba5231-ce15-4e77-47b4-fe8e7831ac3b sha1: 65457bbeda336dc4b710cd68
f71e9dd218fdf594) started
Blob download 'debian_nfs_server/nfs-kernel-server_1.2.5-3ubuntu3_amd64.deb' (id: 39ba5231-ce15-4e77-47b4-fe8e7831ac3b) finished
Blob download 'gitlab-ee-omnibus/gitlab-ee_9.1.7-ee.0_amd64.deb' (327 MB) (id: b7fb9667-3e1b-45b8-6b98-4841f535ad61 sha1: 4bff892d611f176eed24391c9d8a6a07b11c
9a5c) started

The gitlab-ee version doesn't match what I expect. Checking into this.

In re:HOME .. indeed. Perhaps we should add this to the ENV inside the container.

In re: EE version, I will check master on gitlab-ee-bosh-release

Indeed, 9.1.7 is that last release, as we are intended to be 1 release behind stable. You should be updating to the (current) end of the 9.2.x version which appears to be 9.2.7

I have started https://gitlab.com/gitlab-pivotal/gitlab-ee-bosh-release/merge_requests/27 for updates to the documentation on the bosh release.

• https://gitlab.com/gitlab-pivotal/gitlab-ee-bosh-release/#developing-against-gcp Should be cleaned up and put into a script.
• HOME needs added.
• We need some of entrypoint that will create the group and user for the uid:gid pair for us, knowing that on Linux, it defaults to 100x, and on Mac it defaults to 50x

Values in .env_example should be single quoted.

bundle install
Warning: the running version of Bundler (1.14.3) is older than the version that created the lockfile (1.14.5). We suggest you upgrade to the latest version of Bundler by running `gem install bundler`.

We'll need to full rebuild the container anyways, with ENV HOME=/tmp anyways .. so :)

Needed to use git config --global to configure git in order for spec:product to pass

Needed to update OLD_RELEASE_VERSION to 127 from 27. Change made in .env_example as well

Currently stuck with enabling lfs by default. Changes to gitlab.rb.erb are not showing up in the deployment.

I've run: bosh create-release --name $BOSH_RELEASE_NAME --force --tarball=foo and the created tarball contains the updated gitlab.rb.erb file with gitlab_rails['lfs_enabled'] = true. But, after running ci/bosh_deploy.sh $BOSH_DEPLOYMENT_NAME $BOSH_RELEASE_NAME, /etc/gitlab/gitlab.rb on the running vm still contains that line commented out.

Lets move on with the release and leave the lfs for another time. It is obvious that it needs a bit more work than we expected.

Following https://gitlab.com/gitlab-pivotal/p-gitlab-ee/blob/master/docs/overview.md, I'm moving on to https://gitlab.com/gitlab-pivotal/gitlab-ee-with-tile-gen

Error running wget in tile-gen container:

wget  https://s3-eu-west-1.amazonaws.com/gitlab-ee-bosh-release/releases/gitlab-ee/gitlab-ee-134.tgz
Connecting to s3-eu-west-1.amazonaws.com (52.218.17.4:443)
wget: can't execute 'ssl_helper': No such file or directory
wget: error getting response: Connection reset by peer

I fixed by installing openssl:

$ docker exec -it --user root tile-gen bash -o vi                                                                                          (130)
bash-4.3# apk update
fetch http://dl-cdn.alpinelinux.org/alpine/v3.5/main/x86_64/APKINDEX.tar.gz
fetch http://dl-cdn.alpinelinux.org/alpine/v3.5/community/x86_64/APKINDEX.tar.gz
v3.5.2-123-g1b30cfc350 [http://dl-cdn.alpinelinux.org/alpine/v3.5/main]
v3.5.2-123-g1b30cfc350 [http://dl-cdn.alpinelinux.org/alpine/v3.5/community]
OK: 7967 distinct packages available
bash-4.3# apk add openssl
(1/3) Installing libcrypto1.0 (1.0.2k-r0)
(2/3) Installing libssl1.0 (1.0.2k-r0)
(3/3) Installing openssl (1.0.2k-r0)
Executing busybox-1.25.1-r0.trigger
Executing ca-certificates-20161130-r1.trigger
OK: 104 MiB in 41 packages
bash-4.3# update-ca-certificates
WARNING: ca-certificates.crt does not contain exactly one certificate or CRL: skipping

For determining the release number, need to look at the merge request pipeline from the MR created in https://gitlab.com/gitlab-pivotal/gitlab-ee-bosh-release/blob/master/README.md step 16. The create_final_version in the pipeline that spawns will print a message like: Upload bosh release version 140, from master SHA:d2b36f2957eb27a64ba7d92b9346354cdb3aceb7.

I'll update the docs accordingly.

Wording in the step 4 sublist from https://gitlab.com/gitlab-pivotal/gitlab-ee-with-tile-gen#testing-tile is somewhat confusing. Password should be the one printed out by cf-info.

Should note that LDAP login should happen on the main tab, and root login should happen on the Standard tab on the login page.

Release should be complete. I believe I've updated the documentation with some of the issues I ran into. There should be separate issues for everything else.

Have you done the MR to the Pivotal's documentation?

https://github.com/pivotal-cf/docs-gitlab/pull/13

mentioned in issue gitlab-org/omnibus-gitlab#2568 (closed)

closed