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 c
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 t
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 de
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 th
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 the
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
On 09/09/2014 08:24 AM, Joe Gordon wrote:
1) Should we explicitly set the number of workers that services use in
devstack? Why have so many workers in a small all-in-one environment? What
is the right balance here?
There is a review out for that [1].
Devstack has a switch for everything, and t
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 i
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 fi
On 12/02/2014 04:25 AM, Ben Nemec wrote:
1) A specific reason SHELLOPTS can't be used.
IMO leave this alone as it changes global behaviour at a low-level and
that is a vector for unintended side-effects. Some thoughts:
- We don't want tracing output of various well-known scripts that
might
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 list
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 b
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 it
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] http://docs.openstack.org/developer/d
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
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
j
Hi,
To summarize recent discussions, nobody is opposed in general to
having Fedora / Centos included in the gate. However, it raises a
number of "big" questions : which job(s) to run on Fedora, where does
the quota for extra jobs come from, how do we get the job on multiple
providers, how stable
Hi,
Rather than adding more MAGIC_VARIABLE="foo" variables to devstack
that really only add lines to config files, I've been asking people to
add them to local.conf and provide additional corresponding
documentation if required.
However increased use has exposed some issues, now covered by sever
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 tak
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 d
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 ...
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, oslo.co
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 give
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 go
On Mon, Aug 05, 2013 at 03:37:24PM -0700, Jay Buffington wrote:
> I used Anvil for the first three months, but it required constant
> updating of dependency versions and it didn't support quantum.
What do you mean by "updating" here? The rpm packages being updated
causing a lot of churn, or some
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 unreliab
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
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 t
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. Th
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 the
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 wh
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 dependenci
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 p
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
br
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 distro
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
...
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
make
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 m
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
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
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 /tmp/foo/lib/python
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 relevan
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 ope
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
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]
---
(test)ubuntu@trust
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
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. I
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
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 on
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
___
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 usu
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} =~
> (precise|trusty|vivid|7.0|wheezy|sid|testing|jessie|f20|f
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.
- Geor
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); t
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 o
On 03/12/2015 10:37 AM, Ian Wienand wrote:
> File "/tmp/easy_install-mV2rSm/unittest2-1.0.0/unittest2/case.py", line
> 16, in
> ImportError: cannot import name range
> Complete output from command python setup.py egg_info:
OK, so this suggests the version of &quo
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 ` in my local to setup
GlusterFS b
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 se
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 follo
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 inst
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
>
>
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 there,
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].
Thi
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
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 -- th
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
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
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 we
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 a
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
functional job on ppc64.
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 like
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 L
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/
>
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 attention
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
_
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 out
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
xenial-server-cloudimg-amd64-root.ta
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
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 comp
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 point
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.
The
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 in
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
'gate-{name}-pyt
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 C
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 while
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 hand
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
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
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.
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 i
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
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
_
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,
On 10/21/2017 07:14 AM, Clark Boylan wrote:
The current issue this change is facing can be seen at
http://logs.openstack.org/25/513825/4/check/legacy-tempest-dsvm-py35/c31deb2/logs/devstacklog.txt.gz#_2017-10-20_20_07_54_838.
The tl;dr is that for distutils installed packages (basically all the
d
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 syste
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 pa
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 dependenci
On 12/21/2017 02:51 AM, Afek, Ifat (Nokia - IL/Kfar Sava) wrote:
There is an open bug in launchpad about the new release of Networkx
2.0, that is backward incompatible with versions 1.x [1].
From diskimage-builder's POV, we can pretty much switch whenever
ready, just a matter of merging [2] aft
Hi,
So I guess since CentOS included libvirt 3.2 (7-1708, or around RHEL
7.4), it's been incompatible with libvirt-python requirements of 2.1.0
in newton [1] and 2.5.0 in ocata [2] (pike, at 3.5.0, works).
Do we want to do anything about this? I can think of several options
* bump the libvirt-p
On 01/12/2018 02:53 PM, Matthew Thode wrote:
First, about newton, it's dead (2017-10-11).
Yeah, there were a few opt-outs, which is why I think devstack still
runs it. Not worth a lot of effort.
Next, about ocata, it looks like it can support newer libvirt, but
just because a distro updated
1 - 100 of 129 matches
Mail list logo
