[openstack-dev] Update MAINTAINERS.rst for devstack

Hi, By its nature, devstack tends to attract new contributors proposing a wide-range of changes to just about every project under the Open Stack banner. These contributors often don't yet have the context to find the right people to help with some +1's. It's also nice for people approving the

[openstack-dev] [infra] Centos 7 images for HP Helion

Hi, I would like to get centos 7 based testing working, but I am stuck without images being provided in the HP Cloud. Rackspace has a (slightly quirky, but workable) image and we have an experimental job that runs fine. I am aware that building our own custom images with disk-image-builder is

Re: [openstack-dev] [infra] Centos 7 images for HP Helion

On 08/27/2014 08:31 PM, Karanbir Singh wrote: If you let me know what the issues with the Rackspace images are, I can try to reach out and help them work through those. The main issue was a verison of cloud-init installed via pip that conflicted with packaged python. I put a work-around in

Re: [openstack-dev] [bashate] .bashateignore

On 08/29/2014 10:42 PM, Sean Dague wrote: I'm actually kind of convinced now that none of these approaches are what we need, and that we should instead have a .bashateignore file in the root dir for the project instead, which would be regex that would match files or directories to throw out of

Re: [openstack-dev] [bashate] .bashateignore

On 09/02/2014 10:13 PM, Sean Dague wrote: One of the things that could make it better is to add file extensions to all shell files in devstack. This would also solve the issue of gerrit not syntax highlighting most of the files. If people are up for that, I'll propose a rename patch to get us

Re: [openstack-dev] [bashate] .bashateignore

On 09/03/2014 11:32 AM, Robert Collins wrote: if-has-bash-hashbang-and-is-versioned-then-bashate-it? That misses library files that aren't execed and have no #! This might be an appropriate rule for test infrastructure to generate a list for their particular project, but IMO I don't think we

Re: [openstack-dev] PostgreSQL jobs slow in the gate

On 09/18/2014 09:49 AM, Clark Boylan wrote: Recent sampling of test run times shows that our tempest jobs run against clouds using PostgreSQL are significantly slower than jobs run against clouds using MySQL. FYI There is a possibly relevant review out for max_connections limits [1], although

Re: [openstack-dev] [infra] recheck no bug and comment

On 07/16/2014 11:15 PM, Alexis Lee wrote: What do you think about allowing some text after the words recheck no bug? I think this is a good idea; I am often away from a change for a bit, something happens in-between and Jenkins fails it, but chasing it down days later is fairly pointless given

[openstack-dev] [bashate] towards inbox zero on bashate changes, release?

Hi, I took the liberty of rebasing and approving the fairly obvious and already +1'd bashate changes today that had been sitting for quite a while. What's left is minimal and fall into three categories 1) changes for auto-detection. IMO, we should drop all these and just leave bashate as

Re: [openstack-dev] FreeBSD host support

I do not want to hijack this thread with Solaris specific questions, but this point is a major sticking point for us too. To my knowledge, modifying devstack for anything not RHEL/Ubuntu is out of the question (they're not interested in supporting other OSes). I think if the question is does

Re: [openstack-dev] [bashate] towards inbox zero on bashate changes, release?

On 10/14/2014 04:03 PM, Ian Wienand wrote: Maybe it is time for a release? One thing; does the pre-release check run over TOT devstack and ensure there are no errors? We don't want to release and then 10 minutes later gate jobs start failing. Just to loop back on this ... Our main goal here

Re: [openstack-dev] [nova] pci pass through turing complete config options?

On 10/29/2014 12:42 AM, Doug Hellmann wrote: Another way to do this, which has been used in some other projects, is to define one option for a list of “names” of things, and use those names to make groups with each field I've proposed that in [1]. I look forward to some -1's :) OTOH,

[openstack-dev] [diskimage-builder] Tracing levels for scripts (119023)

Hi, My change [1] to enable a consistent tracing mechanism for the many scripts diskimage-builder runs during its build seems to have hit a stalemate. I hope we can agree that the current situation is not good. When trying to develop with diskimage-builder, I find myself constantly going and

Re: [openstack-dev] [diskimage-builder] Tracing levels for scripts (119023)

On 12/02/2014 03:46 PM, Clint Byrum wrote: 1) Conform all o-r-c scripts to the logging standards we have in OpenStack, or write new standards for diskimage-builder and conform them to those standards. Abolish non-conditional xtrace in any script conforming to the standards. Honestly in the

Re: [openstack-dev] [diskimage-builder] Tracing levels for scripts (119023)

On 12/03/2014 09:30 AM, Clint Byrum wrote: I for one find the idea of printing every cp, cat, echo and ls command out rather frustratingly verbose when scanning logs from a normal run. I for one find this ongoing discussion over a flag whose own help says -x -- turn on tracing not doing the

Re: [openstack-dev] [DevStack] Python dependencies: PyPI vs distro packages

On Mon, Aug 05, 2013 at 12:03:07PM -0500, Dean Troyer wrote: * proposals to use a tool to automatically decide between package and PyPI (harlowja, sdague): this works well on the surface, but anything that does not take in to account the dependencies in these packages going BOTH ways is going

Re: [openstack-dev] [DevStack] Python dependencies: PyPI vs distro packages

On Thu, Aug 08, 2013 at 10:10:09AM -0300, Monty Taylor wrote: I don't think we will gain much by auto-generating packages. What really is the difference between devstack auto-generating a package and having a human basically doing the same thing and sticking it in a repo? It just seems

[openstack-dev] Skipping tests in tempest via config file

Hi, I proposed a change to tempest that skips tests based on a config file directive [1]. Reviews were inconclusive and it was requested the idea be discussed more widely. Of course issues should go upstream first. However, sometimes test failures are triaged to a local/platform problem and it

[openstack-dev] [heat] puppet heat config file

Hi, The current heat puppet modules don't work to create the heat config file [1] My first attempt [2] created separate config files for each heat component. It was pointed out that configuration had been consolidated into a single file [3]. My second attempt [4] did this, but consensus seems

Re: [openstack-dev] [diskimage-builder] Tracing levels for scripts (119023)

On 12/04/2014 05:41 AM, Clint Byrum wrote: What if the patch is reworked to leave the current trace-all-the-time mode in place, and we iterate on each script to make tracing conditional as we add proper logging? I have run [1] over patchset 15 to keep whatever was originally using -x tracing

Re: [openstack-dev] [devstack] localrc for mutli-node setup

On 12/13/2014 07:03 AM, Danny Choi (dannchoi) wrote: I would like to use devstack to deploy OpenStack on a multi-node setup, i.e. separate Controller, Network and Compute nodes Did you see [1]? Contributions to make that better of course welcome. -i [1]

Re: [openstack-dev] [all] UserWarning: Unknown distribution option: 'pbr'

On 11/27/2014 12:59 PM, Li Tianqing wrote: I write a module to extend openstack. When install by python setup.py develop, it always blame this /usr/lib/python2.7/distutils/dist.py:267: UserWarning: Unknown distribution option: 'pbr' warnings.warn(msg) ... Processing dependencies for

[openstack-dev] [devstack] Devstack plugins and gate testing

Hi, With [1] merged, we now have people working on creating external plugins for devstack. I worry about use of arbitrary external locations as plugins for gate jobs. If a plugin is hosted externally (github, bitbucket, etc) we are introducing a whole host of problems when it is used as a gate

Re: [openstack-dev] [all] Testtools 1.7.0 may error if you installed it before reading this email

On 03/11/2015 08:10 AM, Robert Collins wrote: The wheel has been removed from PyPI and anyone installing testtools 1.7.0 now will install from source which works fine. I noticed the centos7 job failed with the source version. The failing job was [1] where the back-trace looks like ~45 songs on

Re: [openstack-dev] [swift] swift memory usage in centos7 devstack jobs

On 03/27/2015 08:47 PM, Alan Pevec wrote: But how come that same recent pyOpenSSL doesn't consume more memory on Ubuntu? Just to loop back on the final status of this ... pyOpenSSL 0.14 does seem to use about an order of magnitude more memory than 0.13 (2mb - 20mb). For details see [1].

Re: [openstack-dev] [swift] swift memory usage in centos7 devstack jobs

On 03/26/2015 04:07 PM, Ian Wienand wrote: See [1] for some more details; but the short story is that the various swift processes -- even just sitting around freshly installed from devstack before anything happens -- take up twice as much space on centos as ubuntu --- swift (% total system

Re: [openstack-dev] [swift] swift memory usage in centos7 devstack jobs

On 03/27/2015 08:47 PM, Alan Pevec wrote: But how come that same recent pyOpenSSL doesn't consume more memory on Ubuntu? Because we don't use it in CI; I believe the packaged version is installed before devstack runs on our ubuntu CI vm's. It's probably a dependency of some base package

Re: [openstack-dev] [devstack] Overriding settings file for devstack plugin

On 03/24/2015 03:17 PM, Deepak Shetty wrote: For eg: Look at [1] [1] https://github.com/stackforge/devstack-plugin-glusterfs/blob/master/devstack/settings I would like ability to change these while I use the enable_plugin apporach to setup devstack w/ GlusterFS per my local glusterfs setup

[openstack-dev] [swift] swift memory usage in centos7 devstack jobs

Hi, We've been having an issue with Centos 7 jobs and the host running out of memory. After some investigation; one likely angle seems to be the memory usage by swift. See [1] for some more details; but the short story is that the various swift processes -- even just sitting around freshly

Re: [openstack-dev] [devstack] Overriding settings file for devstack plugin

On 03/25/2015 09:28 PM, Sean Dague wrote: I would instead do the following: 1) CINDER_ENABLED_BACKENDS+=,glusterfs:glusterfs This is what I was about to suggest. I'd be willing to believe ordering could still get tangled depending on exactly what you want -- I think at that point best to

Re: [openstack-dev] [devstack] Overriding settings file for devstack plugin

On 03/23/2015 09:20 PM, Deepak Shetty wrote: Hi all, I was wondering if there was a neat way to override the settings file present in the devstack plugin stackforge project. For eg: stackforge/devstack-plugin-glusterfs I plan to use `enable_plugin glusterfs repo` in my local to setup

Re: [openstack-dev] The Evolution of core developer to maintainer?

On 04/02/2015 09:02 AM, Jeremy Stanley wrote: but since parties who don't understand our mostly non-hierarchical community can see those sets of access controls, they cling to them as a sign of importance and hierarchy of the people listed within. There is no hierarchy for submitting code --

Re: [openstack-dev] [OpenStack-Infra] Gerrit downtime and upgrade on Saturday 2015-05-09 at 1600 UTC

On 05/10/2015 05:20 AM, James E. Blair wrote: If you encounter any problems, please let us know here or in #openstack-infra on Freenode. One minor thing is that after login you're redirected to https://review.openstack.org//; (note double //, which then messes up various relative-links when

Re: [openstack-dev] [devstack] What's required to accept a new distro rlease?

On 05/15/2015 01:05 PM, Tony Breeds wrote: I'm wondering what are the requirements for accepting something like: -if [[ ! ${DISTRO} =~ (precise|trusty|7.0|wheezy|sid|testing|jessie|f20|f21|rhel7) ]]; then +if [[ ! ${DISTRO} =~

Re: [openstack-dev] [swift] swift memory usage in centos7 devstack jobs

Note; I haven't finished debugging the glusterfs job yet. This relates to the OOM that started happening on Centos after we moved to using as much pip-packaging as possible. glusterfs was still failing even before this. On 04/01/2015 07:58 PM, Deepak Shetty wrote: 1) So why did this happen on

Re: [openstack-dev] [all][infra][tc][ptl] Scaling up code review process (subdir cores)

On 06/03/2015 07:24 AM, Boris Pavlovic wrote: Really it's hard to find cores that understand whole project, but it's quite simple to find people that can maintain subsystems of project. We are made wise not by the recollection of our past, but by the responsibility for our future. -

Re: [openstack-dev] [puppet] [infra] issues with beaker/centos7 job

On 07/02/2015 11:52 AM, Emilien Macchi wrote: details. I tried to install deltarpm before, but it says : No Presto metadata available for rdo-release. So I looked into this with Gilles, and that error is a red-herring (it's just saying the rdo repos don't create the presto/deltarpm stuff); the

Re: [openstack-dev] Make libguestfs available on pypi

On 07/30/2015 04:55 AM, Kris G. Lindgren wrote: The following bug has already been created over a year ago [1], and it looks like most of the work on the libguestfs side is already done [2]. It seems something about a complaint of licensing per the bug report. I think best to follow up in

Re: [openstack-dev] [CI] No image was created after running nodepoold -d $DAEMON_ARGS

On 07/30/2015 01:51 PM, Ian Wienand wrote: Nothing jumps out Something I just thought of that has caused problems is check your users; I think running things by hand as root and then switching back to a unprivileged user can cause problems as the second run hits things it can't modify. -i

Re: [openstack-dev] [CI] No image was created after running nodepoold -d $DAEMON_ARGS

On 07/30/2015 12:34 PM, Xie, Xianshan wrote: DEBUG nodepool.NodePool: Finished node launch calculation INFO nodepool.DiskImageBuilderThread: Running disk-image-create ... So, nothing after this? Nothing jumps out; first thought was to check if disk-image-create is running and go from there.

Re: [openstack-dev] [all][infra] CI System is broken

On 07/29/2015 07:33 PM, Andreas Jaeger wrote: Currently Zuul is stuck and not processing any events at all, thus no jobs are checked or gated. I think whatever happened has happened again; if jhesketh is out it might be a few hours from this email before people with the right access are back

[openstack-dev] [devstack] package dependency installs after recent clean-ups

devstack maintainers, et al. If your CI is failing with missing packages (xml bindings failing to build, postgres bindings, etc), it may be due to some of the issues covered below. I believe some of the recent changes around letting pip build wheels and cleaning up some of the package

Re: [openstack-dev] [requirements] [infra] speeding up gate runs?

On 11/05/2015 01:43 AM, Matthew Thode wrote: python wheel repo could help maybe? So I think we've (i.e. greghaynes) got that mostly in place, we just got a bit side-tracked. [1] adds mirror slaves, that build the wheels using pypi-mirror [2], and then [3] adds the jobs. This should give us

Re: [openstack-dev] DevStack errors...

On 11/03/2015 10:51 AM, Thales wrote: I'm trying to get DevStack to work, but am getting errors. Is this a good list to ask questions for this? I can't seem to get answers anywhere I look. I tried the openstack list, but it kind of moves slow. Best to file a bug in launchpad, and *attach

Re: [openstack-dev] [all][heat] Which repo to use in docs -- git.openstack.org or github.com?

On 10/21/2015 04:20 AM, Christopher Aedo wrote: On the other hand, the fact that github renders the README nicely (including images) leads to a much more inviting first impression. I think it's nice to just have a standard docs target, even if it just includes the README; [1] is an example.

Re: [openstack-dev] [infra] Upgrade to Gerrit 2.11

On 10/14/2015 11:08 AM, Zaro wrote: We are soliciting feedback so please let us know what you think. Since you asked :) Mostly it's just different which is fine. Two things I noticed when playing around, shown in [1] When reviewing, the order "-1 0 +1" is kind of counter-intuitive to the

Re: [openstack-dev] [nova][infra] Getting a bleeding edge libvirt gate job running

On 11/18/2015 06:10 AM, Markus Zoeller wrote: This was a trigger to see if we can create a gate job which utilizes the latest, bleeding edge, version of libvirt to test such features. * Is already someone working on something like that and I missed it? I believe the closest we have got is

Re: [openstack-dev] [murano] Fix order of arguments in assertEqual

On 09/24/2015 08:18 PM, Andrey Kurilin wrote: I agree that wrong order of arguments misleads while debugging errors, BUT how we can prevent regression? Spell it out and use keyword args? assertEqual(expected="foo", observed=...) is pretty hard to mess up -i

Re: [openstack-dev] [TripleO][DIB] diskimage-builder and python 2/3 compatibility

On 12/09/2015 07:15 AM, Gregory Haynes wrote: > We ran in to a couple issues adding Fedora 23 support to > diskimage-builder caused by python2 not being installed by default. > This can be solved pretty easily by installing python2, but given that > this is eventually where all our supported

Re: [openstack-dev] [devstack][QA] Changing logging format to match documented defaults

On 12/23/2015 05:55 AM, Ronald Bradford wrote: > I have observed that devstack uses custom logging formatting that > differs from the documented defaults. An example is for nova. which > is defined in [1] The original point mentioned there of using "*_name" for extra verbosity still seems

Re: [openstack-dev] [devstack] How to source openrc?

On 11/23/2015 03:17 PM, Wilence Yao wrote: > source openrc admin admin > openrc:90: unknown condition: -v I'm pretty sure you're using zsh -- we only support bash (stack.sh checks for bash, maybe we should add that to openrc) Anyway, you can probably follow [1] to source it; other things might

Re: [openstack-dev] [TripleO] [diskimage-builder] Howto refactor?

On 06/01/2016 02:10 PM, Andre Florath wrote: My long term goal is, to add some functionality to the DIB's block device layer, like to be able to use multiple partitions, logical volumes and mount points. Some thoughts... There's great specific info in the readme's of the changes you posted

Re: [openstack-dev] [devstack] pip 8 no longer over-installs system packages [was: Gate failure]

On 01/20/2016 04:14 PM, Ian Wienand wrote: On 01/20/2016 12:53 PM, Robert Collins wrote: I suspect we'll see fallout in unit tests too, once new images are built. If the images can build ... yeah, dib is not happy about this either Just removing the directory as pip used to do has been

Re: [openstack-dev] [devstack] pip 8 no longer over-installs system packages [was: Gate failure]

On 01/20/2016 12:53 PM, Robert Collins wrote: I suspect we'll see fallout in unit tests too, once new images are built. If the images can build ... This was marked as deprecated, I understand, but the removal is very unfortunate [1] considering it's really just a shoot-yourself-in-the-foot

Re: [openstack-dev] [all] pip 8 no longer over-installs system packages [was: Gate failure]

On 01/20/2016 06:21 PM, Andreas Jaeger wrote: > Now docs, pep8, and python27 are broken as well here: > https://review.openstack.org/#/c/268687/ Ok, so this is a weird one. On trusty, argparse is sort of in, and sort of out of the virtualenv. I think it has to do with [1] ---

[openstack-dev] [infra] Jobs failing : "No matching distribution found for "

So it seems the just released pip 8.1.2 has brought in a new version of setuptools with it, which creates canonical names per [1] by replacing "." with "-". The upshot is that pip is now looking for the wrong name on our local mirrors. e.g. --- $ pip --version pip 8.1.2 from

[openstack-dev] [tripleo][releases] Remove diskimage-builder from releases

Hi, diskimage-builder has fallen under the "centralised release tagging" mechanism [1], presumably because it is under tripleo. I'd like to propose that we don't do that. Firstly, dib doesn't have any branches to manage. dib's other main function is as part of the daily CI image builds. This

Re: [openstack-dev] [tripleo][releases] Remove diskimage-builder from releases

On 04/20/2016 06:09 AM, Fox, Kevin M wrote: I've seen dib updated and broken things. I've seen dib elements updated and things broke (centos6 removal in particular hurt.) By the time it gets to a release, however, anything we've broken is already baked in. Any changes in there have already

Re: [openstack-dev] [tripleo][releases] Remove diskimage-builder from releases

On 04/20/2016 03:25 AM, Doug Hellmann wrote: It's not just about control, it's also about communication. One of the most frequent refrains we hear is "what is OpenStack", and one way we're trying to answer that is to publicize all of the things we release through releases.openstack.org. So for

Re: [openstack-dev] [all] create periodic-ci-reports mailing-list

On 04/14/2016 03:22 AM, Jeremy Stanley wrote: Mentioned in IRC as well, but would an RSS/ATOM feed be a good compromise between active notification and focus on the dashboard as an entry point to researching job failures? For myself, simply ordering by date on the log page as per [1] would

Re: [openstack-dev] [infra][neutron] - best way to load 8021q kernel module into cirros

On 08/09/2016 02:10 AM, Jeremy Stanley wrote: I haven't personally tested the CirrOS build instructions, but have a feeling writing a diskimage-builder element wrapper for that wouldn't be particularly challenging. I'm not exactly sure it fits that well into dib; it seems like "bundle" has it

Re: [openstack-dev] [ironic-pyhon-agent][DIB] IPA failed to start on Ubuntu because of modprobe path

On 01/21/2017 09:31 PM, Moshe Levi wrote: Added ExecStartPre=/usr/sbin/modprobe vfat to the ironic-python-agent systemd script The problem is that modprobe location in Ubuntu / sbin/modprobe (the /usr/sbin/modprobe vfat works for redhat) I have opened this bug in Launchpad >

[openstack-dev] [all] Moving coverage jobs to check queue

Hello, In a prior thread we discussed moving coverage jobs from "post" jobs to the check queue [1]. Firstly, if you have no idea what I'm talking about, the coverage jobs run the unit tests under the coverage tool [2] and produce some output like [3] which identifies which parts of the code have

[openstack-dev] [dib] diskimage-builder v2 RC1 release; request for test

Hi diskimage-builder has been working on a feature/v2 branch incorporating some largely internal changes to the way it finds and calls elements, enhancements to partitioning and removal of some long-deprecated elements. We have just tagged 2.0.0rc1 and are requesting testing by interested

Re: [openstack-dev] [infra][Neutron] Running out of memory on gate for linux bridge job

On 01/14/2017 02:48 AM, Jakub Libosvar wrote: > recently I noticed we got oom-killer in action in one of our jobs [1]. > Any other ideas? I spent quite a while chasing down similar things with centos a while ago. I do have some ideas :) The symptom is probably that mysql gets chosen by the

Re: [openstack-dev] [all] PBR 2.0.0 release *may* cause gate failures

On 03/02/2017 01:13 AM, Doug Hellmann wrote: Tony identified caps in 5 OpenStack community projects (see [1]) as well as powervm and python-jsonpath-rw-ext. Pull requests to those other projects are linked from the bug [2]. [1] https://review.openstack.org/#/q/topic:bug/1668848 Am I nuts or

[openstack-dev] [release][diskimage-builder] v2 branch request

Hi, diskimage-builder would like to request a feature/v2 branch. We have a backlog of changes that we would like to give more extensive testing together before we merge to master [1]. We've discussed this in our meeting, and we feel like series-independent releases in general work well for us,

[openstack-dev] Gerrit downtime on Tuesday 2016-11-22 at 21:00UTC

Hi everyone, On Tuesday, November 22nd from approximately 21:00 through 21:30 UTC Gerrit will be unavailable while we complete project renames. Currently, we plan on renaming the following projects: rsc -> valence Existing reviews, project watches, etc, for these projects will all be carried

[openstack-dev] [gerrit] dell-afc-ci disabled but constantly connecting to gerrit

Hi, There's a zombie account "dell-afc-ci" which was disabled in April [1] that has been trying to connect to gerrit every 5 seconds since ... [2016-12-15 06:27:44,223 +] 946a4473 dell-afc-ci - AUTH FAILURE FROM 143.166.116.138 inactive-account [2016-12-15 06:27:49,544 +] 9497a4aa

[openstack-dev] Gerrit downtime on Thursday 2017-01-12 at 20:00 UTC

Hi everyone, On Thursday, January 12th from approximately 20:00 through 20:30 UTC Gerrit will be unavailable while we complete project renames. Currently, we plan on renaming the following projects: Nomad -> Cyborg - openstack/nomad -> openstack/cyborg Nimble -> Mogan - openstack/nimble

Re: [openstack-dev] [cinder] [third-party][ci] devstack failures

On 12/05/2016 04:43 PM, Apoorva Deshpande wrote: > [1] http://openstack-ci.tintri.com/tintri/refs-changes-23-405223-4/ This is failing at 2016-12-05 01:19:17.356 | + functions-common:git_timed:598 : timeout -s SIGINT 0 git clone git://git.openstack.org/openstack/horizon.git

Re: [openstack-dev] Your next semi weekly gate status report

On 03/28/2017 08:57 AM, Clark Boylan wrote: 1. Libvirt crashes: http://status.openstack.org/elastic-recheck/#1643911 and http://status.openstack.org/elastic-recheck/#1646779 Libvirt is randomly crashing during the job which causes things to fail (for obvious reasons). To address this will

Re: [openstack-dev] [dib] diskimage-builder v2 RC1 release; request for test

On 03/21/2017 03:10 AM, Mikhail Medvedev wrote: On Fri, Mar 17, 2017 at 3:23 PM, Andre Florath wrote: Submitted the bug https://bugs.launchpad.net/diskimage-builder/+bug/1674402 Thanks; some updates there. Would adding a third-party CI job help? I can put together a

Re: [openstack-dev] [dib][heat] dib-utils/dib-run-parts/dib v2 concern

On 03/16/2017 08:22 AM, Ben Nemec wrote: Anyway, I don't know that anything is broken at the moment since I believe dib-run-parts was brought over unchanged, but the retirement of dib-utils was proposed in https://review.openstack.org/#/c/445617 and I would like to resolve this question before

Re: [openstack-dev] [dib][heat] dib-utils/dib-run-parts/dib v2 concern

On 03/17/2017 03:46 AM, Steven Hardy wrote: > (undercloud) [stack@undercloud ~]$ rpm -qf /usr/bin/dib-run-parts > dib-utils-0.0.11-1.el7.noarch > (undercloud) [stack@undercloud ~]$ rpm -qf /bin/dib-run-parts > dib-utils-0.0.11-1.el7.noarch /bin is a link to /usr/bin? So I think this is the same

Re: [openstack-dev] [infra] Stop enabling EPEL mirror by default

On 04/05/2017 03:02 AM, Paul Belanger wrote: > Recently we've been running into some issues keeping our EPEL mirror > properly sync'd. We are working to fix this, however we'd also like > to do the following: > Stop enabling EPEL mirror by default > https://review.openstack.org/#/c/453222/ >

Re: [openstack-dev] [all] Switching gate testing to use Ubuntu Cloud Archive

On 04/04/2017 09:06 AM, Clark Boylan wrote: > I have pushed a change to devstack [3] to enable using UCA which pulls > in new Libvirt and mostly seems to work. I think we should consider > switching to UCA as this may fix our Libvirt problems and if it doesn't, > we will be closer to a version of

Re: [openstack-dev] [heat][infra] Help needed! high gate failure rate

On 08/10/2017 06:18 PM, Rico Lin wrote: > We're facing a high failure rate in Heat's gates [1], four of our gate > suffering with fail rate from 6 to near 20% in 14 days. which makes most of > our patch stuck with the gate. There have been a confluence of things causing some problems recently.

Re: [openstack-dev] [all][infra]Plan to support Python 3.6 ?

On 08/09/2017 11:25 PM, ChangBo Guo wrote: We received Python 3.6 related Bug recently [1][2]. That let me think what's the plan to support Python 3.6 for OpenStack in the future. Python 3.6 was released on December 23, 2016, has some different behaviors from Python 3.5[3]. talked with cdent

[openstack-dev] [infra][devstack] DIB builds after mysql.qcow2 removal

Hi, The removal of the mysql.qcow2 image [1] had a flow-on effect noticed first by Paul in [2] that the tools/image_list.sh "sanity" check was not updated, leading to DIB builds failing in a most unhelpful way as it tries to cache the images for CI builds. So while [2] fixes the problem; one

Re: [openstack-dev] [infra][devstack] DIB builds after mysql.qcow2 removal

On 07/18/2017 10:01 AM, Tony Breeds wrote: It wasn't forgotten as suchi, there are jobs still using it/them. If keeping the branches around cuases bigger probelsm then EOLing them is fine. I'll try to generate a list of the affected projects/jobs and turn them off. Thanks; yeah this was

[openstack-dev] [infra][nova] Corrupt nova-specs repo

Hi, Unfortunately it seems the nova-specs repo has undergone some corruption, currently manifesting itself in an inability to be pushed to github for replication. Upon examination, it seems there's a problem with a symlink and probably jgit messing things up making duplicate files. I have filed

[openstack-dev] [infra] openstack-ubuntu-testing-bot -- please turn off

Hi, If you know of someone in control of whatever is trying to use this account, running on 91.189.91.27 (a canonical IP), can you please turn it off. It's in a tight loop failing to connect to gerrit, which probably isn't good for either end :) -i

Re: [openstack-dev] diskimage builder works for trusty but not for xenial

On 06/21/2017 04:44 PM, Ignazio Cassano wrote: * Connection #0 to host cloud-images.ubuntu.com left intact Downloaded and cached http://cloud-images.ubuntu.com/xenial/current/xenial-server-cloudimg-amd64-root.tar.gz, having forced upstream caches to revalidate

[openstack-dev] [diskimage-builder] Restarting bi-weekly meeting

Hi, We've let this meeting [1] lapse, to our communications detriment. I will restart it, starting next week [2]. Of course agenda items are welcome, otherwise we will use it as a session to make sure patches are moving in the right direction. If the matter is urgent, and not getting

[openstack-dev] [infra] shutting down pholio.openstack.org

Hello, We will be shutting down pholio.openstack.org in the next few days. As discussed at the last #infra meeting [1], in short, "the times they are a changin'" and the Pholio services have not been required. Of course the original deployment puppet, etc, remains (see [2]), so you may reach

Re: [openstack-dev] [devstack] Why do we apt-get install NEW files/debs/general at job time ?

On 09/20/2017 09:30 AM, David Moreau Simard wrote: At what point does it become beneficial to build more than one image per OS that is more aggressively tuned/optimized for a particular purpose ? ... and we can put -dsvm- in the jobs names to indicate it should run on these nodes :) Older

Re: [openstack-dev] [devstack] Why do we apt-get install NEW files/debs/general at job time ?

On 09/19/2017 11:03 PM, Jeremy Stanley wrote: On 2017-09-19 14:15:53 +0200 (+0200), Attila Fazekas wrote: [...] The jobs does 120..220 sec apt-get install and packages defined /files/debs/general are missing from the images before starting the job. Is the time spent at this stage mostly

Re: [openstack-dev] [DIB] DIB Meetings

On 10/06/2017 02:19 AM, Andreas Scheuring wrote: seems like there is some confusing information about the DIB meetings in the wiki [1]. The meeting is alternating between 15:00 and 20:00 UTC. But whenever the Text says 15:00 UTC, the link points to a 20:00 UTC worldclock site and vice versa.

Re: [openstack-dev] [all] Zuul v3 Rollout Update - devstack-gate issues edition

On 10/12/2017 04:28 PM, Ian Wienand wrote: - logs issues Should be behind us. The logs partition ran out of inodes, causing log upload failures. Pruning jobs should have rectified this. This time it's true :) But please think about this with your jobs, and don't upload hundreds of little

Re: [openstack-dev] [devstack] zuulv3 gate status; LIBS_FROM_GIT failures

On 09/29/2017 03:37 PM, Ian Wienand wrote: I'm not aware of issues other than these at this time Actually, that is not true. legacy-grenade-dsvm-neutron-multinode is also failing for unknown reasons. Any debugging would be helpful, thanks. -i

[openstack-dev] [devstack] zuulv3 gate status; LIBS_FROM_GIT failures

Hi, There's a few issues with devstack and the new zuulv3 environment LIBS_FROM_GIT is broken due to the new repos not having a remote setup, meaning "pip freeze" doesn't give us useful output. [1] just disables the test as a quick fix for this; [2] is a possible real fix but should be tried a

[openstack-dev] [all] Python 3.6 testing is available on Fedora 26 nodes

Hello, In a recent discussion [1] I mentioned we could, in theory, use Fedora 26 for Python 3.6 testing (3.6.2, to be exact). After a few offline queries we have put theory into practice, sorted out remaining issues and things are working. For unit testing (tox), you can use the

[openstack-dev] [diskimage-builder] Does anyone use "fedora" target?

Hi, The "fedora" element -- the one that downloads the upstream .qcow2 and re-packages it -- is currently broken as the links we use have disappeared [1]. Even allowing for this, it's still broken with some changes to the kernel install scripts [2]. AFAICT, the only thing noticing this is our

Re: [openstack-dev] [all] Zuul v3 Rollout Update - devstack-gate issues edition

There are still significant issues - logs issues Should be behind us. The logs partition ran out of inodes, causing log upload failures. Pruning jobs should have rectified this. - Ubuntu package issues You may notice a range of issues with Ubuntu packages. The root cause is that our mirror

[openstack-dev] [infra][all] Removal of packages from bindep-fallback

Hello, Some time ago we started the process of moving towards projects being more explicit about thier binary dependencies using bindep [1] To facilitate the transition, we created a "fallback" set of dependencies [2] which are installed when a project does not specifiy it's own bindep

Re: [openstack-dev] Building Openstack Trove Images

On 11/07/2017 05:40 PM, Ritesh Vishwakarma wrote: > as the *dib-lint* file is there instead of the mentioned > *disk-image-create *and when executed just verifies the other > elements. Those instructions unfortunately look out of date for master diskimage-builder. I will try to get a minute to

Re: [openstack-dev] [infra] Short gerrit / zuul outage 2017-10-20 20:00UTC

On 10/20/2017 03:46 PM, Ian Wienand wrote: We plan a short outage (<30 minutes) of gerrit and zuul on 2017-10-20 20:00UTC to facilitate project rename requests. Note this has been postponed to a future (TBD) date Thanks,

[openstack-dev] [infra] Short gerrit / zuul outage 2017-10-20 20:00UTC

Hello, We plan a short outage (<30 minutes) of gerrit and zuul on 2017-10-20 20:00UTC to facilitate project rename requests. In flight jobs should be restarted, but if something does go missing a "recheck" comment will work. Thanks, -i

Re: [openstack-dev] Fwd: [Distutils][pbr][devstack][qa] Announcement: Pip 10 is coming, and will move all internal APIs

On 10/22/2017 12:18 AM, Jeremy Stanley wrote: Right, on Debian/Ubuntu it's not too terrible (cloud-init's dependencies are usually the biggest issue there and we manage to avoid them by building our own images with no cloud-init), but on Red Hat derivatives there are a lot of deep operating

  1   2   >