[Starlingx-discuss] FW: Sanity Test - ISO 20181211
Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2018-Dec-11 (link<http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20181211T060000Z/outputs/iso/>) Sanity Test is executed in a Virtual Environment Status: RED Simplex Setup 03 TCs [PASS] | 01 TCs [FAIL] Provisioning 00 TCs [PASS] | 01 TCs [FAIL] Sanity 00 TCs [PASS] | 18 TCs [FAIL] TOTAL: [ 03 TCs PASS ] | [ 20 TCs FAIL ] Duplex Setup 03 TCs [PASS] | 01 TCs [FAIL] Provisioning 00 TCs [PASS] | 01 TCs [FAIL] Sanity 00 TCs [PASS] | 19 TCs [FAIL] TOTAL: [ 03 TCs PASS ] | [ 21 TCs FAIL ] Multinode Controller Storage Setup 03 TCs [PASS] | 01 TCs [FAIL] Provisioning 00 TCs [PASS] | 01 TCs [FAIL] Sanity 00 TCs [PASS] | 19 TCs [FAIL] TOTAL: [ 03 TCs PASS ] | [ 21 TCs FAIL ] Multinode Dedicated Storage Setup 03 TCs [PASS] | 01 TCs [FAIL] Provisioning 00 TCs [PASS] | 01 TCs [FAIL] Sanity 00 TCs [PASS] | 19 TCs [FAIL] TOTAL: [ 03 TCs PASS ] | [ 21 TCs FAIL ] ------------------------------------------------------------------ This issue was found by our Robot test framework. During config_controller, the suite copy a Config file from host to StarlingX system. Robot uses SSHLibrary keyword, such keyword uses sftp service to perform the transfer file. Such transfer failed due to sftp service is not working on the system. Launchpad open: https://bugs.launchpad.net/starlingx/+bug/1808054 Regards. Juan Carlos Alonso
I think you need to get a new ISO updated and deploy the system again. Until now there is not a way to update the installation while it is running. Regards. Juan Carlos Alonso From: volker.von.hoesslin@gmx.de [mailto:volker.von.hoesslin@gmx.de] Sent: Wednesday, December 12, 2018 6:32 AM To: starlingx <starlingx-discuss@lists.starlingx.io> Subject: Re: [Starlingx-discuss] FW: Sanity Test - ISO 20181211 regardless of the fact that this build failed, if i already have an installation running, how do i get it up to date, are there patch files somewhere i don't know anything about? volker Gesendet: Dienstag, 11. Dezember 2018 um 22:51 Uhr Von: "Alonso, Juan Carlos" <juan.carlos.alonso@intel.com<mailto:juan.carlos.alonso@intel.com>> An: starlingx <starlingx-discuss@lists.starlingx.io<mailto:starlingx-discuss@lists.starlingx.io>> Betreff: [Starlingx-discuss] FW: Sanity Test - ISO 20181211 Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2018-Dec-11 (link<http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20181211T060000Z/outputs/iso/>) Sanity Test is executed in a Virtual Environment Status: RED Simplex Setup 03 TCs [PASS] | 01 TCs [FAIL] Provisioning 00 TCs [PASS] | 01 TCs [FAIL] Sanity 00 TCs [PASS] | 18 TCs [FAIL] TOTAL: [ 03 TCs PASS ] | [ 20 TCs FAIL ] Duplex Setup 03 TCs [PASS] | 01 TCs [FAIL] Provisioning 00 TCs [PASS] | 01 TCs [FAIL] Sanity 00 TCs [PASS] | 19 TCs [FAIL] TOTAL: [ 03 TCs PASS ] | [ 21 TCs FAIL ] Multinode Controller Storage Setup 03 TCs [PASS] | 01 TCs [FAIL] Provisioning 00 TCs [PASS] | 01 TCs [FAIL] Sanity 00 TCs [PASS] | 19 TCs [FAIL] TOTAL: [ 03 TCs PASS ] | [ 21 TCs FAIL ] Multinode Dedicated Storage Setup 03 TCs [PASS] | 01 TCs [FAIL] Provisioning 00 TCs [PASS] | 01 TCs [FAIL] Sanity 00 TCs [PASS] | 19 TCs [FAIL] TOTAL: [ 03 TCs PASS ] | [ 21 TCs FAIL ] ------------------------------------------------------------------ This issue was found by our Robot test framework. During config_controller, the suite copy a Config file from host to StarlingX system. Robot uses SSHLibrary keyword, such keyword uses sftp service to perform the transfer file. Such transfer failed due to sftp service is not working on the system. Launchpad open: https://bugs.launchpad.net/starlingx/+bug/1808054 Regards. Juan Carlos Alonso _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io<mailto:Starlingx-discuss@lists.starlingx.io> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
Not entirely true, StarlingX has an update service so you can upgrade your deployment at any given time, I suggest you follow the stx-update project to get an idea of how that works. If you have a deployment based on the latest stable release you are good to go. These daily builds are getting patches and code for features that are not ready for production nor fully tested until the next release cycle. We are basically fixing bugs being introduced as part of the normal development process. CL On Thu, Dec 13, 2018, 7:31 AM <volker.von.hoesslin@gmx.de wrote:
outch, that's not so good :( how are the plans to offer updates about patches here?
volker...
*Gesendet:* Mittwoch, 12. Dezember 2018 um 17:57 Uhr *Von:* "Alonso, Juan Carlos" <juan.carlos.alonso@intel.com> *An:* "volker.von.hoesslin@gmx.de" <volker.von.hoesslin@gmx.de>, starlingx <starlingx-discuss@lists.starlingx.io> *Betreff:* RE: [Starlingx-discuss] FW: Sanity Test - ISO 20181211
I think you need to get a new ISO updated and deploy the system again.
Until now there is not a way to update the installation while it is running.
Regards.
Juan Carlos Alonso
*From:* volker.von.hoesslin@gmx.de [mailto:volker.von.hoesslin@gmx.de] *Sent:* Wednesday, December 12, 2018 6:32 AM *To:* starlingx <starlingx-discuss@lists.starlingx.io> *Subject:* Re: [Starlingx-discuss] FW: Sanity Test - ISO 20181211
regardless of the fact that this build failed, if i already have an installation running, how do i get it up to date, are there patch files somewhere i don't know anything about?
volker
*Gesendet:* Dienstag, 11. Dezember 2018 um 22:51 Uhr *Von:* "Alonso, Juan Carlos" <juan.carlos.alonso@intel.com> *An:* starlingx <starlingx-discuss@lists.starlingx.io> *Betreff:* [Starlingx-discuss] FW: Sanity Test - ISO 20181211
Status of the Sanity Test for last CENGN ISO: *bootimage.iso from 2018-Dec-11 *(link <http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20181211T060000Z/outputs/iso/> )
Sanity Test is executed in a *Virtual Environment*
Status: *RED*
*Simplex*
Setup 03 TCs [PASS] | 01 TCs [FAIL]
Provisioning 00 TCs [PASS] | 01 TCs [FAIL]
Sanity 00 TCs [PASS] | 18 TCs [FAIL]
TOTAL: [ 03 TCs PASS ] | [ 20 TCs FAIL ]
*Duplex*
Setup 03 TCs [PASS] | 01 TCs [FAIL]
Provisioning 00 TCs [PASS] | 01 TCs [FAIL]
Sanity 00 TCs [PASS] | 19 TCs [FAIL]
TOTAL: [ 03 TCs PASS ] | [ 21 TCs FAIL ]
*Multinode Controller Storage*
Setup 03 TCs [PASS] | 01 TCs [FAIL]
Provisioning 00 TCs [PASS] | 01 TCs [FAIL]
Sanity 00 TCs [PASS] | 19 TCs [FAIL]
TOTAL: [ 03 TCs PASS ] | [ 21 TCs FAIL ]
*Multinode Dedicated Storage*
Setup 03 TCs [PASS] | 01 TCs [FAIL]
Provisioning 00 TCs [PASS] | 01 TCs [FAIL]
Sanity 00 TCs [PASS] | 19 TCs [FAIL]
TOTAL: [ 03 TCs PASS ] | [ 21 TCs FAIL ]
------------------------------------------------------------------
This issue was found by our Robot test framework.
During config_controller, the suite copy a Config file from host to StarlingX system. Robot uses SSHLibrary keyword, such keyword uses sftp service to perform the transfer file. Such transfer failed due to sftp service is not working on the system.
Launchpad open: https://bugs.launchpad.net/starlingx/+bug/1808054
Regards.
Juan Carlos Alonso
_______________________________________________ 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
On Thu, Dec 13, 2018 at 8:02 AM Cesar Lara <cesarlarag@gmail.com> wrote:
Not entirely true, StarlingX has an update service so you can upgrade your deployment at any given time, I suggest you follow the stx-update project to get an idea of how that works.
I do not think that the process of creating update/upgrade packages is documented publicly yet. This service uses specifically built files for this purpose, it does not use a later ISO build.
If you have a deployment based on the latest stable release you are good to go. These daily builds are getting patches and code for features that are not ready for production nor fully tested until the next release cycle. We are basically fixing bugs being introduced as part of the normal development process.
As I understand the process, updates to the internal package repo need to be loaded onto the controller, then those updates can be schedules out to the various nodes. It is the creation of those updates that I think we are missing here. I am not aware of a documented way to take a later ISO and apply that directly to achieve the same result. I would love to be wrong about that... dt -- Dean Troyer dtroyer@gmail.com
On Thu, 2018-12-13 at 11:13 -0600, Dean Troyer wrote:
On Thu, Dec 13, 2018 at 8:02 AM Cesar Lara <cesarlarag@gmail.com> wrote:
Not entirely true, StarlingX has an update service so you can upgrade your deployment at any given time, I suggest you follow the stx-update project to get an idea of how that works.
I do not think that the process of creating update/upgrade packages is documented publicly yet. This service uses specifically built files for this purpose, it does not use a later ISO build.
If you have a deployment based on the latest stable release you are good to go. These daily builds are getting patches and code for features that are not ready for production nor fully tested until the next release cycle. We are basically fixing bugs being introduced as part of the normal development process.
As I understand the process, updates to the internal package repo need to be loaded onto the controller, then those updates can be schedules out to the various nodes. It is the creation of those updates that I think we are missing here. I am not aware of a documented way to take a later ISO and apply that directly to achieve the same result.
We don't have a way to provide updates for the people that already installed a StarlingX instance. I would recommend to use the r/2018.10 ISO, the master branch is on heavy development and prone to bugs. However, if we want to fix it, I think we need to : 1) Provide the packages with updates: we should pay special attention into versioning of every package. 2) Find a way to install the updates and download them to be served into the additional controllers and computes. (not sure if this is what stx-update does)
I would love to be wrong about that...
dt
On Thu, Dec 13, 2018 at 11:35 AM Cordoba Malibran, Erich <erich.cordoba.malibran@intel.com> wrote:
On Thu, 2018-12-13 at 11:13 -0600, Dean Troyer wrote:
On Thu, Dec 13, 2018 at 8:02 AM Cesar Lara <cesarlarag@gmail.com> wrote:
Not entirely true, StarlingX has an update service so you can upgrade your deployment at any given time, I suggest you follow the stx-update project to get an idea of how that works.
I do not think that the process of creating update/upgrade packages is documented publicly yet. This service uses specifically built files for this purpose, it does not use a later ISO build.
If you have a deployment based on the latest stable release you are good to go. These daily builds are getting patches and code for features that are not ready for production nor fully tested until the next release cycle. We are basically fixing bugs being introduced as part of the normal development process.
As I understand the process, updates to the internal package repo need to be loaded onto the controller, then those updates can be schedules out to the various nodes. It is the creation of those updates that I think we are missing here. I am not aware of a documented way to take a later ISO and apply that directly to achieve the same result.
We don't have a way to provide updates for the people that already installed a StarlingX instance.
Then i had this idea wrong, i had the strong belive we had stx-update for this reason Can someone help me to point about external documentation for stx-update? I would recommend to use the r/2018.10
ISO, the master branch is on heavy development and prone to bugs.
However, if we want to fix it, I think we need to :
1) Provide the packages with updates: we should pay special attention into versioning of every package.
Don't we provide a list of rpm's on every new build?
2) Find a way to install the updates and download them to be served into the additional controllers and computes. (not sure if this is what stx-update does)
Me neither , i think we might need a good education mail about what does stx-update does
I would love to be wrong about that...
dt
_______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
participants (6)
-
Alonso, Juan Carlos
-
Cesar Lara
-
Cordoba Malibran, Erich
-
Dean Troyer
-
Victor Rodriguez
-
volker.von.hoesslin＠gmx.de