Details

    • Customer:
      Zain KSA 3.X

      Description

      Click to add description

      Issue Links

        Activity

        Hide
        Indrasan Yadav added a comment -

        Dear @Khaled Khalil,

        Could you please assign a DEV resource to investigate and resolve the issue described below?

        I validated the data in NEP on platform .14 after the XML (2024-12-05-08.21.07_ZainKsa) was imported. During the validation, I found the following issue related to the licenses data, which were not imported into NEP:

        1. The licenses are available in the XML, as shown in the snippet below for reference.

        2. When I reviewed the error report, I did not find any errors related to this issue. However, I observed a warning message under the "Category Validation Failed" section concerning config and usage. Please note that these config and usage details are not required in this case, as they are not present in the XML.

        3. Similar issue was also faced in Huawei case which was fixed by @Diana Hamdouche.

        Best regards,
        Indrasan

        Show
        Indrasan Yadav added a comment - Dear @Khaled Khalil, Could you please assign a DEV resource to investigate and resolve the issue described below? I validated the data in NEP on platform .14 after the XML (2024-12-05-08.21.07_ZainKsa) was imported. During the validation, I found the following issue related to the licenses data, which were not imported into NEP: 1. The licenses are available in the XML, as shown in the snippet below for reference. 2. When I reviewed the error report, I did not find any errors related to this issue. However, I observed a warning message under the "Category Validation Failed" section concerning config and usage. Please note that these config and usage details are not required in this case, as they are not present in the XML. 3. Similar issue was also faced in Huawei case which was fixed by @Diana Hamdouche. Best regards, Indrasan
        Hide
        Mustapha Al-Hage added a comment -

        Dear @Indrasan Yadav,

        After reviewing the database, error reports, and implemented logic, we identified the following:

        1. Upon checking the database, I found that the NE licenses were imported into NEP on 7-DEC-2024, which is the date this XML was imported. Additionally, the number of NE licenses imported is 51,588

        2. As per the logic implemented, the warnings you are getting in the error report “License: XYZ is not imported due to: Config. has invalid value It must be a number” and “License: XYZ is not imported due to: Usage. has invalid value It must be a number” do not prevent the import of NE Licenses.

        However, these warnings are misleading. Therefore, we have updated the warning to “License XYZ: Config has invalid value, It must be a number”.

        Patch is needed for the warnings update: 3.7.1.635

        In conclusion, the NE licenses were successfully imported into NEP, and the warnings in the error report do not stop the import process.

        Regards,
        Mustapha Al Hage

        Show
        Mustapha Al-Hage added a comment - Dear @Indrasan Yadav, After reviewing the database, error reports, and implemented logic, we identified the following: 1. Upon checking the database, I found that the NE licenses were imported into NEP on 7-DEC-2024, which is the date this XML was imported. Additionally, the number of NE licenses imported is 51,588 2. As per the logic implemented, the warnings you are getting in the error report “License: XYZ is not imported due to: Config. has invalid value It must be a number” and “License: XYZ is not imported due to: Usage. has invalid value It must be a number” do not prevent the import of NE Licenses. However, these warnings are misleading. Therefore, we have updated the warning to “License XYZ: Config has invalid value, It must be a number”. Patch is needed for the warnings update: 3.7.1.635 In conclusion, the NE licenses were successfully imported into NEP, and the warnings in the error report do not stop the import process. Regards, Mustapha Al Hage
        Hide
        Indrasan Yadav added a comment -

        Okay, currently Huawei_RAN XML import is ongoing.

        Once done we will request to @Integration to apply the mentioned patch on .14 then will start import the Nokia XML and see the result.

        Show
        Indrasan Yadav added a comment - Okay, currently Huawei_RAN XML import is ongoing. Once done we will request to @Integration to apply the mentioned patch on .14 then will start import the Nokia XML and see the result.
        Hide
        Indrasan Yadav added a comment -

        Dear @ABHINAV PARASHAR,

        As discussed, please deploy the patch 3.7.1.635 on .14.

        Best regards,
        Indrasan

        Show
        Indrasan Yadav added a comment - Dear @ABHINAV PARASHAR, As discussed, please deploy the patch 3.7.1.635 on .14. Best regards, Indrasan
        Hide
        Indrasan Yadav added a comment -

        Patch has been deploy on .14 & Nokia XML import started on .14, once complete I will validate the data.

        Show
        Indrasan Yadav added a comment - Patch has been deploy on .14 & Nokia XML import started on .14, once complete I will validate the data.
        Hide
        Indrasan Yadav added a comment -

        Now, all LIC are imported in NEP as available in XML.

        Show
        Indrasan Yadav added a comment - Now, all LIC are imported in NEP as available in XML.
        Hide
        Indrasan Yadav added a comment -

        We are now closing this child JIRA as it pertains to an individual issue.

        As suggested by @Ahad, all code commit JIRAs will be covered under the parent JIRA.

        Show
        Indrasan Yadav added a comment - We are now closing this child JIRA as it pertains to an individual issue. As suggested by @Ahad, all code commit JIRAs will be covered under the parent JIRA.

          People

          • Assignee:
            Indrasan Yadav
            Reporter:
            Indrasan Yadav
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Due:
              Created:
              Updated:
              Planned Start:
              Planned End:
              Actual Start:
              Date of Baselining:

              Time Tracking

              Estimated:
              Original Estimate - Not Specified
              Not Specified
              Remaining:
              Remaining Estimate - 0 minutes
              0m
              Logged:
              Time Spent - 2 days, 4 hours
              2d 4h

                Drag and Drop