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

Dropping label for origin releasepayload #496

Merged

Conversation

abhinavdahiya
Copy link
Contributor

The olm manifests are blocking ClusterVersionOperator intergration in
openshift/installer.

xref: openshift/installer#330 (comment)
cc @smarterclayton

The olm manifests are blocking ClusterVersionOperator intergration in
openshift/installer. One example of error is:
```yaml
oc -n openshift-operator-lifecycle-manager describe pods package-server-6495dfd49b-zc55f
Name:               package-server-6495dfd49b-zc55f
Namespace:          openshift-operator-lifecycle-manager
Priority:           0
PriorityClassName:  <none>
Node:               ip-10-0-137-91.ec2.internal/10.0.137.91
Start Time:         Mon, 01 Oct 2018 18:19:41 -0700
Labels:             app=package-server
                    pod-template-hash=2051898056
Annotations:        openshift.io/scc=anyuid
Status:             Pending
IP:                 10.2.4.8
Controlled By:      ReplicaSet/package-server-6495dfd49b
Containers:
  package-server:
    Container ID:
    Image:         registry.svc.ci.openshift.org/openshift/origin-v4.0-20181001234718@sha256:52f6d50f38ea0ebe93af48c968c4a646fbbf171eb4309c4f7b410ebed82888f6
    Image ID:
    Port:          443/TCP
    Host Port:     0/TCP
    Command:
      /bin/package-server
      -v=4
      --debug
    State:          Waiting
      Reason:       CreateContainerError
    Ready:          False
    Restart Count:  0
    Liveness:       http-get https://:443/healthz delay=0s timeout=1s period=10s #success=1 #failure=3
    Readiness:      http-get https://:443/healthz delay=0s timeout=1s period=10s #success=1 #failure=3
    Environment:    <none>
    Mounts:
      /apiserver.local.config/certificates from certs (ro)
      /var/run/secrets/kubernetes.io/serviceaccount from olm-operator-serviceaccount-token-rkqbj (ro)
Conditions:
  Type              Status
  Initialized       True
  Ready             False
  ContainersReady   False
  PodScheduled      True
Volumes:
  certs:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  package-server-certs
    Optional:    false
  olm-operator-serviceaccount-token-rkqbj:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  olm-operator-serviceaccount-token-rkqbj
    Optional:    false
QoS Class:       BestEffort
Node-Selectors:  <none>
Tolerations:     <none>
Events:
  Type     Reason                  Age                 From                                  Message
  ----     ------                  ----                ----                                  -------
  Normal   Pulled                  24m (x7 over 26m)   kubelet, ip-10-0-137-91.ec2.internal  Successfully pulled image "registry.svc.ci.openshift.org/openshift/origin-v4.0-20181001234718@sha256:52f6d50f38ea0ebe93af48c968c4a646fbbf171eb4309c4f7b410ebed82888f6"
  Warning  Failed                  24m (x7 over 26m)   kubelet, ip-10-0-137-91.ec2.internal  Error: container create failed: container_linux.go:336: starting container process caused "exec: \"/bin/package-server\": stat /bin/package-server: no such file or directory"
  Normal   Pulling                 3m (x99 over 27m)   kubelet, ip-10-0-137-91.ec2.internal  pulling image "registry.svc.ci.openshift.org/openshift/origin-v4.0-20181001234718@sha256:52f6d50f38ea0ebe93af48c968c4a646fbbf171eb4309c4f7b410ebed82888f6"
```
@openshift-ci-robot openshift-ci-robot added size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Oct 2, 2018
@smarterclayton
Copy link
Collaborator

/ok-to-test

@openshift-ci-robot openshift-ci-robot removed the needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. label Oct 2, 2018
@smarterclayton
Copy link
Collaborator

@ecordell can we temporarily disable to unblock?

@smarterclayton smarterclayton added 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. labels Oct 2, 2018
@openshift-ci-robot
Copy link
Collaborator

[APPROVALNOTIFIER] This PR is APPROVED

Approval requirements bypassed by manually added approval.

This pull-request has been approved by:

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

The pull request process is described here

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

@smarterclayton
Copy link
Collaborator

Tagging, we should be able to reenable soon

@openshift-merge-robot openshift-merge-robot merged commit 17dca6e into operator-framework:master Oct 2, 2018
@abhinavdahiya abhinavdahiya deleted the remove_label branch October 2, 2018 13:48
ecordell pushed a commit to ecordell/operator-lifecycle-manager that referenced this pull request Mar 8, 2019
…abel

Dropping label for origin releasepayload
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/XS Denotes a PR that changes 0-9 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants