[Starlingx-discuss] Sanity TC code or output

Wed Aug 12 15:45:15 UTC 2020

Hi Pratik,
I've checked the digests for the tags: rc-3.0-centos-stable-20191212T162958Z.0 (from the versioned helm-chart) and rc-3.0-centos-stable-latest (form the latest helm-chart).
It seems the images have different digests. As far as I know, the digest should be the same. 
@Sun, Austin - let me know if we need to fill in a bug for this.

Regards,
Nicolae Jascanu, Ph.D.
TSD Software Engineer

Internet Of Things Group
Galati, Romania

-----Original Message-----
From: Pratik M. <pvmpublic at gmail.com> 
Sent: Monday, August 10, 2020 11:40
To: Jascanu, Nicolae <nicolae.jascanu at intel.com>; Webster, Steven <Steven.Webster at windriver.com>
Cc: Sun, Austin <austin.sun at intel.com>; starlingx-discuss at lists.starlingx.io
Subject: Re: [Starlingx-discuss] Sanity TC code or output

Hi,
Thank you for the help. I used stable-latest based on the documentation here:
https://docs.starlingx.io/deploy_install_guides/r3_release/openstack/install.html#install-application-manifest-and-helm-charts

I will try w/ stable-versioned and let you know. Should I open a documentation bug?

I am not sure I still understand the reason why R3.0 OpenStack install worked earlier, but fails now. Can the tags move after a release? So the stable-latest OpenStack is from upstream's perspective (so no StarlingX sanity check)? Just trying to understand.

[sysadmin at controller-0 ~(keystone_admin)]$ grep 'registry\.local'
/opt/platform/armada/19.12/stx-openstack/1.0-19-centos-stable-latest/stx-openstack-stx-openstack.yaml
| grep neutron
        neutron_bagpipe_bgp:
registry.local:9001/docker.io/starlingx/stx-neutron:rc-3.0-centos-stable-latest
        neutron_db_sync:
registry.local:9001/docker.io/starlingx/stx-neutron:rc-3.0-centos-stable-latest
        neutron_dhcp:
registry.local:9001/docker.io/starlingx/stx-neutron:rc-3.0-centos-stable-latest
        neutron_l2gw:
registry.local:9001/docker.io/starlingx/stx-neutron:rc-3.0-centos-stable-latest
        neutron_l3:
registry.local:9001/docker.io/starlingx/stx-neutron:rc-3.0-centos-stable-latest
        neutron_linuxbridge_agent:
registry.local:9001/docker.io/starlingx/stx-neutron:rc-3.0-centos-stable-latest
        neutron_metadata:
registry.local:9001/docker.io/starlingx/stx-neutron:rc-3.0-centos-stable-latest
        neutron_openvswitch_agent:
registry.local:9001/docker.io/starlingx/stx-neutron:rc-3.0-centos-stable-latest
        neutron_server:
registry.local:9001/docker.io/starlingx/stx-neutron:rc-3.0-centos-stable-latest
        neutron_sriov_agent:
registry.local:9001/docker.io/starlingx/stx-neutron:rc-3.0-centos-stable-latest
        neutron_sriov_agent_init:
registry.local:9001/docker.io/starlingx/stx-neutron:rc-3.0-centos-stable-latest

Thanks in advance
Pratik

On Sat, Aug 8, 2020 at 1:03 PM Jascanu, Nicolae <nicolae.jascanu at intel.com> wrote:
>
> Hi Pratik,
> We installed the 3.0.0 image using the versioned helm-charts at: 
> http://mirror.starlingx.cengn.ca/mirror/starlingx/release/3.0.0/centos
> /outputs/helm-charts/stx-openstack-1.0-19-centos-stable-versioned.tgz
>
> The sanity went well for simplex, duplex and standard external storage.
>
> Regards,
> Nicolae Jascanu, Ph.D.
> TSD Software Engineer
>
>
>
> Internet Of Things Group
> Galati, Romania
>
> -----Original Message-----
> From: Sun, Austin <austin.sun at intel.com>
> Sent: Friday, August 7, 2020 18:05
> To: Pratik M. <pvmpublic at gmail.com>; Jascanu, Nicolae 
> <nicolae.jascanu at intel.com>
> Cc: starlingx-discuss at lists.starlingx.io
> Subject: RE: [Starlingx-discuss] Sanity TC code or output
>
> Hi Pratik:
>     The R3.0 images should tag as rc-3.0-centos-stable-latest.  Would 
> you like check your env via this command
>
> grep 'registry\.local' 
> /opt/platform/armada/19.12/stx-openstack/1.0-19-centos-stable-latest/s
> tx-openstack-stx-openstack.yaml
>
> Thanks.
> BR
> Austin Sun.
>
> -----Original Message-----
> From: Pratik M. <pvmpublic at gmail.com>
> Sent: Friday, August 7, 2020 4:22 PM
> To: Jascanu, Nicolae <nicolae.jascanu at intel.com>
> Cc: starlingx-discuss at lists.starlingx.io
> Subject: Re: [Starlingx-discuss] Sanity TC code or output
>
> Thank you. I am using R3.0 19.12 (pl. see below). This seems to be a known issue.
> http://lists.starlingx.io/pipermail/starlingx-discuss/2020-July/009270
> .html
>
> I guess the charts are OK, but the upstream docker images changed? So even though the tests passed when R3.0 was released, the openstack install will fail for everyone trying to use R3.0, now.
>
> [sysadmin at controller-0 ~(keystone_admin)]$ cat /etc/build.info ### ### StarlingX
> ###     Release 19.12
> ###
>
> OS="centos"
> SW_VERSION="19.12"
> BUILD_TARGET="Host Installer"
> BUILD_TYPE="Formal"
> BUILD_ID="r/stx.3.0"
>
> JOB="STX_BUILD_3.0"
> BUILD_BY="starlingx.build at cengn.ca"
> BUILD_NUMBER="21"
> BUILD_HOST="starlingx_mirror"
> BUILD_DATE="2019-12-13 02:30:00 +0000"
>
> Thanks
> Pratik
>
> On Thu, Aug 6, 2020 at 5:25 PM Jascanu, Nicolae <nicolae.jascanu at intel.com> wrote:
> >
> > Hi Pratik,
> > We are using for regular sanity the tests located at:
> > https://opendev.org/starlingx/test/src/branch/master/automated-robot
> > -s
> > uite/Tests
> >
> > Could you please tell what version you installed?
> > The output of: cat /etc/build.info will be useful.
> >
> > Regards,
> > Nicolae Jascanu, Ph.D.
> > TSD Software Engineer
> >
> >
> >
> > Internet Of Things Group
> > Galati, Romania
> >
> > -----Original Message-----
> > From: Pratik M. <pvmpublic at gmail.com>
> > Sent: Tuesday, August 4, 2020 13:12
> > To: starlingx-discuss at lists.starlingx.io
> > Subject: [Starlingx-discuss] Sanity TC code or output
> >
> > Hi,
> > I am seeing stx-openstack apply failure w/ R3.0. I am following the 
> > steps from documentation. Seems others are seeing this too
> > https://bugs.launchpad.net/starlingx/+bug/1889023
> >
> > But the "Sanity OpenStack" TC must have passed, so I want to compare my steps with the ones there, to figure out if there is a difference.
> > Can someone point me to either the code or the output of the test cases?
> >
> > Thanks
> > Pratik
> >
> > _______________________________________________
> > 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