XMLWordPrintable

      SNO Issue description Code Change Required Status Comment
      1 While generating charts, Getting NPEs when component spec does not contain auxiliary helm section and policy-info section. It should provide exceptions so that one can add these sections. Also, policy-info section should be optional and should not throw exception. Below is the list of things - need to determine required/optionallogDirectory
      certDirectory
      tlsServer - optional
      auxillary / helm section - Mandatory
      policy-info - optional
       Yes RESOLVED  Throws Error if Mandatory sections are not provided else it is success
      2 When I try to install the generated helm chart tgz file, below error happens in first tryError: unable to build kubernetes objects from release manifest: error validating "": error validating data: [ValidationError(Deployment.spec.template.spec.containers[0].readinessProbe.httpGet): missing required field "port" in io.k8s.api.core.v1.HTTPGetAction, ValidationError(Deployment.spec.template.spec.containers[0].readinessProbe.periodSeconds): invalid type for io.k8s.api.core.v1.Probe.periodSeconds: got "string", expected "integer", ValidationError(Deployment.spec.template.spec.containers[0].readinessProbe.timeoutSeconds): invalid type for io.k8s.api.core.v1.Probe.timeoutSeconds: got "string", expected "integer"]It does not like period seconds and timeoutsecond*s with 10s or 15s, it accepts integer 10 or 15. Also *health check port is required field (so need to populate port) - how do we check this ?  Yes  NEED TO TEST  To be verified by modifying spec schema changes
       3  After manually fixing, get an error. Error: rendered manifests contain a resource that already exists. Unable to continue with install: ConfigMap "dev-dcae-ves-collector-application-config-configmap" in namespace "onap" exists and cannot be imported into the current release: invalid ownership metadata; annotation validation error: key "meta.helm.sh/release-name" must equal "dev-dcae-ves-collector-new": current value is "dev-dcaegen2-services"   NO TESTED Resolved after fixing the environment
       4 applicationEnv section under auxillary/helm section should be optional YES TESTED Resolved
      5 NPE if use_external_tls is not provided in spec file.
      Also, external certificates should be populated based on use_external_tls flag (not use_tls flag)
      YES TESTED Resolved
      6 Policy Info Section needs to populated correctly in values.yaml YES  TESTED Resolved
      7 NPE if optional timeout and interval is not provided in specs. This got introduced when the code was updated for conversion from 15s to 15 YES TESTED Resolved
      8 postgres and secrets sections are generated in values,yaml even if the database section not defined in component spec YES TESTED Resolved
      9 Schema validator does not properly show the errors. Difficult to trace the error.  YES  OPEN  
      10 Following exception is thrown if spec schema is not provided as a parameter. But successfully generates helm chart without validation.
      java.io.FileNotFoundException: src\main\resources\specSchema.json (The system cannot find the path specified)
      YES TESTED  Resolved
      11 1.4.3 - error related to repositoryGenerator dependency
       
       java.io.FileNotFoundException: ./input/blueprint/base/charts/repositoryGenerator/values.yaml (No such file or directory)
              at java.base/java.io.FileInputStream.open0(Native Method)
       
      The specified file does not exist as the corresponding dependency was loaded as tar.gz file. After extracting the dependent tar.gz file though – the chart generation was successful. Need to check why application is looking for specific values.yaml.
      YES TESTED Resolved
       12  Sonar coverage reporting 0% due to missing property - need to include sonar.coverage.jacoco.xmlReportPaths (similar to here - https://git.onap.org/dcaegen2/platform/tree/mod/bpgenerator/pom.xml#n75)  YES CLOSED  
               
               

       
       

            mssivakumar01 mssivakumar01
            vv770d vv770d
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: