US 12,067,387 B2
Software modification error resolution and management
Kumaravel Palanisamy, Bangalore (IN); Nida Taranum, Bangalore (IN); and Yogesh Balgi, Honavar (IN)
Assigned to Dell Products, L.P., Hopkinton, MA (US)
Filed by Dell Products, L.P., Hopkinton, MA (US)
Filed on Jan. 10, 2023, as Appl. No. 18/152,194.
Prior Publication US 2024/0231991 A1, Jul. 11, 2024
Int. Cl. G06F 8/65 (2018.01); G06F 11/07 (2006.01)
CPC G06F 8/65 (2013.01) [G06F 11/0787 (2013.01); G06F 11/0793 (2013.01); G06F 11/0712 (2013.01)] 18 Claims
OG exemplary drawing
 
1. A method of implementing a software modification process by a software update manager, comprising:
initiating the software modification process of a software package by the software update manager, the software update manager executing a software update script defining the software modification process to be implemented on the software package;
determining occurrence of an error during the software modification process by an error detection and log collection system;
in response to determining the occurrence of the error, collecting logs associated with the software modification process and the software package by the error detection and log collection system;
transmitting the error and logs from the error detection and log collection system to the software update manager;
in response to receipt of the error, starting an instance of an error resolution system;
providing the error to the error resolution system;
parsing the error by the error resolution system to generate a knowledge base article database inquiry;
using the knowledge base article database inquiry to obtain a set of knowledge base articles from a knowledge base article database;
determining a reliance value for each of the set of knowledge base articles; and
comparing respective reliance values with a reliance threshold value;
in response to a determination that the reliance value of a first knowledge base article of the set of knowledge base articles exceeds the reliance threshold value, identifying a workaround based on the first knowledge base article and applying the workaround to the software modification process on the software package; and
in response to a determination that no knowledge base article in the set of knowledge base articles has a respective reliance value in excess of the reliance threshold value, automatically generating an error correction request in a software bug tracking system.