Open cnocula-i opened 3 years ago
Hi @cnocula-i , Can you please share which image of operator are you using ?
This issue will be addressed in v1.1.0.
I was using the Red Hat OpenShift GitOps v1.0.0 operator from Marketplace on OpenShift 4.6.17_1533.
I was using the Red Hat OpenShift GitOps v1.0.0 operator from Marketplace on OpenShift 4.6.17_1533.
This issue will be addressed in v1.1.0.
Is there some kind of roadmap available to see, when the next releases are coming up?
@cnocula-i As mentioned by @wtam2018 this should be part of 1.1.0 which is planned to release next week.
we migrated from community operator to RH's operator and we would like to avoid rolling back. any chance for this bug to be fixed this week @iam-veeramalla ?
we migrated from community operator to RH's operator and we would like to avoid rolling back. any chance for this bug to be fixed this week @iam-veeramalla ?
@aelbarkani release is planned for today . This issue should be fixed
v1.1 has been released which fixed this issue.
@wtam2018 where can I find the new version ? it doesn't seem to be released in Operator Hub in Openshift (we have paying distribution, not OKD). Also, there seems to be no commit to this github repo nor a tag for the new release...
Currently, it is only available to OCP 4.7+.
On Fri, Apr 16, 2021 at 9:23 AM Anas EL BARKANI @.***> wrote:
@wtam2018 https://github.com/wtam2018 where can I find the new version ? it doesn't seem to be released in Operator Hub in Openshift (we have paying distribution, not OKD). Also, there seems to be no commit to this github repo nor a tag for the new release...
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/redhat-developer/gitops-operator/issues/99#issuecomment-821172770, or unsubscribe https://github.com/notifications/unsubscribe-auth/AKQAJII5JONMDXADSU4TPDDTJA25BANCNFSM4Z7NGTTA .
@aelbarkani you must be on OCP 4.6. We will backport the fix to 4.6.
@wtam2018 yes we are using 4.6
@wtam2018 any updates on the backport ?
Hi @aelbarkani , we haven't decided on a backport to 4.6, yet. Supporting a GA product on a newer version of OpenShift is a significant commitment and we'd like to make a well-thought out decision on that.
May I ask, which features/scenarios you are looking for, from the newer release of GA ?
@aelbarkani Sorry. My bad. As @sbose78 said, we haven't decided to backport to 4.6 as it was a Tech Preview release on 4.6.
@sbose78 well we just need the argocd image to be fixed, so no new features needed, just a bug fix. Also, we cannot upgrade to Openshift 4.7 since all upgrades from OpenShift 4.6 seems to be disabled (Redhat support confirmed that, and there is a bugzilla opened). So unfortunately I think we are blocked at this moment: no possibility to rollback to community version, Redhat version broken, and upgrades to OpenShift 4.7 broken. So adding the tar to the image for OCP 4.6 would be of great help for us :)
Redhat support confirmed that, and there is a bugzilla opened
Would you have the support case / bugzilla number handy? :)
FWIW, the operator can create a new Argo CD instance with a specific argocd image. See the image field iin the "Create Argo CD" UI.
@sbose78 : case 02913271 @wtam2018 : ok thanks, will test that workaround
Describe the bug Applications with Helm charts defined in a chart repository fail to be deployed.
To Reproduce Steps to reproduce the behavior:
Expected behavior Chart is downloaded as a "tgz" file and processed correctly.
Screenshots If applicable, add screenshots to help explain your problem.
Additional context Add any other context about the problem here.