Skip to content

change the operator pods' checking#3884

Closed
jianzhangbjz wants to merge 1 commit intooperator-framework:masterfrom
jianzhangbjz:OSDK-1308
Closed

change the operator pods' checking#3884
jianzhangbjz wants to merge 1 commit intooperator-framework:masterfrom
jianzhangbjz:OSDK-1308

Conversation

@jianzhangbjz
Copy link
Copy Markdown
Contributor

Description of the change:
Adress some issues in the merged PR 3819

Motivation for the change:

  • Succeeded means the Pod finished and exited. For the operator pods, they should be running all the time to monitor the CRs, so, the expected status should be Running, not Succeeded.

  • Sometimes, there are multi containers in a Pod. Should add the container name to distinguish them.

Checklist

If the pull request includes user-facing changes, extra documentation is required:

@jianzhangbjz
Copy link
Copy Markdown
Contributor Author

@bharathi-tenneti @jmrodri @estroz Could you help review it? Thanks!

@jianzhangbjz
Copy link
Copy Markdown
Contributor Author

/assign @bharathi-tenneti

@jianzhangbjz
Copy link
Copy Markdown
Contributor Author

/retest

@openshift-ci-robot
Copy link
Copy Markdown

@jianzhangbjz: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

Details

In response to this:

/retest

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 kubernetes/test-infra repository.

@jmrodri
Copy link
Copy Markdown
Member

jmrodri commented Sep 16, 2020

/ok-to-test

@openshift-ci-robot openshift-ci-robot added the ok-to-test Indicates a non-member PR verified by an org member that is safe to test. label Sep 16, 2020
@bharathi-tenneti
Copy link
Copy Markdown
Contributor

@jianzhangbjz Good catch, You can go ahead an remove the comments.

@openshift-ci-robot openshift-ci-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Sep 17, 2020
@jianzhangbjz
Copy link
Copy Markdown
Contributor Author

Fix the below error:

- /target/docs/contribution-guidelines/testing/travis-build/index.html
  *  External link https://github.com/operator-framework/operator-sdk/blob/master/test/e2e/e2e_suite_test.go failed: 404 No error

@openshift-ci-robot openshift-ci-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Sep 17, 2020
@jianzhangbjz
Copy link
Copy Markdown
Contributor Author

@bharathi-tenneti Thanks! Removed the comments.

@jianzhangbjz
Copy link
Copy Markdown
Contributor Author

@jmrodri @bharathi-tenneti Could you help add the /lgtm label to merge it? Thanks!

@jianzhangbjz
Copy link
Copy Markdown
Contributor Author

@jmrodri @varshaprasad96 Could you help approve it? Thanks!

Comment thread internal/olm/client/client.go Outdated
@jianzhangbjz
Copy link
Copy Markdown
Contributor Author

@joelanford Thanks for your suggestions! I added it. Could you help have a review again? Thanks!

@jianzhangbjz jianzhangbjz force-pushed the OSDK-1308 branch 2 times, most recently from 589e8cf to b73ce55 Compare September 18, 2020 08:33
@jianzhangbjz
Copy link
Copy Markdown
Contributor Author

/retest

@bharathi-tenneti
Copy link
Copy Markdown
Contributor

@jianzhangbjz just FYI, this code is being refactored. #3908
May be, you can review that PR, and see if it covers your changes.

Copy link
Copy Markdown
Contributor

@camilamacedo86 camilamacedo86 left a comment

Choose a reason for hiding this comment

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

the change shows fine.
/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Sep 18, 2020
@jianzhangbjz
Copy link
Copy Markdown
Contributor Author

Thanks! How to address this failure?

    TASK [Fetch the kubeconfig] ****************************************************
fatal: [kind-test-local]: FAILED! => {"changed": false, "file": "/root/.kube/config", "msg": "unable to calculate the checksum of the remote file"}
    
    PLAY RECAP *********************************************************************
    kind-test-local            : ok=0    changed=0    unreachable=0    failed=1    skipped=0    rescued=0    ignored=0
    
ERROR: 

image

@jianzhangbjz
Copy link
Copy Markdown
Contributor Author

/retest

@jianzhangbjz
Copy link
Copy Markdown
Contributor Author

@rafaelvanoni @bharathi-tenneti Could you help look at it? Thanks!

Copy link
Copy Markdown
Member

@estroz estroz left a comment

Choose a reason for hiding this comment

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

/lgtm

@estroz
Copy link
Copy Markdown
Member

estroz commented Sep 29, 2020

@jianzhangbjz can you rebase this with master? There was a CI change that isn't being picked up here.

@camilamacedo86
Copy link
Copy Markdown
Contributor

camilamacedo86 commented Oct 30, 2020

Hi @jianzhangbjz,

By checking how the master is now, shows that it is already solved. Could you please check? If yes, we can close this one. If not, could you please rebase with the master and add the new changelog fragment in changelog/fragments (see changelog/fragments/00-template.yaml) for we are able to get it merged?

@bharathi-tenneti bharathi-tenneti removed their assignment Oct 30, 2020
@camilamacedo86 camilamacedo86 added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Oct 30, 2020
@openshift-ci-robot
Copy link
Copy Markdown

New changes are detected. LGTM label has been removed.

@openshift-ci-robot openshift-ci-robot removed lgtm Indicates that a PR is ready to be merged. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. labels Jan 20, 2021
@jianzhangbjz
Copy link
Copy Markdown
Contributor Author

Hi @camilamacedo86, I'm so sorry for the late reply. I forgot it to update it. The new logic looks good to me. But, I combine an if logic there, could you have a review? Thanks!

@openshift-bot
Copy link
Copy Markdown

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci-robot openshift-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 20, 2021
@openshift-bot
Copy link
Copy Markdown

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

@openshift-ci openshift-ci Bot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels May 20, 2021
@openshift-bot
Copy link
Copy Markdown

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

@openshift-ci openshift-ci Bot closed this Jun 26, 2021
@openshift-ci
Copy link
Copy Markdown

openshift-ci Bot commented Jun 26, 2021

@openshift-bot: Closed this PR.

Details

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/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 kubernetes/test-infra repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. ok-to-test Indicates a non-member PR verified by an org member that is safe to test.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

9 participants