-
Notifications
You must be signed in to change notification settings - Fork 23
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 2247737: add APIs to scheme, role and role binding to bundle #38
Conversation
leelavg
commented
Nov 2, 2023
•
edited
Loading
edited
- Add missing ClusterVersion and ClusterServiceVersion APIs to status reporter Scheme
- Add missing Role and RoleBinding to Kustomize and generate CSV Bundle
- ClusterVersion and ClusterServiceVersion APIs addition to scheme is missing in status reporter job Signed-off-by: Leela Venkaiah G <[email protected]>
- Status reporter role and role binding is missing in generated CSV bundle Signed-off-by: Leela Venkaiah G <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
changes LGTM, please let me know once testing is done
LGTM |
@leelavg: This pull request references Bugzilla bug 2247737, 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. 2 validation(s) were run on this bug
Requesting review from QA contact: In response to this:
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[bot]: GitHub didn't allow me to request PR reviews from the following users: nehaberry. Note that only red-hat-storage members and repo collaborators can review this PR, and authors cannot review their own PRs. In response to this:
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. |
Without fix:
With fix: $ cat storageclient-29011.yaml
apiVersion: batch/v1
kind: CronJob
metadata:
name: storageclient-29011-status-reporter
namespace: openshift-storage-client
spec:
concurrencyPolicy: Allow
failedJobsHistoryLimit: 1
jobTemplate:
metadata:
creationTimestamp: null
spec:
template:
metadata:
creationTimestamp: null
spec:
containers:
- command:
- /status-reporter
env:
- name: STORAGE_CLIENT_NAMESPACE
value: openshift-storage-client
- name: STORAGE_CLIENT_NAME
value: storageclient
- name: OPERATOR_NAMESPACE
value: openshift-storage-client
image: quay.io/rhn_support_lgangava/code:29011
imagePullPolicy: IfNotPresent
name: heartbeat
serviceAccount: ocs-client-operator-status-reporter
serviceAccountName: ocs-client-operator-status-reporter
terminationGracePeriodSeconds: 30
restartPolicy: OnFailure
schedule: '* * * * *'
successfulJobsHistoryLimit: 3
suspend: false
---
apiVersion: rbac.authorization.k8s.io/v1
kind: Role
metadata:
creationTimestamp: null
name: ocs-client-operator-status-reporter
namespace: openshift-storage-client
rules:
- apiGroups:
- operators.coreos.com
resources:
- clusterserviceversions
verbs:
- get
- list
- watch
---
kind: RoleBinding
apiVersion: rbac.authorization.k8s.io/v1
metadata:
name: ocs-client-operator-status-reporter
namespace: openshift-storage-client
roleRef:
apiGroup: rbac.authorization.k8s.io
kind: Role
name: ocs-client-operator-status-reporter
subjects:
- kind: ServiceAccount
name: ocs-client-operator-status-reporter
namespace: openshift-storage-client
---
$ k get storageconsumer storageconsumer-f4aec37d-d6de-4ea2-9d4c-4210170a4f92 -oyaml | yq 'del(.metadata.annotations)'
apiVersion: ocs.openshift.io/v1alpha1
kind: StorageConsumer
metadata:
creationTimestamp: "2023-10-29T03:49:30Z"
generation: 2
name: storageconsumer-f4aec37d-d6de-4ea2-9d4c-4210170a4f92
namespace: openshift-storage
resourceVersion: "21003071"
uid: 1cbb0e37-301b-427f-9b96-2161e4d48236
spec:
enable: true
status:
cephResources:
- kind: CephClient
name: 126102a1ddafcaa8045be5cfb98746c0
status: Ready
client:
operatorVersion: 4.14.0-160.hci
platformVersion: 4.14.0-rc.7
lastHeartbeat: "2023-11-03T05:41:24Z"
state: Ready |
@leelavg As we have multiple problems, Are we going to have a different PR for the above problem? |
|
/lgtm |
@Madhu-1 if above testing isn't enough for the vote, I tested deploying via OLM
|
/approved |
/approve |
1 similar comment
/approve |
/approve |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED Approval requirements bypassed by manually added approval. This pull-request has been approved by: leelavg, Madhu-1, nb-ohad 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 |
/tide refresh |
@leelavg: All pull requests linked via external trackers have merged: Bugzilla bug 2247737 has been moved to the MODIFIED state. In response to this:
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. |