e notes [2], and the
complete log of all commits since Beaker 25.6 is also available [3].
[1] https://beaker-project.org/releases/
[2] https://beaker-project.org/docs/whats-new/release-26.html
[3]
https://git.beaker-project.org/cgit/beaker/log/?qt=range&q=beaker-25.6..beaker-26.0&
t;yum clean
expire-cache".
The harness repos remaining unsigned for now, as do the *-testing repos.
The server and client repos for Fedora are also still unsigned for now,
I am still working on this. At this stage it is more likely we will get
all packages into Fedora itself and remove thes
=1 in /etc/yum.repos.d/ you will need to change this back to
gpgcheck=0. Sorry for the inconvenience.
In future we want to get this signing process going again and we will be
looking at ways to enable that.
--
Dan Callaghan
Senior Software Engineer, Products & Technologies Operations
Red
e!
I just realised that we never announced the 24.4 maintenance release
when it was published back in September. Sorry for the oversight. The
release notes for that are in the usual place too:
https://beaker-project.org/docs/whats-new/release-24.html#beaker-24-4
--
Dan Callaghan
Senio
https://beaker-project.org/releases/
[2] https://beaker-project.org/docs/whats-new/release-24.html#beaker-24-5
[3]
https://git.beaker-project.org/cgit/beaker/log/?qt=range&q=beaker-24.4..beaker-24.5&showmsg=1
--
Dan Callaghan
Senior Software Engineer, Products & Technologies O
etable when we can expect to have
> you or someone on your team be available to comment on the patches?
I'll go through them again today, sorry.
--
Dan Callaghan
Senior Software Engineer, Products & Technologies Operations
Red Hat
sig
t get whatever Anaconda finds by itself, which is the
installation repo plus any add-ons it finds in .treeinfo. And they won't
be available after installation.
If the user wants the full complement of repos to be available during
and after installation, like a normal Beaker recipe would
the different filter options. It would
only be a meaningful test if you have also imported all the distros we
have in our labs. That's why beaker-devel is good for testing this kind
of thing, since it has the same set of distros imported as in
stage/prod.
--
Dan Callaghan
Senior Software
the menus. I think at Jeff Burke's request. :-) But we can define
a filter which matches everything *except* your new fake distro.
Essentially in inventory/group_vars/beaker we would put:
beaker_pxemenu_xml_filter: ''
--
Dan Callaghan
Senior
ng an entirely new compose each
time, whys not just register each one in Beaker separately?
Let's continue the discussion on the devel list (cc'ed) so others can
see. Coincidentally Anwesha has just started working on proper support
for "user-supplied distro trees" in
urrently derived from the lab mirror URL stored
in the distro library. It should be easy to tweak that to download from
elsewhere instead.
--
Dan Callaghan
Senior Software Engineer, Products & Technologies Operations
Red Hat
signature.asc
Description: PGP signature
___
t might be enough to just make Beaker skip the kickstart
generation (and hide the relevant bits of the UI that task about the
recipe installation) assuming that the initramfs will contain a harness
that can report back to Beaker.
--
Dan Callaghan
Senior Software Engi
07-25 18:06:40,987 __main__ INFO Populating tables with
> pre-defined values if necessary
> 2017-07-25 18:06:41,225 __main__ INFO Pre-defined values populated
> 2017-07-25 18:06:41,226 __main__ INFO Exiting
>
>
>
> SELECT * FROM alembic_version;
> +-+
> | versi
Gears.
The normal way to upgrade/downgrade the database schema on a Beaker
installation is using beaker-init (to upgrade) or
beaker-init --downgrade= (to downgrade).
If you're running from a git checkout with a database configured in
dev.cfg, you can just do something like:
cd Ser
s is probably a good one:
https://git.beaker-project.org/cgit/beaker/commit/?id=da355153e4583da4e3147a2f0daa2dcc54e64d84
op.add_column / op.drop_column are the ones you will want here too.
--
Dan Callaghan
Senior Software Engineer, Products & Technologies Operations
Red Hat
sign
"devices" to be
closer to the lshw tree model because it seems to be a good way of
generically describing a lot of different hardware. Not saying we need
to go full speed down this route right now -- but anything that brings
Beaker's model of devices closer to lshw&#x
;firmware"]')[0]
> +#create dictionary with key-values for version and date
> +SystemFirmware = dict(version = sysfwinfo.findtext('version'), date =
> sysfwinfo.findtext('date'))
> +#add to data
> +data['SystemFirmware'] =
happening is that when the tests are firing
up the server it is loading a different copy of widgets.py from
elsewhere. For example you are editing a git checkout but it is loading
from /usr/lib/python2.6/site-packages.
--
Dan Callaghan
Senior Software Engineer, Products & Technologies Opera
ages besides
those ones.
There is also no support for row versioning which could detect
concurrent modifications and give back a 409 (like Bugzilla's "mid-air
collision" error message).
--
Dan Callaghan
Senior Software Engineer, Products & Technologies Operati
ur question in general: by hassling me until I review the
patch on Gerrit. :-)
--
Dan Callaghan
Senior Software Engineer, Products & Technologies Operations
Red Hat
signature.asc
Description: PGP signature
___
Beaker-devel mailing li
Excerpts from Don Zickus's message of 2017-05-31 16:54 -04:00:
> On Tue, May 30, 2017 at 05:25:06PM +1000, Dan Callaghan wrote:
>
> Hi Dan,
>
> This is V2 of my patch. Things move farther along. But now I can't
> actually 'send_file'. It doesn't ret
cause you need some more thorough test coverage
(the HTTP API is tested separately from the web UI) -- having that is
a good thing of course, but it takes time to write. And then it adds
extra difficulty if you are dealing with a particularly badly designed
(or badly aged) piece of UI that needs
ols'),
> +('user_group', 'User Groups')],
> + default='system',
> + help_text = export_help_text)
> +exportform = HorizontalForm(
> +'export&
eaker-project.org/releases/
[2] https://beaker-project.org/docs/whats-new/release-24.html#beaker-24-3
[3]
https://git.beaker-project.org/cgit/beaker/log/?qt=range&q=beaker-24.2..beaker-24.3&showmsg=1
--
Dan Callaghan
Senior Software Engineer, Products & Technologies Operations
Red Ha
worry, although if Beaker is getting the name from .composeinfo
then the name in .treeinfo will not have any effect so it shouldn't
matter.
--
Dan Callaghan
Senior Software Engineer, Products & Technologies Operations
Red Hat
signature.asc
Description: PGP signature
__
e gets a copy.
Yes, will contact you off-list about this.
--
Dan Callaghan
Senior Software Engineer, Products & Technologies Operations
Red Hat
signature.asc
Description: PGP signature
___
Beaker-devel mailing list -- beaker-devel@lists.fedorahost
cept to start rewriting.
Now you can probably appreciate when people said "why does it take you
guys so long to churn out Beaker features? why haven't you done mine
yet?" it's not because the three of us were just sitting around
twiddling our thumbs. :-)
--
Dan Calla
Excerpts from Shawn Doherty's message of 2017-05-16 15:26 -04:00:
> -
ut it is far, far easier to just use the development server by doing cd
Server; ./run-server.sh from a git checkout. Your js changes will be
visible on every page refresh.
--
Dan Callaghan
Senior Software Engineer, Products & Technologies Operations
Red Hat
signature.asc
Description: PG
course you set a non-empty password for your MySQL "root"
account... right? :-)
--
Dan Callaghan
Senior Software Engineer, Products & Technologies Operations
Red Hat
signature.asc
Description: PGP signature
___
Beaker-devel mailing list -- bea
replace that with a Flask request handler (the functions decorated with
@app.route).
What you can't do is port half of a request handler and mix-and-match
CherryPy-related calls (that includes anything that is a TG widget) with
Flask-related calls, as you discovered in your origin
there are indeed some modern
alternatives like JSON columns in Postgres like Nick suggested. But that
is pretty far off. We are stuck on MySQL 5.1 for the foreseeable future
and migrating MySQL->Postgres is an even bigger task.
--
Dan Callaghan
Senior Software Engineer, Pro
frozen
in time.
In fact ideally the anamon script should really be kept alongside the
harness because, like the harness packages, it does really need to vary
depending on which distro is being installed...
--
Dan Callaghan
Senior Software Engineer, Products & Technologies Operation
range&q=beaker-24.1..beaker-24.2&showmsg=1
--
Dan Callaghan
Senior Software Engineer, Products & Technologies Operations
Red Hat
signature.asc
Description: PGP signature
___
Beaker-devel mailing list -- beaker-devel@lists.fedorahosted.o
https://git.beaker-project.org/cgit/beaker/log/?qt=range&q=beaker-24.0..beaker-24.1&showmsg=1
--
Dan Callaghan
Senior Software Engineer, Products & Technologies Operations
Red Hat
signature.asc
Description: PGP signature
___
Beaker-d
lable in the release notes [2].
[1] https://beaker-project.org/releases/
[2] https://beaker-project.org/docs/whats-new/release-23.html#beaker-23-3
--
Dan Callaghan
Senior Software Engineer, Products & Technologies Operations
Red Hat
signature.asc
Description: PGP
rlGetPrimaryArch/rlGetSecondaryArch
> BEAKERLIB_JOURNAL not defined in the environment
> x86_64
> > rlGetPrimaryArch
> :: [ 08:23:58 ] :: [ ERROR ] :: rlGetPrimaryArch: Concept of primary and
> secondary architectures is defined on RHEL only
> BEAKERLIB_JOURNAL not defined in the environm
repo
contains unsigned packages. The client repo is also unsigned but we will
work towards switching this over to be signed in future.
--
Dan Callaghan
Senior Software Engineer, Products & Technologies Operations
Red Hat
signature.asc
Description: PGP signature
___
ermissions just now, if you see any further
problems with these yum repos please hit reply.
--
Dan Callaghan
Senior Software Engineer, Products & Technologies Operations
Red Hat
signature.asc
Description: PGP signature
___
Beaker-devel maili
eaker-project.org/docs/whats-new/release-23.html#beaker-23-2
--
Dan Callaghan
Senior Software Engineer, Products & Technologies Operations
Red Hat
signature.asc
Description: PGP signature
___
Beaker-devel mailing list
beaker-devel@lists.fedorah
liminate the "importing" step
entirely, in favour of directly looking up trees in PDC.
In the short term could you do something like, make the Taskotron task
ssh to Beaker and invoke beaker-import? Or maybe trigger an Ansible
playbook (through the RBAC stuff) which invokes beaker-im
task, but that's
normally /distribution/install so it shouldn't happen there).
So that means we're not rescheduling aborted recipes, but suspiciously
aborted recipes.
--
Dan Callaghan
Senior Software Engineer, Products & Technologies Operati
.
[1] https://beaker-project.org/releases/
[2] https://bugzilla.redhat.com/show_bug.cgi?id=1295998
[3] https://beaker-project.org/docs/whats-new/release-22.html#beaker-22-1
[4]
https://git.beaker-project.org/cgit/beaker/log/?qt=range&q=beaker-22.0..beaker-22.1&showmsg=1
--
Dan Callaghan
Se
t go with it, because this layout for
"reviewed" checkboxes seems fairly natural and it works well in Gerrit
and we couldn't come up with any better alternative layouts for it.
--
Dan Callaghan
Senior Software Engineer, Products & Technologies Operations
Red Hat, Inc.
signat
Thanks for the feedback Jeff.
Excerpts from Jeffrey Burke's message of 2015-10-26 07:54 -04:00:
> On Sun, Oct 25, 2015 at 10:55 PM, Dan Callaghan wrote:
> > * The original design proposal for the job page improvements mentioned
> > allowing ack/nak/comment on recipes
.
[1] https://beaker-project.org/releases/
[2] https://beaker-project.org/docs/whats-new/release-21.html#beaker-21-1
[3]
https://git.beaker-project.org/cgit/beaker/log/?qt=range&q=beaker-21.0..beaker-21.1&showmsg=1
--
Dan Callaghan
Senior Software Engineer, Products & Technologies O
aive" which is equivalent to nack'ing a recipe
set, or "un-waive" to reverse it.
If you see any issues with the above, or if you think it might break
your workflows, please hit reply.
[1] https://beaker-project.org/dev/proposals/job-page-improvemen
For some time yesterday the SSL certificate for beaker-project.org was
expired. If you were trying to access anything there your browser/client
would (I hope!) have given you an SSL error.
I've deployed a new valid certificate this morning. Sorry for any
inconvenience.
--
Dan Call
r Jenkins.
For now, you can see the output of the script running each night here:
https://beaker-project.org/~dcallagh/gerritstats/
We can find a more permanent home for the graph in future if it turns
out to be useful.
--
Dan Callaghan
Senior Software Engineer, Products & Technologies
eaker-project.org/docs/whats-new/release-21.html
[3]
https://git.beaker-project.org/cgit/beaker/log/?qt=range&q=beaker-20.2..beaker-21.0&showmsg=1
--
Dan Callaghan
Senior Software Engineer, Products & Technologies Operations
Red Hat, Inc.
signature.asc
Descripti
w the
data. So far we've only done some smaller, less commonly used grids like
the activity grid.
The systems grid and jobs grid will be the hardest ones but we will
tackle them eventually. That would be a good time for us to consider
adding some extra functionality like the bulk edit
aker-20.1..beaker-20.2&showmsg=1
--
Dan Callaghan
Senior Software Engineer, Products & Technologies Operations
Red Hat, Inc.
signature.asc
Description: PGP signature
___
Beaker-devel mailing list
Beaker-devel@lists.fedor
you have access to those:
--
Dan Callaghan
Senior Software Engineer, Products & Technologies Operations
Red Hat, Inc.
signature.asc
Description: PGP signature
___
Beaker-devel mailing list
Beaker-devel@lists.fedorahosted.org
https://lists.f
will be your yum repo containing the Python 3.5
RPMs. Instead of SKIP_NOARCH you will want to populate the
SRPM_WHITELIST parameter based on the list of SRPMs from step 2, bearing
in mind that the whitelist is a list of globs matched against the entire
filename including .src.rpm extension
isting kickstart
templates that Beaker uses to generate kickstarts. It should just be
a matter of getting beaker-provision to find and configure the right
kernel+initramfs for network booting the Debian/Ubuntu installer.
https://help.ubuntu.com/community/KickstartCompatibility
--
Dan Callaghan
poorly performing parts of code while we are working
on regular patches.
--
Dan Callaghan
Senior Software Engineer, Products & Technologies Operations
Red Hat, Inc.
signature.asc
Description: PGP signature
___
Beaker-devel mailing list
Beake
Thanks, applied.
--
Dan Callaghan
Senior Software Engineer, Products & Technologies Operations
Red Hat, Inc.
signature.asc
Description: PGP signature
___
Beaker-devel mailing list
Beaker-devel@lists.fedorahosted.org
https://lists.fedorahosted
arch64
distro, which has never had a GA and usually the best thing we can do is
use the latest compose available.
Since this is really just a temporary measure I think an admin
configurable list with hardcoded default is an okay approach.
--
Dan Callaghan
Software Engineer, Products & Te
Excerpts from Matt Jia's message of 2015-05-07 08:38 +10:00:
>
> > - Original Message -
> > > From: "Dan Callaghan"
> > > To: "beaker-devel"
> > > Sent: Wednesday, May 6, 2015 3:48:16 PM
> > > Subject: Re: [Beaker-dev
administrators to replace the default list with a different one.
Good idea.
--
Dan Callaghan
Software Engineer, Products & Technologies Operations
Red Hat, Inc.
signature.asc
Description: PGP signature
___
Beaker-devel mailing list
Beaker-devel@l
efined list of OS majors matches then it
should just pick *anything* and we just hope it will work. That should
cover the RHEL-alikes.
--
Dan Callaghan
Software Engineer, Products & Technologies Operations
Red Hat, Inc.
signature.asc
Description: PGP signature
tallation may not have any trees with that tag. Therefore if
there are no trees in the family tagged RELEASED, it should just use the
latest available tree.
--
Dan Callaghan
Software Engineer, Products & Technologies Operations
Red Hat, Inc.
sign
using the ksmeta to actually pick a distro tree. I suspect the
implementation would actually be very messy.
I think having some hardcoded rules in Beaker is fine, if someone wants
to use a different distro they can always construct a job explicitly
(using bkr machine-test or workflow-simple or a
the status calculation so that if any task
is Aborted or Cancelled, the entire recipe is Aborted or Cancelled, and
thus the recipe set and job is Aborted or Cancelled too.
If you see any issues with this change in behaviour please bring it up
here and we can discuss.
--
Dan Callaghan
Software
h
lshw and I've scheduled them across the next couple of sprints, so that
we can finally have proper inventory scans on all RHEL releases
including RHEL7.
--
Dan Callaghan
Software Engineer, Products & Technologies Operations
Red Hat, Inc.
signature.asc
Description: PGP signatur
etailed list of all changes made since Beaker 19.3 is also
available [3].
[1] https://beaker-project.org/releases/
[2] https://beaker-project.org/docs/whats-new/release-20.html
[3]
https://git.beaker-project.org/cgit/beaker/log/?qt=range&q=beaker-19.3..beaker-20.0&showmsg=1
--
Dan Calla
to scratch on
x86_64 so that we can switch over it to completely -- but that's
a fairly low priority now that aarch64 and POWER8 are working.
Jeff, was there some particular fix/feature in the inventory data which
you were looking for?
--
Dan Callaghan
Software Engineer, Products &
> from the nightlies repository.
Would it make more sense for the image to have the latest beaker-client
preinstalled, and for us to run a Jenkins job which pushes a new Docker
image every time the package is updated?
--
Dan Callaghan
Software Engineer, Products & Technolog
Excerpts from Bill Peck's message of 2015-03-24 21:49 +10:00:
> On 03/23/2015 10:34 PM, Dan Callaghan wrote:
> > Thinking about it some more, I wonder if the best solution might be
> > to just make the Koji buildroots we are using be the RHEL7 GA
> > release,
>
>
Excerpts from Bill Peck's message of 2015-03-23 23:11 +10:00:
> On 03/23/2015 04:12 AM, Dan Callaghan wrote:
> > One small issue I just noticed with the RHEL7 builds of restraint.
> > They
> > require the latest selinux-policy, since they are built against the
>
rsion of selinux-policy is probably not in
any RHEL7 composes aside from the very newest ones.
I think we need to pre-build a policy module using the RHEL7.0 GA
selinux-policy and commit it to source, the way we did for beah. I will
look into it some more this week.
--
Dan Callaghan
S
beaker-devel,
we will announce it as a supported alternative harness.
--
Dan Callaghan
Software Engineer, Products & Technologies Operations
Red Hat, Inc.
signature.asc
Description: PGP signature
___
Beaker-devel mailing li
e tests and
> probably in
> some other manner that requires the defaults to be set in the mysql config,
> instead of
> what we are used to from the model :).
Indeed! You have found a bug :-) Filed:
https://bugzilla.redhat.com/show_bug.cgi?id=1197917
Workaround is to add th
ons to disable
nose's capturing: -s (--nocapture) disables stdout capturing,
--nologcapture disables log capturing. But nose already displays both of
those on failures so there is not really any reason to disable the
capturing, unless you suspect that some setup in a su
Thanks for the patch! Merged, will be in the next release.
Excerpts from Andrej Manduch's message of 2015-02-27 06:38 +10:00:
> When you have strange things in your ~/.basrc (like grep --color=always)
> then beaker autocompletion can produce wrong output.
> [...]
--
Dan Calla
m/show_bug.cgi?id=1124139
although it's not straigh-forward due to compatibility with the existing
/login redirect and form-based auth we have for the web UI.
--
Dan Callaghan
Software Engineer, Hosted & Shared Services
Red Hat, Inc.
___
Be
{'atom': 'http://www.w3.org/2005/Atom'})
https://git.beaker-project.org/cgit/beaker/tree/Client/src/bkr/client/commands/cmd_list_systems.py#n238
--
Dan Callaghan
Software Engineer, Hosted & Shared Services
Red Hat, Inc.
___
Beaker-devel mailing list
Beaker-devel@lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/beaker-devel
quot; where everyone with
> system policy management access can add and remove their own systems
> from that pool)
>
> I think it's also a valid use case for being able to clone an existing
> policy from an arbitrary pool when creating a new pool.
Yes these are both interest
modules will go away and the js
will be packaged as proper RPMs like everything else.
[1] https://bugzilla.redhat.com/show_bug.cgi?id=1151877
--
Dan Callaghan
Software Engineer, Hosted & Shared Services
Red Hat, Inc.
signature.asc
Description: PGP signature
___
Excerpts from Alexander Todorov's message of 2015-01-12 19:55 +10:00:
> На 12.01.2015 в 06:43, Dan Callaghan написа:
> >
> > We could add a way for *users* to override the snippets in their recipe
> > XML. Maybe an element like
> >
> >
> > .
can just do yum-builddep beaker.spec to install the dependencies and then
> execute Misc/rpmbuild.sh -bs to just build the SRPM and Misc/rpmbuild.sh -bb
> to
> build the RPMs.
On RHEL6, you will need RHEL6 Server + Optional as well as the Beaker
server repo from https://beaker-project.o
. Either --pool-policy='' which is
a bit awkward, or else a separate mutually exclusive option like
--use-custom-policy.
--
Dan Callaghan
Software Engineer, Hosted & Shared Services
Red Hat, Inc.
signature.asc
Description: PGP signature
_
-project.org/releases/
[2] https://beaker-project.org/docs/whats-new/release-19.html#beaker-19-2
--
Dan Callaghan
Software Engineer, Hosted & Shared Services
Red Hat, Inc.
signature.asc
Description: PGP signature
___
Beaker-devel mailing list
Beaker-d
rbitrary collection of systems which owners are free create for any
purpose (easy identification of systems, grouping geographically or to
reflect org chart, for ease of sharing policies, etc... or in a future
release, for making scheduling decisions).
--
Dan Callaghan
Software Engineer, Host
ystems free.
It would be easier to tackle after we have implemented the "event-driven
scheduler" idea [1] because then the queries will go from N × M in
a single query to just 1 × N.
[1] https://beaker-project.org/dev/proposals/event-driven-scheduler.html
--
Dan Callaghan
special treatment. A system would start off
in no pools, with a custom access policy containing only one rule (view
for everybody). That's what we have now.
Every new pool would start off with an access policy that is the same
(view for everybody, empty aside from that).
--
Dan Callaghan
ave now) or they can pick *one* of the
pools the system is in and the access policy will be inherited from that
pool.
--
Dan Callaghan
Software Engineer, Hosted & Shared Services
Red Hat, Inc.
signature.asc
Description: PGP signature
___
Beaker-de
what exactly you mean by "policy type"... but I really want to
avoid making policies into a first-class object.
Maybe my replies to some of the other questions in the thread will make
it clearer what I am suggesting.
--
Dan Callaghan
Software Engineer, Hosted & Shared Service
mplement the UI for creating pools and adding/removing systems, but the
scheduler features (host restrictions and ordering) would be left for
later.
--
Dan Callaghan
Software Engineer, Hosted & Shared Services
Red Hat, Inc.
signature.asc
Description: PGP signature
or partitions in particular: we have discussed
previously the idea of allowing raw kickstart commands inside the
element. I can't find an RFE for it though. Also, the raw
partition commands would be passed straight through to the kickstart,
not treated as a Jinja template.
Are there any other b
Excerpts from Alexander Todorov's message of 2015-01-06 22:17 +10:00:
> На 6.01.2015 в 07:47, Dan Callaghan написа:
> > This is one of the "distro feature variables" already mentioned: end. It
> > expands to %end if supported or else empty string. In the server
>
ecipe page (similar in scale to the system page
improvements in Beaker 19). Please take a look and send any feedback to
the list.
--
Dan Callaghan
Software Engineer, Hosted & Shared Services
Red Hat, Inc.
signature.asc
Description: PGP signature
__
variables" already mentioned: end. It
expands to %end if supported or else empty string. In the server
templates we use it like this:
%post
something
{{ end }}
--
Dan Callaghan
Software Engineer, Hosted & Shared Services
Red Hat, Inc.
_
Excerpts from Nick Coghlan's message of 2015-01-06 11:55 +10:00:
> - Original Message -
> > From: "Alexander Todorov"
> > Additionally Dan Callaghan commented on Gerrit:
> > >
> > > Yes it sounds like this is a good time to re-think the tem
istro
plus all Beaker dependencies installed? Then we can avoid the first step
of build_base_image.sh. You could call the images
beaker-development-fedora-21, beaker-development-rhel-6,
beaker-development-rhel-7. Can we register a namespace for Beaker on the
docker.io registry somehow?
--
Dan C
to wish everyone a happy new year from the
Beaker team. See you in 2015!
[1] https://beaker-project.org/releases/
[2] https://beaker-project.org/docs/whats-new/release-19.html#beaker-19-1
--
Dan Callaghan
Software Engineer, Hosted & Shared Services
Red Hat, Inc.
signature.asc
Description:
we will need to work out.
We have not been doing a very good job of it with lshw so far.
--
Dan Callaghan
Software Engineer, Hosted & Shared Services
Red Hat, Inc.
signature.asc
Description: PGP signature
___
Beaker-devel mailing list
Beaker-devel@
It turned out to be an IPv6 problem. Every HTTP request from LC ->
server is attempting IPv6 first, but that times out after a while, then
it falls back to IPv4 which works.
I have a ticket open.
--
Dan Callaghan
Software Engineer, Hosted & Shared Services
Red Hat, Inc.
signat
ral minutes for things that should be
instantaneous. Not sure yet of the cause, I am investigating.
Thanks for taking the time to test and report this Jeff!
--
Dan Callaghan
Software Engineer, Hosted & Shared Services
Red Hat, Inc.
signature.asc
Description: PGP signature
_
ystem page itself, when you were
using it? Click a button, and it takes an entire minute for the request
to come back?
Or was it just on the scheduler side? You submitted a job with reserve
workflow and it took a minute for the job to be started?
--
Dan Callaghan
Software Engineer, Hosted &
1 - 100 of 265 matches
Mail list logo
