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

Bug 1811834: Sync jsonnet dependencies #722

Merged
merged 5 commits into from Mar 30, 2020

Conversation

paulfantom
Copy link
Contributor

Multiple things in one PR (sorry):

Some other changes include ones described in prometheus-operator/kube-prometheus#470

Note: jsonnetfile.lock.json was updated in stages to check what is changing, but in the end it came down to running jb update on all.

/cc @openshift/openshift-team-monitoring

@openshift-ci-robot openshift-ci-robot requested a review from a team March 25, 2020 09:23
@openshift-ci-robot
Copy link
Contributor

@paulfantom: This pull request references Bugzilla bug 1811834, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target release (4.5.0) matches configured target release for branch (4.5.0)
  • bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)

In response to this:

Bug 1811834: Sync jsonnet dependencies

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.

@openshift-ci-robot openshift-ci-robot added bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Mar 25, 2020
@paulfantom paulfantom force-pushed the sync_deps branch 4 times, most recently from e0ea276 to 9923716 Compare March 25, 2020 11:48
@paulfantom
Copy link
Contributor Author

/hold
until prometheus/node_exporter#1649 is merged and propagated

@openshift-ci-robot openshift-ci-robot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Mar 25, 2020
@lilic
Copy link
Contributor

lilic commented Mar 25, 2020

Its been merged it seems.

@paulfantom
Copy link
Contributor Author

/unhold

prometheus/node_exporter#1649 is merged and propagated here.

@openshift-ci-robot openshift-ci-robot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Mar 26, 2020
@@ -9,8 +9,19 @@ metadata:
namespace: openshift-monitoring
spec:
endpoints:
- honorLabels: true
port: http
- bearerTokenFile: /var/run/secrets/kubernetes.io/serviceaccount/token
Copy link
Contributor

Choose a reason for hiding this comment

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

why do we have 2 endpoint entries?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Good catch! Fixing.

@paulfantom paulfantom force-pushed the sync_deps branch 2 times, most recently from 63c1fef to 78836ef Compare March 26, 2020 12:35
@paulfantom
Copy link
Contributor Author

/test generate

pkg/client/client.go Outdated Show resolved Hide resolved
@paulfantom paulfantom changed the title Bug 1811834: Sync jsonnet dependencies WIP: Bug 1811834: Sync jsonnet dependencies Mar 26, 2020
@openshift-ci-robot openshift-ci-robot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Mar 26, 2020
@paulfantom paulfantom force-pushed the sync_deps branch 2 times, most recently from e276c10 to ad4ef92 Compare March 26, 2020 13:55
@paulfantom
Copy link
Contributor Author

/retest

@lilic
Copy link
Contributor

lilic commented Mar 26, 2020

/retest

should be back now

@paulfantom
Copy link
Contributor Author

/retest

@paulfantom paulfantom changed the title WIP: Bug 1811834: Sync jsonnet dependencies Bug 1811834: Sync jsonnet dependencies Mar 27, 2020
@openshift-ci-robot openshift-ci-robot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Mar 27, 2020
@paulfantom
Copy link
Contributor Author

Rebased to solve merge conflicts

Copy link
Contributor

@lilic lilic left a comment

Choose a reason for hiding this comment

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

Couple of questions, otherwise looks good

is configured on this host.
summary: Clock not synchronising.
expr: |
min_over_time(node_timex_sync_status[5m]) == 0
Copy link
Contributor

Choose a reason for hiding this comment

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

We don't need the job label selector here, like we had for ClockSkewDetected?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

That metric comes only from node_exporter which is deployed as DaemonSet, so I don't see why we would need it.

@@ -87,3 +87,15 @@ rules:
- get
- list
- watch
- apiGroups:
Copy link
Contributor

Choose a reason for hiding this comment

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

Do we know why this was added for prometheus-operator in kube-prom, can't seem to find it in the prometheus-operator repo itself? https://github.com/coreos/prometheus-operator/blob/master/example/rbac/prometheus-operator/prometheus-operator-cluster-role.yaml should this be updated there?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Without those kube-rbac-proxy didn't work and metrics couldn't be scraped.

Copy link
Contributor

Choose a reason for hiding this comment

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

okay that explains that, thanks!

}
}
return errors.Wrap(err, "updating deployment object failed")
return errors.Wrap(err, "updating Deployment object failed")
Copy link
Contributor

Choose a reason for hiding this comment

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

Thanks :)

Copy link
Contributor

Choose a reason for hiding this comment

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

Follow up task to us, maybe tech-debt, unrelated to this PR: we should include the name of these objects in the logs. WDYT?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

good idea, could you create JIRA?

Copy link
Contributor

Choose a reason for hiding this comment

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

@lilic
Copy link
Contributor

lilic commented Mar 27, 2020

aws fails with 🤔:

fail [github.com/openshift/origin/test/extended/prometheus/prometheus.go:231]: possibly some services didn't register ServiceMonitors to allow metrics collection
Unexpected error:
<*errors.errorString | 0xc00028d1d0>: {
s: "timed out waiting for the condition",
}
timed out waiting for the condition
occurred

@paulfantom
Copy link
Contributor Author

argh, yes. We are checking if prometheus-operator is available over http and not https -.-

Source: https://github.com/openshift/origin/blob/master/test/extended/prometheus/prometheus.go#L222

@paulfantom
Copy link
Contributor Author

/retest

Copy link
Contributor

@lilic lilic left a comment

Choose a reason for hiding this comment

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

/lgtm

/hold

In case simon wants to review as well.

@openshift-ci-robot openshift-ci-robot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Mar 30, 2020
@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Mar 30, 2020
@simonpasquier
Copy link
Contributor

/lgtm

/hold cancel

@openshift-ci-robot openshift-ci-robot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Mar 30, 2020
@openshift-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: lilic, paulfantom, simonpasquier

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:
  • OWNERS [lilic,paulfantom,simonpasquier]

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

@openshift-merge-robot openshift-merge-robot merged commit e61d233 into openshift:master Mar 30, 2020
@openshift-ci-robot
Copy link
Contributor

@paulfantom: All pull requests linked via external trackers have merged: openshift/cluster-monitoring-operator#722. Bugzilla bug 1811834 has been moved to the MODIFIED state.

In response to this:

Bug 1811834: Sync jsonnet dependencies

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.

@sferich888
Copy link

/cherry-pick release-4.4
/cherry-pick release-4.3
/cherry-pick release-3.11

@openshift-cherrypick-robot

@sferich888: #722 failed to apply on top of branch "release-4.4":

error: Failed to merge in the changes.
Using index info to reconstruct a base tree...
M	jsonnet/jsonnetfile.lock.json
Falling back to patching base and 3-way merge...
Auto-merging jsonnet/jsonnetfile.lock.json
CONFLICT (content): Merge conflict in jsonnet/jsonnetfile.lock.json
Patch failed at 0001 jsonnet: update dependencies

In response to this:

/cherry-pick release-4.4
/cherry-pick release-4.3
/cherry-pick release-3.11

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.

@lilic
Copy link
Contributor

lilic commented Jun 16, 2020

@sferich888 that won't work as the lock file needs to be generated for each release branch, what are you trying to do backport? :)

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. bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

7 participants