June 2017 - dev - Rdo List Archives

[rdo-list] [Fedocal] Reminder meeting : RDO meeting

by hguemar＠fedoraproject.org

Dear all, You are kindly invited to the meeting: RDO meeting on 2017-06-28 from 15:00:00 to 16:00:00 UTC At rdo(a)irc.freenode.net The meeting will be about: RDO IRC meeting [Agenda at https://etherpad.openstack.org/p/RDO-Meeting ](https://etherpad.openstack.org/p/RDO-Meeting) Every Wednesday on #rdo on Freenode IRC Source: https://apps.fedoraproject.org/calendar/meeting/2017/

6 years, 9 months

1
0
0 / 0

[rdo-list] Automation and Identifiers

by Udi Kalifon

Hello. We are currently updating the automation infrastructure to support the changes in the GUI in OSP12. The work to support the new deployment counters (which replace the assign nodes) is finished, and the validators didn't require any work to be supported but we still refactored the infrastructure to work much faster (more on that later). The rest of the infrastructure will be updated hopefully in the next few days, when some bug fixes land in upstream and we can play with the features. We also need your help. In many places in the automation, we are finding the elements we need without having any identifiers (no ids or any unique classes or other attributes) at all. We find these elements by exhaustively searching the DOM, starting from a parent element that we can identify, and searching its children and their children etc... We also have to rely on the text in the elements in some places, which will be a blocker for us if we ever want to support i18n. This way of working is not only slow and takes a lot of effort from us, but can also fail the tests sometimes. For example, when an element gets unmapped from the DOM (when it's updated, or when a dialog closes, or when we navigate to another page), we need to re-search it. We don't always know when an element becomes "stale" like that because it's not always something that we initiated, and it still surprises us here and there. The problem of stale elements would not be a problem for us if we had an identifier for all the elements - because our infrastructure is already pretty smart and handles the StaleElementException for us by automatically and transparently searching for the element again, using the same identifier that was used the first time. This means that, for elements with identifiers, an event like that can happen at any point in the middle of any script and the test developer doesn't need to bother with it. But when an element doesn't have an identifier this magic can't work, and we crash. With elements that have no identifiers we need to be able to predict when they'll become stale, and it's always ugly and heuristic. Another problem with lack of identifiers is that sooner or later we'll just get stuck and won't be able to interact with certain elements in the GUI, because we simply won't be able to tell some of the elements from each other. Some of the new features which I haven't started automating yet have a very complex GUI and it will probably present a challenge. In the meantime, on a more optimistic note, I was able to get much better at identifying hard-to-identify elements. These identifiers are still fragile and they rely on the structure of the DOM - but they eliminate the need for an exhaustive search and the infrastructure can handle these elements if they become stale. I refactored some of our code with this approach and even got a significant performance increase with the validators infrastructure, which was so slow that it sometimes missed if a validator ran or not. I will update the Automation Identifiers document in the next few days. I'll delete all the irrelevant sections of it (which are probably 99% of the document) and start listing which identifiers we'd ask to have where. We should also make it a rule that in the future, any new feature that is delivered in the GUI, will have identifiers for the automation built-in from the start. Sorry for the long email, I wanted to report on what's going on in the automation front in addition to bringing up the request for identifiers again. Thanks a lot for listening. Regards, Udi Kalifon; Senior QE; RHOS-UI Automation

6 years, 10 months

1
1
0 / 0

[rdo-list] tripleo install undercloud fail

by qinglong.dong＠horebdata.cn

Hi all, I want to install an undercloud node on an baremetal machine following "http://tripleo.org/installation/installation.html#installing-the-undercloud". But I failed when I excuted "openstack undercloud install". Here are some logs. Anyone can help me? Thanks! 2017-06-26 11:46:17,940 INFO: Notice: /Stage[main]/Apache::Service/Service[httpd]: Dependency Mysql_user[keystone@%] has failures: true 2017-06-26 11:46:17,940 INFO: Notice: /Stage[main]/Apache::Service/Service[httpd]: Dependency Mysql_user[keystone(a)192.168.24.1] has failures: true 2017-06-26 11:46:17,940 INFO: Notice: /Stage[main]/Apache::Service/Service[httpd]: Dependency Mysql_database[heat] has failures: true 2017-06-26 11:46:17,940 INFO: Notice: /Stage[main]/Apache::Service/Service[httpd]: Dependency Mysql_user[heat@%] has failures: true 2017-06-26 11:46:17,941 INFO: Notice: /Stage[main]/Apache::Service/Service[httpd]: Dependency Mysql_user[heat(a)192.168.24.1] has failures: true 2017-06-26 11:46:17,941 INFO: Notice: /Stage[main]/Apache::Service/Service[httpd]: Dependency Mysql_database[ironic] has failures: true 2017-06-26 11:46:17,941 INFO: Notice: /Stage[main]/Apache::Service/Service[httpd]: Dependency Mysql_user[ironic@%] has failures: true 2017-06-26 11:46:17,941 INFO: Notice: /Stage[main]/Apache::Service/Service[httpd]: Dependency Mysql_user[ironic(a)192.168.24.1] has failures: true 2017-06-26 11:46:17,941 INFO: Notice: /Stage[main]/Apache::Service/Service[httpd]: Dependency Mysql_database[zaqar] has failures: true 2017-06-26 11:46:17,941 INFO: Notice: /Stage[main]/Apache::Service/Service[httpd]: Dependency Mysql_user[zaqar@%] has failures: true 2017-06-26 11:46:17,941 INFO: Notice: /Stage[main]/Apache::Service/Service[httpd]: Dependency Mysql_user[zaqar(a)192.168.24.1] has failures: true 2017-06-26 11:46:17,941 INFO: Notice: /Stage[main]/Apache::Service/Service[httpd]: Dependency Rabbitmq_plugin[rabbitmq_management] has failures: true 2017-06-26 11:46:17,941 INFO: Warning: /Stage[main]/Apache::Service/Service[httpd]: Skipping because of failed dependencies 2017-06-26 11:46:17,941 INFO: Notice: /Stage[main]/Keystone::Deps/Anchor[keystone::service::end]: Dependency Exec[os-net-config] has failures: true 2017-06-26 11:46:17,941 INFO: Notice: /Stage[main]/Keystone::Deps/Anchor[keystone::service::end]: Dependency Mysql_database[keystone] has failures: true 2017-06-26 11:46:17,942 INFO: Notice: /Stage[main]/Keystone::Deps/Anchor[keystone::service::end]: Dependency Mysql_user[keystone@%] has failures: true 2017-06-26 11:46:17,942 INFO: Notice: /Stage[main]/Keystone::Deps/Anchor[keystone::service::end]: Dependency Mysql_user[keystone(a)192.168.24.1] has failures: true 2017-06-26 11:46:17,942 INFO: Notice: /Stage[main]/Keystone::Deps/Anchor[keystone::service::end]: Dependency Mysql_database[heat] has failures: true 2017-06-26 11:46:17,942 INFO: Notice: /Stage[main]/Keystone::Deps/Anchor[keystone::service::end]: Dependency Mysql_user[heat@%] has failures: true 2017-06-26 11:46:17,942 INFO: Notice: /Stage[main]/Keystone::Deps/Anchor[keystone::service::end]: Dependency Mysql_user[heat(a)192.168.24.1] has failures: true 2017-06-26 11:46:17,942 INFO: Notice: /Stage[main]/Keystone::Deps/Anchor[keystone::service::end]: Dependency Mysql_database[ironic] has failures: true 2017-06-26 11:46:17,942 INFO: Notice: /Stage[main]/Keystone::Deps/Anchor[keystone::service::end]: Dependency Mysql_user[ironic@%] has failures: true 2017-06-26 11:46:17,942 INFO: Notice: /Stage[main]/Keystone::Deps/Anchor[keystone::service::end]: Dependency Mysql_user[ironic(a)192.168.24.1] has failures: true 2017-06-26 11:46:17,942 INFO: Notice: /Stage[main]/Keystone::Deps/Anchor[keystone::service::end]: Dependency Mysql_database[zaqar] has failures: true 2017-06-26 11:46:17,942 INFO: Notice: /Stage[main]/Keystone::Deps/Anchor[keystone::service::end]: Dependency Mysql_user[zaqar@%] has failures: true 2017-06-26 11:46:17,942 INFO: Notice: /Stage[main]/Keystone::Deps/Anchor[keystone::service::end]: Dependency Mysql_user[zaqar(a)192.168.24.1] has failures: true 2017-06-26 11:46:17,942 INFO: Notice: /Stage[main]/Keystone::Deps/Anchor[keystone::service::end]: Dependency Rabbitmq_plugin[rabbitmq_management] has failures: true 2017-06-26 11:46:17,943 INFO: Warning: /Stage[main]/Keystone::Deps/Anchor[keystone::service::end]: Skipping because of failed dependencies 2017-06-26 11:46:17,943 INFO: Error: Failed to apply catalog: Insufficient credentials to authenticate 2017-06-26 11:46:25,651 INFO: + rc=1 2017-06-26 11:46:25,651 INFO: + set -e 2017-06-26 11:46:25,651 INFO: + echo 'puppet apply exited with exit code 1' 2017-06-26 11:46:25,651 INFO: puppet apply exited with exit code 1 2017-06-26 11:46:25,651 INFO: + '[' 1 '!=' 2 -a 1 '!=' 0 ']' 2017-06-26 11:46:25,651 INFO: + exit 1 2017-06-26 11:46:25,652 INFO: [2017-06-26 11:46:25,651] (os-refresh-config) [ERROR] during configure phase. [Command '['dib-run-parts', '/usr/libexec/os-refresh-config/configure.d']' returned non-zero exit status 1] 2017-06-26 11:46:25,652 INFO: 2017-06-26 11:46:25,652 INFO: [2017-06-26 11:46:25,651] (os-refresh-config) [ERROR] Aborting... 2017-06-26 11:46:25,657 DEBUG: An exception occurred Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/instack_undercloud/undercloud.py", line 1592, in install _run_orc(instack_env) File "/usr/lib/python2.7/site-packages/instack_undercloud/undercloud.py", line 1282, in _run_orc _run_live_command(args, instack_env, 'os-refresh-config') File "/usr/lib/python2.7/site-packages/instack_undercloud/undercloud.py", line 593, in _run_live_command raise RuntimeError('%s failed. See log for details.' % name) RuntimeError: os-refresh-config failed. See log for details. 2017-06-26 11:46:25,657 ERROR: ############################################################################# Undercloud install failed. Reason: os-refresh-config failed. See log for details. See the previous output for details about what went wrong. The full install log can be found at /home/stack/.instack/install-undercloud.log. ############################################################################# Traceback (most recent call last): File "<string>", line 1, in <module> File "/usr/lib/python2.7/site-packages/instack_undercloud/undercloud.py", line 1592, in install _run_orc(instack_env) File "/usr/lib/python2.7/site-packages/instack_undercloud/undercloud.py", line 1282, in _run_orc _run_live_command(args, instack_env, 'os-refresh-config') File "/usr/lib/python2.7/site-packages/instack_undercloud/undercloud.py", line 593, in _run_live_command raise RuntimeError('%s failed. See log for details.' % name) RuntimeError: os-refresh-config failed. See log for details. Command 'instack-install-undercloud' returned non-zero exit status 1

6 years, 10 months

1
0
0 / 0

[rdo-list] New "RDO Package Maintainer Guide" in website

by Alfredo Moralejo Alonso

Hi, As part of the actions to improve RDO community according to the feedback received in the last contributor survey, we have created a "RDO Package Maintainer Guide" in our website documentation [1]. Part of it is just reordering of existing information, but there is some new content which I'd like to highlight: 1. An onboarding guide for new maintainers [2] 2. A document about the tasks that packagers should perform when as preparation for a new OpenStack version [3] This is just an initial version, we'll keep adding information but i encourage everyone to send new content or report what it’s missing to make it great! [4] Best regards, Alfredo [1] https://www.rdoproject.org/documentation/rdo-packaging/ [2] https://www.rdoproject.org/documentation/onboarding/ [3] https://www.rdoproject.org/documentation/branching/ [4] https://www.rdoproject.org/community/#docs-and-website

6 years, 10 months

1
0
0 / 0

[rdo-list] State of RDO on power and aarch64?

by Rich Bowen

I wanted to draw attention to this thread over on the CentOS ci-users list - https://lists.centos.org/pipermail/ci-users/2017-June/000601.html - in the hopes that some RDO folks can go comment on that. It has received no responses, and it's likely that some people simply never saw the thread. Thanks. -- Rich Bowen - rbowen(a)redhat.com RDO Community Liaison http://rdoproject.org @RDOCommunity

6 years, 10 months

2
1
0 / 0

[rdo-list] Need inputs on RDO Packages Naming Convention

by Chandan kumar

Hello, In order to automate most of the packaging task, It is necessary to have a consistency in the RDO Packages naming. We have created an etherpad [1.] to collect inputs for the same. Feel free to take a look and provide your feedback there. Links: [1.] https://review.rdoproject.org/etherpad/p/rdo_packages_naming Thanks, Chandan Kumar

6 years, 10 months

1
0
0 / 0

[rdo-list] [Meeting] RDO meeting - 2017-06-21

by Chandan kumar

============================== #rdo: RDO meeting - 2017-06-21 ============================== Meeting started by chandankumar at 15:01:03 UTC. The full logs are available at http://eavesdrop.openstack.org/meetings/rdo_meeting___2017_06_21/2017/rdo... . Meeting summary --------------- * tripleo-common adding a dependency from a package in the Ceph SIG repo (chandankumar, 15:05:06) * LINK: https://review.openstack.org/#/c/469644/14//COMMIT_MSG@16 (fultonj, 15:10:39) * LINK: https://cbs.centos.org/repos/storage7-ceph-jewel-candidate/ (fultonj, 15:16:00) * LINK: https://cbs.centos.org/repos/storage7-ceph-common-candidate/ (fultonj, 15:16:05) * LINK: http://paste.openstack.org/show/613306/ (amoralej, 15:18:23) * LINK: https://review.rdoproject.org/r/#/c/6809 (fultonj, 15:19:44) * LINK: https://review.openstack.org/#/c/469644/14//COMMIT_MSG@16 (fultonj, 15:21:26) * Package naming convention for RDO packages (chandankumar, 15:36:42) * LINK: https://review.rdoproject.org/etherpad/p/rdo_packages_naming (chandankumar, 15:38:12) * ACTION: chandankumar to drop an email for inputs on RDO packages naming conventions (chandankumar, 15:47:14) * RDO Cloud scheduled maintenance on June 22, 1:00 UTC (1 hour) (chandankumar, 15:50:27) * ACTION: jpena to send outage mail to rdo list (chandankumar, 15:52:16) * RDO Cloud scheduled maintenance on June 22, 1:00 UTC (1 hour) (chandankumar, 15:52:26) * chair for next meeting (chandankumar, 15:54:59) * ACTION: ykarel to chair for next meeting. (chandankumar, 15:55:44) * open floor (chandankumar, 15:55:57) Meeting ended at 16:00:30 UTC. Action items, by person ----------------------- * chandankumar * chandankumar to drop an email for inputs on RDO packages naming conventions * jpena * jpena to send outage mail to rdo list * ykarel * ykarel to chair for next meeting. People present (lines said) --------------------------- * chandankumar (58) * fultonj (35) * amoralej (27) * dmsimard (23) * jpena (13) * openstack (10) * jruzicka (8) * trown (4) * number80 (3) * jschlueter (3) * ykarel (2) * rdobot (2) * Duck (1) * jistr (1) * EmilienM (1) Generated by `MeetBot`_ 0.1.4

6 years, 10 months

1
0
0 / 0

[rdo-list] [infra][outage] OS1 and RDO Cloud planned maintenance on June 22, 1:00 UTC

by Javier Pena

Hi, There is a planned network maintenance for OS1 and the RDO Cloud happening on June 22, at 1:00 UTC. It is planned to take 1 hour. During that time, several services will be impacted: - www.rdoproject.org - images.rdoproject.org - logs.rdoproject.org - The CI pools for review.rdoproject.org - and maybe others, if they are hosted on one of the affected clouds or depend on a VM hosted in them Regards, Javier

6 years, 10 months

1
0
0 / 0

[rdo-list] RDO-CI Scrum Weekly Scrum Recap

by Ronelle Landy

Greetings All, Links to the RDO-CI team scrum etherpad [1] and recording [2] from this week's meeting are below. Highlights: - Created archive etherpad for notes from meetings prior to January 2017 [3] - Feature sets Feature sets are exclusively used in upstream CI only atm Requirement: reproduce upstream CI with local tripleo-quickstart invocations Previously we had discussed removing upstream specific keys/values from feature sets New thought.. enable default libvirt to use the feature sets as they are currently defined - There is a certain amount of momentum and shared understanding w/ feature sets upstream (example [4]) - Enable mult-nic net-iso w/ libvirt [5] - This also means checking out openstack-infra/tripleo-ci along w/ tripleo-quckstart - devmode design [6]: Assigned and triaged requested features (to be continued on Thursday) major request to make quickstart options available from devmode - adarazs is working on this [7] - 3party CI - what is the plan? Moving workloads on RH1 to RDO Cloud in RDO Software Factory infra Current status is that the infra is not ready for us dmsimard is our point of contact Right now - we do not have a specific date by which we have to move?\ - DNS/caching See conversation on escalation card [8] for RDO Cloud sshnaidm set up a DNS server as did Graeme for the interim. No long term solution yet. Two reviews out there to change dns server values and single source the dns reference. Status of usage: - ci.centos google dns - RH1 uses internal 10. address - rdo phase 2/qeos 7 uses internal dns [1] - https://review.rdoproject.org/etherpad/p/rdo-infra-scrum [2] - https://bluejeans.com/s/aBIRj/ [3] - https://review.rdoproject.org/etherpad/p/rdo-infra-scrum-archive [4] - https://review.openstack.org/#/c/474772/ [5] - https://trello.com/c/bHPuUIQe/261-add-multi-nic-network-isolation-to-trip... [6] - https://review.rdoproject.org/etherpad/p/devmode-design [7] - https://trello.com/c/a79CQzFq/263-extend-quickstartsh-to-use-instead-of-d... [8] - https://trello.com/c/YqSEdBBT/141-all-rdo-ci-is-intermittently-down-googl... /R

6 years, 10 months

1
0
0 / 0

[rdo-list] ocata centos 7.3 trove patches

by Ignazio Cassano

Hi All, I'd like to know if and when the following patches https://review.openstack.org/#/c/455463/ will be applied and pkackaged for trove ocata on centos 7.3. Installing centos 7.3 ocata trove I got some errors in taskmanager like in the following link: https://bugs.launchpad.net/openstack-ansible/+bug/1672452 Regards Ignazio

6 years, 10 months

2
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

dev June 2017