Skip to content

Conversation

@wking
Copy link
Member

@wking wking commented Oct 3, 2018

This restores the console docs which we'd removed from the README in feb41e9 (#328). And it moves the kubeconfig location information over from the libvirt-specific docs. Launching the cluster is nice, but these other operations are important too ;). Putting them in the README makes increases their visibility. It also lets us drom them from the libvirt-specific docs, now that the libvirt docs link to the README quick-start for these generic operations.

@openshift-ci-robot openshift-ci-robot added size/M Denotes a PR that changes 30-99 lines, ignoring generated files. approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Oct 3, 2018
Copy link
Contributor

Choose a reason for hiding this comment

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

openshift usually recommends oc

Copy link
Member Author

Choose a reason for hiding this comment

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

openshift usually recommends oc

Orthogonal change to existing code ;). File a follow-up PR?

This restores the console docs which we'd removed from the README in
feb41e9 (docs: rework documentation, 2018-09-24, openshift#328).  And it moves
the kubeconfig location information over from the libvirt-specific
docs.  Launching the cluster is nice, but these other operations are
important too ;).  Putting them in the README makes increases their
visibility.  It also lets us drom them from the libvirt-specific docs,
now that the libvirt docs link to the README quick-start for these
generic operations.
@wking wking force-pushed the readme-console-kubeconfig-and-cleanup branch from 219c70f to f9f5e8d Compare October 3, 2018 05:32
@crawford
Copy link
Contributor

crawford commented Oct 4, 2018

/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Oct 4, 2018
@openshift-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: crawford, wking

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@crawford
Copy link
Contributor

crawford commented Oct 4, 2018

CI failed with:

2018/10/04 18:47:35 Copying artifacts from release-latest into /logs/artifacts/release-latest
info: Using registry public hostname registry.svc.ci.openshift.org
info: Found 77 images in image stream
info: Manifests will be extracted to /tmp/release-image-2018-10-04T184720Z005979829
warning: Could not load current user information: user: unknown userid 1008470000
Unable to connect to the server: net/http: TLS handshake timeout

/retest

@wking
Copy link
Member Author

wking commented Oct 4, 2018

e2e:

error: could not run steps: failed to create or restart release pod: unable to delete completed pod: could not delete completed pod: Operation cannot be fulfilled on Pod "release-latest": the UID in the precondition (d20cabd9-c805-11e8-a9f5-42010a8e0004) does not match the UID in record (6732b4d0-c807-11e8-a9f5-42010a8e0004). The object might have been deleted and then recreated

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@wking
Copy link
Member Author

wking commented Oct 4, 2018

e2e:

warning: Could not load current user information: user: unknown userid 1009850000
Loading manifests from cluster-dns-operator: registry.svc.ci.openshift.org/ci-op-x91k706v/stable@sha256:9b5e32c412553763782db3e8e68e816445632da90b2a1bf3808e35c686151de7 ...
Loading manifests from cluster-image-registry-operator: registry.svc.ci.openshift.org/ci-op-x91k706v/stable@sha256:61b10a249a6efcf5ca2affd605365008115c1781fbd857b503f73d7091d23fd2 ...
Loading manifests from cluster-kube-controller-manager-operator: registry.svc.ci.openshift.org/ci-op-x91k706v/stable@sha256:8d335fade89abe158d47c0ae1fa7c5f329533f1a9de56aac918967778779f44d ...
Loading manifests from cluster-network-operator: registry.svc.ci.openshift.org/ci-op-x91k706v/stable@sha256:4fbe6b15627cba5f03190a35477f79ee964ae5b98c054b75315a57474ab3ef92 ...
Loading manifests from cluster-ingress-operator: registry.svc.ci.openshift.org/ci-op-x91k706v/stable@sha256:ff41c397787ec0111fe590052ef0d62182541357f12eb36723c1b60a7440f261 ...
Loading manifests from cluster-kube-scheduler-operator: registry.svc.ci.openshift.org/ci-op-x91k706v/stable@sha256:f9293bacbcb70d292fe2051944911b2132c011b156bce1bf408a4afb90cbc2c9 ...
error: unable to parse image registry.svc.ci.openshift.org/ci-op-x91k706v/stable@sha256:e0681ed61e35f4935013beef627e72fb6b6e2d58f30da21c4eb115a80e7793aa: cannot retrieve image configuration for manifest sha256:e0681ed61e35f4935013beef627e72fb6b6e2d58f30da21c4eb115a80e7793aa: Get https://storage.googleapis.com/openshift-ci-infra-origin-ci-registry-bucket/docker/registry/v2/blobs/sha256/36/364708c8fdb5b05977a881aa20a735c2fbc2f4744cc59b9ffe9e14d214255690/data?Expires=1538686756&GoogleAccessId=api-ci%40openshift-ci-infra.iam.gserviceaccount.com&Signature=j%2F7krUZnLtg2K4%2Bo4rnmbg%2BDKWHk6UoLcEd2v%2Frqkhy%2FDHpwmquPC9jBpnow77P5dHA3rF01%2BLx1ntZ3ctsl4S1wve7yeqc2OB92%2BGNtuT2EqeqMJyGdJuGzip2ATNVrP5exrj2OkYCKYxGqtFSEnPtrzri5KdGeD%2BAV0DGxLyrpsYrFYZtA5u2fwYFOSZpdIL4Bm1mGFq%2BRdmj%2FvXkuFEFKqa9zlNM87Tg9LCK26bwEXG1tyiBxVmuklMcR3kVLMcdDr0xvsRS86SLzaKLpD9%2FHo1B1BFZQJBFt3Hi%2FcN9i79ptrYVM1Ktq4JX4rZvlsAwzbQTyiMpZqMm4RTnK1A%3D%3D: EOF
2018/10/04 20:39:38 Container release in pod release-latest failed, exit code 1, reason Error
2018/10/04 20:39:44 Ran for 7m14s
error: could not run steps: failed to wait for release pod to complete: could not wait for pod completion: the pod ci-op-x91k706v/release-latest failed after 1m49s (failed containers: release):  unknown

Network hiccup?

/retest

@openshift-merge-robot openshift-merge-robot merged commit a6120f4 into openshift:master Oct 4, 2018
@wking wking deleted the readme-console-kubeconfig-and-cleanup branch October 4, 2018 22:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants