Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-34717

The s2i build strategy is not assumed for Serverless Functions

XMLWordPrintable

    • Low
    • No
    • ODC Sprint 3257
    • 1
    • Rejected
    • False
    • Hide

      None

      Show
      None
    • Hide
      * Previously, the Source-to-Image (S2I) build strategy needed to be explicitly mentioned in the `func.yaml` in order to create serverless function. Additionally, the error message did not indicate the problem. With this release, if S2I is not mentioned users can still create the function. However, if it is not S2I, users cannot create the function. Additionally, the error messages have been updated to provide more information. (link:https://issues.redhat.com/browse/OCPBUGS-34717[*OCPBUGS-34717*])
      ____
      Cause: s2i build strategy needed to be explicitly mentioned in the func.yml in order to be able to create serverless function with the repo. Also the error messages if s2i is not mentioned or if func.yml is not there in the repo, were common.
      Consequence: Caused issues among users to identify the reason of failures
      Fix: Updated the logic regarding s2i, so that if its not mentioned, still users can create function, but if its not s2i, users cannot create. Also the error messages are different for both the cases now.
      Result: Bug doesn't present anymore.
      Show
      * Previously, the Source-to-Image (S2I) build strategy needed to be explicitly mentioned in the `func.yaml` in order to create serverless function. Additionally, the error message did not indicate the problem. With this release, if S2I is not mentioned users can still create the function. However, if it is not S2I, users cannot create the function. Additionally, the error messages have been updated to provide more information. (link: https://issues.redhat.com/browse/OCPBUGS-34717 [* OCPBUGS-34717 *]) ____ Cause: s2i build strategy needed to be explicitly mentioned in the func.yml in order to be able to create serverless function with the repo. Also the error messages if s2i is not mentioned or if func.yml is not there in the repo, were common. Consequence: Caused issues among users to identify the reason of failures Fix: Updated the logic regarding s2i, so that if its not mentioned, still users can create function, but if its not s2i, users cannot create. Also the error messages are different for both the cases now. Result: Bug doesn't present anymore.
    • Bug Fix
    • In Progress

      This is a clone of issue OCPBUGS-33733. The following is the description of the original issue:
      —
      Description of problem:

          When creating a Serverless Function via Web Console from GIT repository the validation claims that builder strategy is not s2i. However if the build strategy is not set in func.yaml, then the s2i should be assumed implicitly. There should be no error.

There should be error only if the strategy is explicitly set to something other than s2i in func.yaml.

      Version-Release number of selected component (if applicable):

      How reproducible:

      Steps to Reproduce:

          1. Try to create Serverless function from git repository where func.yaml does not explicitly specify builder.
    2. The Serverless Function cannot be created because of the validation.

      Actual results:

          The Function cannot be created.

      Expected results:

          The function can be created.

      Additional info:

       

            avik6028 Avik Kundu
            openshift-crt-jira-prow OpenShift Prow Bot
            Sanket Pathak Sanket Pathak
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: