[Starlingx-discuss] [ Test ] Sanity results - summary posted

Penney, Don Don.Penney at windriver.com
Wed Sep 12 14:04:35 UTC 2018


I'm not familiar with the "update-network-installer" script. I assume it's an Intel creation? We hand-manage updates to the installer images, with steps described in stx-metal/installer/initrd/README, updating the images only as needed.

The kickstarts provide "repo" directives to Anaconda to point it at the repos under /www/ on the controller, with the base load being in /www/pages/feed/rel-XXXX. Anaconda should be able to install everything from there.

-----Original Message-----
From: Cordoba Malibran, Erich [mailto:erich.cordoba.malibran at intel.com] 
Sent: Tuesday, September 11, 2018 9:51 PM
To: Alonso, Juan Carlos; Young, Ken
Cc: starlingx-discuss at lists.starlingx.io
Subject: Re: [Starlingx-discuss] [ Test ] Sanity results - summary posted

I have narrowed down a little bit the issue, these are my findings.

  - I compared the bootimage_michel.iso with the stx-2018-09-11-111.iso, which is today's ISO.
  - The are not significant package differences between them, minor versions has changed in some packages.
  - The issue is that once the kernel has been loaded through PXE, anaconda is unable to find python2-qpid package. Not sure if this is
the first package that is requested.
  - From the anaconda shell I can see the http://pxecontroller/ serving the files and the repodata seems to be updated there. I installed yum
manually and I was able to install python2-qpid package, (and any other available).
  - The content of the pxe-network-installer package is not the same, WR squashfs.img file has the kernel 3.10.0-693.2.2 but ours has 3.10.0-
862.6.3. We regenerate those files when the kernel was upgraded. (maybe this matches with the date where the issue started to arise..)

So, my guess now is that the problem could be caused by the pxe-network-installer package. We create those files with the update-
network-installer script. That's the same used in WR to generate these files?

I'll keep diging in the generation of these files to see if there is any problem.

-Erich

On 9/11/18, 3:34 PM, "Alonso, Juan Carlos" <juan.carlos.alonso at intel.com> wrote:

    Hi Ken,
    
    Because the issues started from August's ISOs and followed ISOs have the same issues.
    We focused to find from what ISO the issues started, we did it. Now we are focusing on confirm if such package is the root cause of issues, if it is then latest ISOs should work well.
    
    Regards.
    Juan Carlos Alonso
    
    -----Original Message-----
    From: Young, Ken [mailto:Ken.Young at windriver.com] 
    Sent: Tuesday, September 11, 2018 3:19 PM
    To: Alonso, Juan Carlos <juan.carlos.alonso at intel.com>
    Cc: Thebeau, Michel <Michel.Thebeau at windriver.com>; Khalil, Ghada <Ghada.Khalil at windriver.com>; Martinez Monroy, Elio <elio.martinez.monroy at intel.com>; Jones, Bruce E <bruce.e.jones at intel.com>; Cabrales, Ada <ada.cabrales at intel.com>; starlingx-discuss at lists.starlingx.io
    Subject: Re: [Starlingx-discuss] [ Test ] Sanity results - summary posted
    
    Juan Carlos,
    
    I am confused.  Why are we looking at the behaviour of ISOs from August?  That seems like a waste of time.  If I look at the sanity page, ISOs have been produced since then:
    
    https://wiki.openstack.org/wiki/StarlingX/Test#Latest_ISO_image_Sanity_Summary
    
    The latest used there is Sept 6th?  I believe that Mitch's ISO is more recent than that; I would have to check.
    
    Is there a reason we are not discussing the September 10th build?  Does it display the same installer error on the console of controller-1?  Certainly, we have not seen that virtually or physically on any system.
    
    Regards,
    Ken Y
    
    On 2018-09-11, 4:07 PM, "Alonso, Juan Carlos" <juan.carlos.alonso at intel.com> wrote:
    
        Hi,
        
        I also posted a comment on 1790213 with some findings.
        About the ISO sharing, I don't know if we are still able to continue with it.
        
        The installation fail on compute nodes have the same behavior.
        
        Regards.
        Juan Carlos Alonso
        
        -----Original Message-----
        From: Michel Thebeau [mailto:michel.thebeau at windriver.com] 
        Sent: Tuesday, September 11, 2018 2:09 PM
        To: Khalil, Ghada <Ghada.Khalil at windriver.com>; Alonso, Juan Carlos <juan.carlos.alonso at intel.com>; Martinez Monroy, Elio <elio.martinez.monroy at intel.com>; Jones, Bruce E <bruce.e.jones at intel.com>; Cabrales, Ada <ada.cabrales at intel.com>; starlingx-discuss at lists.starlingx.io
        Subject: Re: [ Test ] Sanity results - summary posted
        
        Hi Ghada,
        
        I have posted a comment on #1790716 recommending closing that bug, but referring everyone to #1790213.
        
        I have not yet received the iso named stx-2018-08-30-97, but the iso
        stx-2018-08-28-88 presented a broken installer on the controller-1 console:
        
        " Error populating transaction after 10 retries: failure: 
        Packages/python2-qpid-proton-0.24.0-1.el7.x86_64.rpm from anaconda: 
        [Errno 256] No more mirrors to try."
        
        I think one could refocus on finding out why the installer broke after 2018-08-25-81, before 2018-08-28-88
        
        M
        
        
        On 2018-09-11 09:53 AM, Khalil, Ghada wrote:
        > Hello Juan,
        > I read the notes in the Launchpad.
        >
        > And, just to confirm, are you following the instructions under:  
        > https://wiki.openstack.org/wiki/StarlingX/Installation_Guide_Virtual_E
        > nvironment/Controller_Storage and still reproducing the two issues 
        > below?
        >
        > I was not able to definitively tell from the Launchpad notes. It's important that both our teams are comparing apples to apples.
        >
        > Thanks,
        > Ghada
        >
        > -----Original Message-----
        > From: Alonso, Juan Carlos [mailto:juan.carlos.alonso at intel.com]
        > Sent: Monday, September 10, 2018 1:50 PM
        > To: Khalil, Ghada; Martinez Monroy, Elio; Jones, Bruce E; Cabrales, 
        > Ada; starlingx-discuss at lists.starlingx.io; Thebeau, Michel
        > Subject: RE: [ Test ] Sanity results - summary posted
        >
        > Hi,
        >
        > Such launchpads were updated.
        >
        > A VM was set to upload the ISO tx-2018-08-28-88.iso, such ISO present two issues. Michael will upload his ISO, then we will re test witch each iso in our environment.
        >
        > An script is being developed to get the differences between ISOs.
        >
        > Regards.
        > Juan Carlos Alonso
        >
        > -----Original Message-----
        > From: Khalil, Ghada [mailto:Ghada.Khalil at windriver.com]
        > Sent: Friday, September 7, 2018 4:43 PM
        > To: Khalil, Ghada <Ghada.Khalil at windriver.com>; Martinez Monroy, Elio 
        > <elio.martinez.monroy at intel.com>; Jones, Bruce E 
        > <bruce.e.jones at intel.com>; Cabrales, Ada <ada.cabrales at intel.com>; 
        > starlingx-discuss at lists.starlingx.io; Thebeau, Michel 
        > <Michel.Thebeau at windriver.com>
        > Subject: Re: [Starlingx-discuss] [ Test ] Sanity results - summary 
        > posted
        >
        > Hi Elio/Ada,
        > Are there any updates from your side on these two Launchpads?
        > https://bugs.launchpad.net/starlingx/+bug/1790213
        > https://bugs.launchpad.net/starlingx/+bug/1790716
        >
        > Michel Thebeau (Wind River) has been trying to reproduce these two issues (following the starlingx wikis) without success for two days now. He has been adding his findings to the bugs and communicating with your team.
        > As a result of his investigation, he will be pushing some small fixes to stx-tools shortly (some cleanup).
        >
        > Please let us know if you need any further help from us.
        >
        > Thanks,
        > Ghada
        >
        > -----Original Message-----
        > From: Khalil, Ghada [mailto:Ghada.Khalil at windriver.com]
        > Sent: Wednesday, September 05, 2018 5:39 PM
        > To: Martinez Monroy, Elio; Jones, Bruce E; Cabrales, Ada; 
        > starlingx-discuss at lists.starlingx.io
        > Subject: Re: [Starlingx-discuss] [ Test ] Sanity results - summary 
        > posted
        >
        > Please see inline. There are notes in all the launchpads as well.
        >
        > I have tagged the last bug for the October release. The rest need more information to determine whether they gate or not: two maybe procedural and one requires more information.
        >
        > -----Original Message-----
        > From: Martinez Monroy, Elio [mailto:elio.martinez.monroy at intel.com]
        > Sent: Wednesday, September 05, 2018 2:23 PM
        > To: Jones, Bruce E; Cabrales, Ada; 
        > starlingx-discuss at lists.starlingx.io
        > Subject: Re: [Starlingx-discuss] [ Test ] Sanity results - summary 
        > posted
        >
        > My opinion below
        >
        > -----Original Message-----
        > From: Jones, Bruce E [mailto:bruce.e.jones at intel.com]
        > Sent: Wednesday, September 5, 2018 12:56 PM
        > To: Cabrales, Ada <ada.cabrales at intel.com>; 
        > starlingx-discuss at lists.starlingx.io
        > Subject: Re: [Starlingx-discuss] [ Test ] Sanity results - summary 
        > posted
        >
        > Should the bugs coming out of this be tagged/fixed for the October release?
        >
        > Related bugs:
        > https://bugs.launchpad.net/starlingx/+bug/1790213 < --- Must, this bug is related with 2nd controller provisioning [[GK]] Using the instructions published on the wiki, our designer was not able to reproduce this issue. What instructions are the test team using?
        >
        > https://bugs.launchpad.net/starlingx/+bug/1790514 < --- Can wait until other issues are solved, will fail some test cases related to SSH [[GK]] Requested more information. This cannot be debugged further without this information.
        >
        > https://bugs.launchpad.net/starlingx/+bug/1790716 < --- Must, all 
        > instances need at least one compute for multimode [[GK]] Using the 
        > instructions published on the wiki, our designer was not able to 
        > reproduce this issue. The test team points to internal instructions 
        > which we have no access to. The supported install recipes need to be 
        > on the wiki. I think it is an invalid bug
        >
        > https://bugs.launchpad.net/starlingx/+bug/1790718 < --- Can wait since is related to FM , test cases will fail [[GK]] As Brent pointed out, this is dependent on the integration of stx-gui which is in progress.
        >
        > -----Original Message-----
        > From: Cabrales, Ada [mailto:ada.cabrales at intel.com]
        > Sent: Wednesday, September 5, 2018 10:50 AM
        > To: starlingx-discuss at lists.starlingx.io
        > Subject: [Starlingx-discuss] [ Test ] Sanity results - summary posted
        >
        > Hello all,
        >
        >      As mentioned on the project meeting today, we're posting the summary of the sanity test runs on the Test wiki [0]. The sanity is triggered each time an ISO is generated (a daily task).
        >
        >     Right now we are posting the results manually, and working on a way for automating it. Logs of the run are not included, if you want to have them, you can contact Elio to get them sent to you.
        >
        >
        > [0] 
        > https://wiki.openstack.org/wiki/StarlingX/Test#Latest_ISO_image_Sanity
        > _Summary
        >
        > Regards
        > Ada
        >
        > _______________________________________________
        > Starlingx-discuss mailing list
        > Starlingx-discuss at lists.starlingx.io
        > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
        > _______________________________________________
        > Starlingx-discuss mailing list
        > Starlingx-discuss at lists.starlingx.io
        > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
        > _______________________________________________
        > Starlingx-discuss mailing list
        > Starlingx-discuss at lists.starlingx.io
        > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
        > _______________________________________________
        > Starlingx-discuss mailing list
        > Starlingx-discuss at lists.starlingx.io
        > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
        > _______________________________________________
        > Starlingx-discuss mailing list
        > Starlingx-discuss at lists.starlingx.io
        > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
        
        
        _______________________________________________
        Starlingx-discuss mailing list
        Starlingx-discuss at lists.starlingx.io
        http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
        
    
    _______________________________________________
    Starlingx-discuss mailing list
    Starlingx-discuss at lists.starlingx.io
    http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
    

_______________________________________________
Starlingx-discuss mailing list
Starlingx-discuss at lists.starlingx.io
http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss


More information about the Starlingx-discuss mailing list