We have a valid iso. The build was time stamp 20210514T224518Z http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/5.0/centos/flock/202105... We do NOT yet have a successful build of the docker images The failed images are: *00:19:18* stx-openstackclients *00:19:18* stx-placement *00:19:18* stx-platformclients *00:19:18* stx-vault-manager On 2021-05-15 2:41 p.m., Scott Little wrote:
I can confirm the build is now using the intended branch.
The following packages were 'rolled back' to these earlier versions ...
cgts-client-1.0-219.tis.x86_64.rpm cgts-client-wheels-1.0-219.tis.x86_64.rpm collectd-extensions-1.0-0.tis.60.x86_64.rpm controllerconfig-1.0-249.tis.x86_64.rpm controllerconfig-wheels-1.0-249.tis.x86_64.rpm distributedcloud-client-dcmanagerclient-1.0.0-1.tis.30.noarch.rpm distributedcloud-client-wheels-1.0.0-1.tis.30.noarch.rpm distributedcloud-dccommon-1.0.0-1.tis.259.noarch.rpm distributedcloud-dcdbsync-1.0.0-1.tis.259.noarch.rpm distributedcloud-dcmanager-1.0.0-1.tis.259.noarch.rpm distributedcloud-dcorch-1.0.0-1.tis.259.noarch.rpm distributedcloud-wheels-1.0.0-1.tis.259.noarch.rpm fm-api-1.0-38.tis.x86_64.rpm fm-api-doc-1.0-38.tis.x86_64.rpm fm-api-wheels-1.0-38.tis.x86_64.rpm fm-doc-1.0-36.tis.x86_64.rpm io-scheduler-1.0-2.tis.x86_64.rpm mtce-1.0-199.tis.x86_64.rpm mtce-common-dev-1.0-139.tis.x86_64.rpm mtce-debuginfo-1.0-199.tis.x86_64.rpm mtce-dev-1.0-199.tis.x86_64.rpm mtce-hostw-1.0-199.tis.x86_64.rpm mtce-hwmon-1.0-199.tis.x86_64.rpm mtce-lmon-1.0-199.tis.x86_64.rpm mtce-pmon-1.0-199.tis.x86_64.rpm nfv-1.0-179.tis.x86_64.rpm nfv-client-1.0-179.tis.x86_64.rpm nfv-common-1.0-179.tis.x86_64.rpm nfv-plugins-1.0-179.tis.x86_64.rpm nfv-tools-1.0-179.tis.x86_64.rpm nfv-vim-1.0-179.tis.x86_64.rpm nfv-wheels-1.0-179.tis.x86_64.rpm pam-config-1.0-7.tis.noarch.rpm platform-kickstarts-1.0.0-161.tis.noarch.rpm platform-kickstarts-extracfgs-1.0.0-161.tis.noarch.rpm platform-kickstarts-pxeboot-1.0.0-161.tis.noarch.rpm platform-util-1.0-53.tis.noarch.rpm platform-util-controller-1.0-53.tis.noarch.rpm platform-util-noncontroller-1.0-53.tis.noarch.rpm platform-util-wheels-1.0-53.tis.noarch.rpm playbookconfig-1.0-518.tis.x86_64.rpm puppet-manifests-1.0.0-754.tis.noarch.rpm python-k8sapp-cert-manager-1.0-15.tis.noarch.rpm python-k8sapp-cert-manager-wheels-1.0-15.tis.noarch.rpm python-k8sapp-nginx-ingress-controller-1.0-1.tis.noarch.rpm python-k8sapp-nginx-ingress-controller-wheels-1.0-1.tis.noarch.rpm python-k8sapp-oidc-1.0-43.tis.noarch.rpm python-k8sapp-oidc-wheels-1.0-43.tis.noarch.rpm python-k8sapp-openstack-1.0-82.tis.noarch.rpm python-k8sapp-openstack-wheels-1.0-82.tis.noarch.rpm python-k8sapp-portieris-1.0-19.tis.noarch.rpm python-k8sapp-portieris-wheels-1.0-19.tis.noarch.rpm python-k8sapp-ptp-notification-1.0-38.tis.noarch.rpm python-k8sapp-ptp-notification-wheels-1.0-38.tis.noarch.rpm python-k8sapp-rook-1.0-5.tis.noarch.rpm python-k8sapp-rook-wheels-1.0-5.tis.noarch.rpm python-k8sapp-vault-20.06-17.tis.noarch.rpm python-k8sapp-vault-wheels-20.06-17.tis.noarch.rpm sm-1.0.0-41.tis.x86_64.rpm sm-debuginfo-1.0.0-41.tis.x86_64.rpm starlingx-dashboard-1.0-260.tis.noarch.rpm starlingx-dashboard-wheels-1.0-260.tis.noarch.rpm stx-cert-manager-helm-1.0-15.tis.noarch.rpm stx-oidc-auth-helm-1.0-43.tis.noarch.rpm stx-openstack-helm-1.0-82.tis.noarch.rpm stx-portieris-helm-1.0-19.tis.noarch.rpm stx-ptp-notification-helm-1.0-38.tis.noarch.rpm stx-rook-ceph-1.0-5.tis.noarch.rpm stx-vault-helm-1.0-17.tis.noarch.rpm sysinv-1.0-2039.tis.x86_64.rpm sysinv-wheels-1.0-2039.tis.x86_64.rpm systemd-config-1.0-9.tis.noarch.rpm tsconfig-1.0-46.tis.x86_64.rpm tsconfig-wheels-1.0-46.tis.x86_64.rpm vault-helm-1.0-17.tis.noarch.rpm workerconfig-1.0-12.tis.x86_64.rpm workerconfig-standalone-1.0-12.tis.x86_64.rpm workerconfig-subfunction-1.0-12.tis.x86_64.rpm
On 2021-05-14 4:19 p.m., Scott Little wrote:
I regret to say that all STX 5.0 build to date have been invalid.
They have been picking up unintended content from the master branch.
The problem was first spotted several weeks ago, and we thought we had it fixed, but it turns out a build optimization has kept the the invalid content in place, rather than overwriting it with the correct STX.5.0 content.
I'm working to fix fully this time. Expect to see a few unscheduled builds this weekend. I'll let you know when I'm confident of the result.
With apologies,
Scott
_______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
_______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss