Ask Your Question

fungi's profile - activity

2019-07-01 07:00:00 -0500 commented answer fatal: unable to access '': Could not resolve host:

Do you use this machine for anything else? It really sounds like you haven't configured any DNS resolvers for it yet, or have set it to use resolvers you're unable to reach. How you configure your machine for DNS resolution will vary depending on your operating system and how it does network config.

2019-06-28 06:50:13 -0500 answered a question fatal: unable to access '': Could not resolve host:

This looks like a problem with name resolution on your machine. It's saying it can't find the name "" in DNS, but it's resolving for me with no problem. Do you have trouble cloning Git repositories from anywhere else? You could try git clone instead, for example (the URL you've been trying is an old redirect maintained for compatibility with the previous place that repository was hosted).

2019-06-13 03:43:59 -0500 received badge  Good Answer (source)
2019-06-04 19:45:57 -0500 received badge  Nice Answer (source)
2019-06-04 09:53:38 -0500 received badge  Necromancer (source)
2019-06-03 11:42:27 -0500 answered a question Is there a mentoring program for OpenStack?

See for information on the current mentoring programs in the community.

2019-03-11 09:15:29 -0500 commented answer Is accessing metadata of other VMs disallowed

I agree, the suggestion in that document is misdirected at service users when it should have been a suggestion for deployers. If it's an environment under your control, you can mitigate request spoofing by disabling the metadata service entirely and only making configdrive available to your users.

2019-03-07 10:01:06 -0500 answered a question Is accessing metadata of other VMs disallowed

See for some caveats around this, but in general the assumption is that if instances are unable to spoof their metadata API queries and/or listen to the connections between the Nova metadata service and other instances, then you can probably trust it to be confidential. The reason it's hard to say this definitively is that securing access to metadata is more up to local deployment technology choices outside the sphere of any OpenStack software's control to assure. If you can disable the metadata service and switch to configdrive in your deployment (as mentioned in the OSSN), that also may provide better mitigation of these risks.

It also warrants pointing out that instance metadata was never intended for communicating sensitive information in the first place, so treating it as if it were is not officially recommended.

2018-11-21 13:11:57 -0500 commented answer How to use AND in logstash queries?

I think it's closer to 10 days? But yes, the Kibana interface allows you to select longer timeframes than we keep data. I wonder if that's configurable...

2018-11-21 13:10:11 -0500 commented question How to use AND in logstash queries?

Per subsequent IRC discussion in #openstack-infra your syntax looks fine but you were querying for patterns which haven't been seen as recently as the data retention in the ES cluster so that's why there were no results.

2018-11-21 08:23:23 -0500 commented question How to use AND in logstash queries?

Can you link to a job log which you expect this query to match? Searching the past week for even just message:"connect to mirror" turns up 0 lines.

2018-09-26 17:08:48 -0500 answered a question Cannot be added as a reviewer on gerrit

This was raised and shortly solved the same day in #openstack-infra on the Freenode IRC network:

The issue turned out to be multiple Gerrit accounts for the same E-mail address (the most common reason for this sort of error).

2018-07-26 10:54:40 -0500 commented question What are the magic comments that I can use on OpenStack gerrit for rechecking jobs?

The OpenStack Project Infrastructure team doesn't really monitor questions posted to this site. More appropriate venues are the mailing list or #openstack-infra channel on the Freenode IRC network.

2018-07-26 10:54:18 -0500 answered a question What are the magic comments that I can use on OpenStack gerrit for rechecking jobs?

For the service reporting to its "check" pipeline triggers are configured at and as you can see only responds to the string "recheck" in review comments. The request to allow rechecking specific jobs comes up fairly frequently, and is intentionally not implemented because it significantly increases the risks of merging nondeterministic bugs through what I liken to picking a pin-and-tumbler lock mechanism. If you have 10 jobs and your change introduces a bug which causes each of them to fail 20% of the time, then you'd need to recheck it ~10 times on average before you could get that change to register a passing check result. If you could selectively recheck only the jobs which fail, the passing result would significantly misrepresent the stability of that change. Introducing the ability to do so in the gate pipeline would be even worse still.

Options have been discussed for the ability to selectively rerun jobs without causing them to affect the verify vote on the change in question, though nobody has stepped forward to implement the support which would be required for this in the Zuul code base.

2018-02-13 14:45:40 -0500 commented answer tox errors when running nova scheduling unit tests

Glad this helped! Also I see that nova's bindep.txt is missing libpcre3-dev (a regression introduced last month when whereto was added to test-requirements.txt to improve docs build validation), so I've proposed to hopefully get it included.

2018-02-13 10:57:28 -0500 answered a question tox errors when running nova scheduling unit tests

That output is telling you that the detailed error can be found in a file named /home/mnm13/nova/.tox/py35/log/py35-1.log and without knowing what's in there it's hard to give you a good answer. My guess, since it's pip installing dependencies into a virtualenv which failed, is that you're probably missing one or more library header dependencies which will need to be installed as system packages before pip will be able to build some of the required sdists. Running this should tell you what specific system packages you're missing for a working nova development environment:

tox -e bindep

Note that this is basically what also tells you to do.

2017-09-26 08:08:05 -0500 commented question Is the OpenStack community app catalog dead?

I've cleaned up the stray DNS record for and attempted to make the warning at the top of that wiki page clearer. Hopefully that helps.

2017-08-08 17:24:07 -0500 answered a question Problem accessing

There seems to be some problem with a (observed small) subset of Ubuntu One OpenIDs and the OpenID plugin we have in our Mediawiki deployment. It's tough to debug, and at this point we're hoping it goes away when we switch OpenID providers to in the near future.

2017-08-08 17:16:40 -0500 commented question "Cannot store contact Information" when updating info in OpenStack gerrit

This question is obsolete now:

2017-08-08 17:14:55 -0500 commented answer Does the company need to be a member of the foundation in order for employees to contribute code on behalf of the company?

Note that it is no longer necessary to join the foundation as an individual member to submit code, though you currently do still need to agree to the ICLA in Gerrit:

2017-08-08 17:04:24 -0500 received badge  Organizer (source)
2017-08-08 16:58:07 -0500 commented question Why am I getting an error message about the ICLA requiring contact information when trying to submit patches for review?

This question is obsolete now:

2017-08-08 16:57:15 -0500 commented question Is it a problem if I don't fill in all the contact information on Gerrit?

This question is obsolete now:

2017-08-08 16:56:18 -0500 commented question Why do I need to provide contact information when signing the CLA?

This question is obsolete now:

2017-08-08 16:54:22 -0500 commented question Why are contact fields in Gerrit blank after I provided them?

This question is obsolete now:

2017-04-04 09:48:39 -0500 answered a question pip-missing-reqs fails

That tox env for pip-missing-reqs is not exercised in the OpenStack CI system and so has bit-rotted. It looks like the error reported above was solved by after the tool was renamed, but nova's tox.ini was never updated to use the new package name. I've submitted to update the tox.ini in nova's master branch to install pip_check_reqs now instead of pip_missing_reqs.

2016-07-27 11:26:24 -0500 received badge  Necromancer (source)
2016-07-27 11:06:58 -0500 answered a question unable to login to with my openstack id

New account creation (which happens the first time you attempt to authenticate to via the Launchpad SSO OpenID) was disabled on February 29, 2016 to help us combat a serious uptick in spam volume. We've been working on improving some of our spam mitigation in the wiki (there's a lot more still to come), and it's reached the point where we were able to safely reenable new account creation on July 20.

We have still disabled all new file uploads since our current captcha extension doesn't guard that function, but with that in place the remaining spammers which show up are few enough (a dozen or so a day) that our wiki admins are able to keep on top of blocking them and cleaning up their mess.

2016-05-19 22:25:34 -0500 commented answer tox -epy34 errors

This at least matches the version of Python 3.4 we're using on Ubuntu 14.04 LTS in the official OpenStack CI, so it's unlikely to be a behavior specific to your version of the interpreter.

2016-05-19 11:35:10 -0500 commented answer tox -epy34 errors

I asked which version of Python 3.4 you have installed, since tox -e py34 uses Python 3.4.x not Python 2.7.x.

2016-05-18 09:32:31 -0500 answered a question tox -epy34 errors

We run official CI tests of horizon changes on Ubuntu 14.04 at the moment, and don't see that error. For example, this ran yesterday on a change which was subsequently merged:

When did this first start? Was it working for you up until recently? Also, where did you obtain your Python 3.4 interpreter for Ubuntu 12.04? As reflects, it was not officially packaged and distributed in Ubuntu until 14.04 LTS (Trusty Tahr).

Note that bugs in Horizon (including bugs in its unit tests) should be reported to the bug tracker instead:

2016-05-17 12:10:33 -0500 answered a question Zuul Installation

You'll have more luck asking on the mailing list or in the #openstack-infra channel on the Freenode IRC network.

2015-12-30 07:26:45 -0500 edited question "Cannot store contact Information" when updating info in OpenStack gerrit


While uploading my blueprint to gerrit, i am getting the following error to capture the contact information in my profile.

stack@ubuntu-47:~/openstack-specs/cinder-specs$ git config --list Kaligotla
stack@ubuntu-47:~/openstack-specs/cinder-specs$ git review

stack@ubuntu-47:~/openstack-specs/cinder-specs$ git review
**fatal: ICLA contributor agreement requires current contact information.
Please review your contact information:
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.**

When i login into the and try to update the contact information for my account, i get the following error.

Code Review - Error
Server Error
Cannot store contact Information

As a result i am unable to upload my blueprint docs into gerrit review system

I am not sure if I am doing something wrong here or if this is a bug. Is anyone else seeing it too?

Following is the screenshot of message.

image description

2015-11-10 11:22:20 -0500 commented answer "Cannot store contact Information" when updating info in OpenStack gerrit

Yes, is where all our other documentation on getting started with our community is supposed to send you. We don't really have a good solution for people who just turn up at our Gerrit instance and expect things to work out.

2015-08-03 23:52:03 -0500 received badge  Nice Answer (source)
2015-06-09 11:23:49 -0500 answered a question gerrit multiple projects in openstack with diffrent groups and users?

Maintainers of OpenStack community infrastructure systems such as do not watch for help requests, so you may have more luck E-mailing the mailing list or asking in the #openstack-infra channel on the Freenode IRC network.

2015-06-09 11:22:48 -0500 answered a question multiple email with zuul

Developers of OpenStack community infrastructure projects such as Zuul do not watch for help requests, so you may have more luck E-mailing the mailing list or asking in the #openstack-infra channel on the Freenode IRC network.

2015-05-14 17:22:04 -0500 commented answer Is there an Openstack patch for the Venom vuln? Do we need to patch qemu manually?

To clarify, you should obtain fixed versions of qemu from wherever you got your original versions of qemu. The OpenStack project doesn't write, maintain or distribute qemu itself.

2015-04-29 08:23:17 -0500 answered a question zuul trigger pep8 job when fail and put it in loop

Review your Zuul debug.log for confirmation, but I suspect you have configured a pipeline in your layout.yaml to trigger on all comments on a change rather than filtering for specific expressions in comments (or rather than only triggering on new patchsets). This can cause Zuul to react to events from Gerrit's stream for the comments it has left, and continually retrigger itself in an infinite loop.

Also, most of the Zuul developers and user community don't really pay attention to (it's more for OpenStack server software, not community infrastructure projects). I recommend the #openstack-infra IRC channel on Freenode or mailing list for Zuul help.

2015-04-27 10:30:48 -0500 answered a question Gerrit Code Review Email Notifications

It looks like you're asking a question about running Gerrit, but you have mistaken the OpenStack Q&A site for Gerrit configuration support.

Questions about how to run Gerrit should be directed to the Gerrit community. They can be found at!for... and in the #gerrit channel on the Freenode IRC network.

2015-04-17 09:48:31 -0500 commented question how to add smtp to from in zuul layout.yaml piplines for reports?

Most of the Zuul developers and user community don't really pay attention to (it's more for OpenStack server software, not community infrastructure projects). I recommend the #openstack-infra IRC channel on Freenode or mailing list for Zuul help.

2015-04-17 09:38:02 -0500 commented answer how to add smtp to from in zuul layout.yaml piplines for reports?

Well, yes the trigger in my example above is for a timer (periodic) trigger rather than a gerrit trigger. I was mostly including that pipeline definition to highlight a real-world example of the smtp reporter.

2015-04-16 08:09:56 -0500 commented question how to add smtp to from in zuul layout.yaml piplines for reports?

Does it trigger builds when you don't add the smtp reporter to that pipeline? What leads you to believe it's an SMTP reporter configuration problem?

2015-04-16 08:07:15 -0500 answered a question how to add smtp to from in zuul layout.yaml piplines for reports?

The Zuul documentation has a great example of its SMTP reporter, but if you need a real-life example have a look at the layout.yaml for and in the pipelines list you should see an entry for a periodic-stable pipeline like this:

  - name: periodic-stable
    description: Periodic checks of the stable branches.
    manager: IndependentPipelineManager
    source: gerrit
    precedence: low
        - time: '1 6 * * *'
        subject: 'Stable check of {change.project} failed'
2015-04-06 08:08:37 -0500 commented answer How to send a patch set to other author's commit?

Not adding a dependency, but updating a change (the one smaffulli linked in his answer). The critical part is that you need to make sure you use --amend when you commit so that you update the current commit rather than adding a new commit.

2015-03-31 09:37:21 -0500 answered a question Why third-party ci check is failed after request git review

It looks like your current patchset succeeds on all voting jobs in the official upstream CI (the one reporting as the "jenkins" account in Gerrit).

If the reviewers on your proposed change don't indicate a concern with any of the third-party CI results, then you probably don't need to worry about it either. Third-party CI systems reporting on your change may be broken in various ways from time to time, and the only ones deemed stable enough to trust by the project on which they're reporting are those posting an actual -1 vote in the verified column of the reviewers table. The rest are likely still works in progress.

Maintainers of third-party CI systems which are experiencing problems should be updating the table at to indicate this, but not all of them remember to do so.

2015-03-30 13:52:46 -0500 edited answer how to request code review

You might want to try starting over from the clone step. The error message "you are not allowed to upload merges" implies that at some point between the clone and the review you did a git pull or something similar which has introduced a merge commit into your bug/1437794 topic branch that doesn't exist in the master branch. Our Gerrit ACLs explicitly prevent inclusion of merge commits in normal code review.

Alternatively, if you're a seasoned Git user, it should just be a matter of inspecting your current commit history and rebasing your commit on top of something which is present in the remote branch (for example, the branch tip commit).