1 2 Previous Next 17 Replies Latest reply on Jan 4, 2016 10:26 AM by Bill Robinson

    Exit code error

    Anushansa Gupta

      Hi All,

       

      I am running a patch deployment job on a RHEL6 target server and I am getting below error in the "Commit" state, however "Stage & Simulate" are completed successfully after patch analysis.

       

      bldeploy logs for the same are:

      12/06/15 20:44:05.605 DEBUG    bldeploy -  TDR***** 4029 -1/-1 (Not_available): (Not_available):   CPU Before = 81

      12/06/15 20:44:05.605 DEBUG    bldeploy -  TDR***** 4029 -1/-1 (Not_available): (Not_available):   CPU After = 0

      12/06/15 20:44:05.605 DEBUG    bldeploy -  TDR***** 4029 -1/-1 (Not_available): (Not_available):   Process Group ID = 4029

      12/06/15 20:44:05.605 INFO     bldeploy -  TDR***** 4029 -1/-1 (Not_available): (Not_available): Got processes list: 1 entries

      12/06/15 20:44:05.606 INFO     bldeploy - Bldeploy done - nRet = 7 (Apply failed; auto-rollback failed) exitCode = -4001 (Deployment failed)

       

      **Hostname changed because of security reasons**

       

      Please help on this.

        • 1. Re: Exit code error
          Jim Wilson

          There will be other messages of relevance in the log - please attach the whole thing (use the Advanced Editor to get the Attach option)

          • 2. Re: Exit code error
            Anushansa Gupta

            Hi Jim,

             

            PFA the complete deploy logs file.

             

            Please check and update.

             

            Thanks in advance.

            • 3. Re: Exit code error
              Jim Wilson

              The underlying reason the deploy failed:

              12/06/15 20:43:01.353 INFO bldeploy - [2][New RPM Group] [stdout: 2]    Running yum from /var/tmp/stage/61e85a7c138430629231644f8ceae152 and yum used is blyum...
              12/06/15 20:44:02.993 WARN bldeploy - [2][New RPM Group] [stderr: 2]  

              Error Downloading Packages:

                rp-pppoe-3.10-11.el6.x86_64: Caching enabled but no local cache of //var/tmp/stage/61e85a7c138430629231644f8ceae152/blrepos/repo/packages/rp-pppoe-3.10-11.el6.x86_64.rpm from repo

              12/06/15 20:44:03.040 INFO bldeploy - [2][New RPM Group] [stdout: 2]    yum deploy failed.

               

              If you cannot determine the solution form this information, and no-one else can contribute on the communities, you should open a  support case

              • 4. Re: Exit code error
                Santosh Kothuru

                you may need to enable the keepcache=1 option in the /etc/yum.conf configuration file on target server to avoid the caching errors and try to execute job.

                • 5. Re: Exit code error
                  Bill Robinson

                  please explain how will adding the keepcache=1 help ?

                   

                   

                  what version of bsa is this ?  this is likely related to a defect w/ the include list handing where rpms are included in the include list and yum commands but the corresponding payload is not present in the catalog or not added to the deploy package from bsa during remediation.

                  • 6. Re: Exit code error
                    Santosh Kothuru

                    yum updates the header files and always download the headers, even if we are installing the package multiple times. To avoid redundancy, we can enable header and package file caching. To do so, we need to enable the keepcache=1 option in the /etc/yum.conf configuration file and then call yum with the -C  option, yum will access the cache regardless of the /etc/yum.conf settings. Of course, this will only work if you really do have the required resources in the cache. If resources are missing, yum will give you the message Caching enabled but no local cache type of errors.

                    • 7. Re: Exit code error
                      Bill Robinson

                      when using yum via bsa, is any of what you said true ?

                      • 8. Re: Exit code error
                        Santosh Kothuru

                        that's not about BSA. its all about target server.

                        • 9. Re: Exit code error
                          Rohit Sharma

                          The customer is using BSA 86 SP1 build 66.

                           

                          Also, can we check if the RPM "rp-pppoe-3.10-11.el6.x86_64" is present in the catalog and is not a part of irrelevant patches.

                           

                          We have seen issues in the past where some patches are removed to irrelevant patches after filters were modified on an existing catalog.

                           

                          We can also have a look at a filters that are used while creating the catalog and also verify if a change was made recently or not

                          • 10. Re: Exit code error
                            Bill Robinson

                            why is it not about bsa?  this is a deploy job, generated by bsa, from a redhat patching job right ?

                            • 11. Re: Exit code error
                              Santosh Kothuru

                              correct. But if the keepcache=0 is set on target server and the same job will fail on target server as well when they run manually. That's why we need to enable keepcache=1 to avoid the cache errors.

                              • 12. Re: Exit code error
                                Bill Robinson

                                you clearly have no idea how bsa works.

                                 

                                during the deploy job that's based on patching results the following happens:

                                - a copy of the repo (patch catalog) metadata is copied over to the target

                                - a custom yum.conf file is generated that points to the copy of the repo metadata

                                - the rpm payloads identified as missing by the analysis job are copied to the target

                                - if an include list was used during the analysis that is generated for the deploy

                                - blyum is called (which is bsa's version of yum) using the generated yum.conf - using the -C (cache) option since there is not actually a yum repo available via http/nfs/ftp/etc - and any include list is passed.

                                 

                                so using the 'keepcache' will do nothing here because we are already using the cache.  the problem here is that one or more packages are mentioned in the include list but they are not present on the target.

                                 

                                typically this happens because the rpm file is present on the repo file system and include in the repo metadata but flagged as irrelevant in the catalog or was removed from the catalog.  there are a couple defects that cause this - one is related to the deploy include list not being pruned properly (to only include the latest version of the rpm in the include list) and another is due to the filter options causing the rpm to be tagged as irrelevant incorrectly.  there may be a couple other causes.

                                • 13. Re: Exit code error
                                  Jim Wilson

                                  Bill Robinson wrote:

                                   

                                  there are a couple defects that cause this - one is related to the deploy include list not being pruned properly (to only include the latest version of the rpm in the include list) and another is due to the filter options causing the rpm to be tagged as irrelevant incorrectly.  there may be a couple other causes.

                                   

                                  From the attached log:

                                   

                                  12/06/15 20:43:01.313 INFObldeploy - [2][New RPM Group] [stdout: 2]    Using Includes List =

                                   

                                  So, the includes list issue can be eliminated

                                  • 14. Re: Exit code error
                                    Bill Robinson

                                    yeah - so expanding on what rohit said - rp-pppoe-3.10-11.el6.x86_64 is part of this errata: https://access.redhat.com/errata/RHEA-2014:0424

                                     

                                    this is an 'enhancement'.  if you look at the catalog filter options and 'enhancement' is not checked that will likely be the root of the problem.  you should also look to see if rp-pppoe-3.10-11.el6.x86_64 shows up in the RPMs or Irrelevant Patches smart groups. 

                                    1 2 Previous Next