- Users - oVirt List Archives

Dumb question: exclamation mark next to VM?
by Chris Adams 16 Mar '16

16 Mar '16

I set up a new oVirt 3.6.2 cluster on CentOS 7.2 (everything up to date as of yesterday). I created a basic CentOS 7.2 VM with my local customizations, created a template from it, and then created a VM from that template. That new VM has an exclamation mark next to it in the web GUI (between the up arror for "running" and the "server" icon). Usually I would expect that means something is wrong or needs attention, but I can't find anything to fix/address/etc. (no messages in the Alerts, nothing odd in the Events, etc.). What does the exclamation mark mean, and how do I clear it? -- Chris Adams <cma(a)cmadams.net>

9 17

Coming (Very) Soon - New ovirt.org Website & Deprecated Wiki
by Mikey Ariel 16 Mar '16

16 Mar '16

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 In the past months we've been working on upgrading the oVirt project infrastructure, to better support the community contributions. One of the main platforms for our user documentation, release management content, and community content has been the MediaWiki site that you all know as ovirt.org. Most of us are familiar with the wiki site format, with all its advantages and disadvantages. After several years of serving the community, I'm happy to announce that we are very near to completing a full upgrade of the website infrastructure from a wiki site to a static site, source-controlled on GitHub and authored in Markdown. This email is the pre-launch announcement, as we are reaching the final stages of the migration, and there are a few actions that might affect your work on website content in the meantime. Why migrate the website ======================= As mentioned, wiki sites provide an open and flexible content editing platform. Unfortunately, as the site grows the content becomes quite difficult to manage and curate, resulting in lots of obsolete, outdated, and incorrect information. By moving to a source-controlled repository and implementing GitHub's contribution workflow, we strive to ease the work of maintaining an up-to-date content site, employ a peer-review process for changes, and standardize the authoring markup language to lower the contribution barrier. The Middleman framework (Ruby-based static site generator) was chosen based on observing successful implementation of other open-source community websites, such as OpenStack RDO, Project Atomic, and Gluster. What we did so far ================== When we started the migration, our Web design team exported all of the wiki content from the old website and converted it to MD files. They also set up the website config flow, auto-deploy, and upgraded the look-and-feel of the website. We then initiated a content review effort as well as a UX review for the new website in a smaller forum, which caught most of the critical issues with the new website and helped us get the new format to a place where we can release the website in a near-GA/public-beta format. Yesterday (Wednesday Feb 17) we exported the website one more time and currently we're running a diff on all the files that changed since the initial export was done, to make sure we grab all the updates and the latest content before we launch the new website. What is about to happen ======================= Today we are initiating a **wiki freeze**, which means the old MediaWiki site will become read-only. This is to ensure that all of our diff scripts reflect the most current state of the content on the website, and that we don't lose any content in the transition. Barring any unexpected blockers, we will port the ovirt.org domain to point to the new website and open the new website for contributions on **Monday February 22** or earlier. What do you need to do right now ================================ If you have any wiki pages that you're actively editing, please don't save them to the old MediaWiki site, and hold onto your pending changes until we send the happy launch email. We will also include instructions on how to contribute/edit/add content to the new website, but in general the workflow will be aligned with the standard GitHub best practices (clone-edit-commit-pullrequest), so you can utilize all of the git commands that you already know or work directly within the GitHub web editor. I'd like to thank all of the people who were involved with this migration so far, ovirt.org is a big website with lots of content and it was no small task to upgrade it. Please feel free to ping me on- or off-list if you have any questions about the next steps, and expect a happy launch email soon! Cheers, Mikey - -- Mikey Ariel Community Lead, oVirt www.ovirt.org "To be is to do" (Socrates) "To do is to be" (Jean-Paul Sartre) "Do be do be do" (Frank Sinatra) Mobile: +420-702-131-141 IRC: mariel / thatdocslady Twitter: @ThatDocsLady -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJWxa5AAAoJEHYPPTOszxHow10H/jeuhzMrUrPsCBedLg7OKnNh jdKDujT/aCyA4LgnRHnVBEASunShmVaOJrMdU4r0PZbdkX1Mf5/SvCEFGKY14qAg m/5CnDhlwbp5rqo09VOGLMg20CaMtpUoE1LpKE/epGYEKSBr2JIAA+HAsYa1OEyS 9oHDDx+ZIbfHNlygW1KpW6dsuZRscTbfy4kk8rY83YdJGyQiQN+ulsjT/c2N8ArR WylohBE2OcC7+nzf7AejKJ94loWxnVhO4qWbNWAH00LArG89yFWBBSlMK6ocJUED P4k2IzgG+75eTiCZAAw5/Vaqx0YVU7hScSmBqOPQu/wo4e2t11AR7A8D7Cn+vpU= =XWEH -----END PGP SIGNATURE-----

5 4

[ANN] oVirt 3.6.4 First Release Candidate is now available for testing
by Sandro Bonazzola 16 Mar '16

16 Mar '16

The oVirt Project is pleased to announce the availability of the First Release Candidate of oVirt 3.6.4 for testing, as of March 16th, 2016 This release is available now for: * Fedora 22 * Red Hat Enterprise Linux 6.7 * CentOS Linux 6.7 (or similar) * Red Hat Enterprise Linux 7.2 or later * CentOS Linux (or similar) 7.2 or later This release supports Hypervisor Hosts running: * Red Hat Enterprise Linux 7.2 or later * CentOS Linux (or similar) 7.2 or later * Fedora 22 This release is also available with experimental support for: * Debian 8.3 Jessie This release candidate includes the following updated packages: - ovirt-engine - vdsm - ovirt-hosted-engine-ha - ovirt-hosted-engine-setup See the release notes [1] for installation / upgrade instructions and a list of new features and bugs fixed. Notes: * A new oVirt Live ISO is already available [2]. * Mirrors[3] might need up to one day to synchronize. Additional Resources: * Read more about the oVirt 3.6.3 release highlights: http://www.ovirt.org/release/3.6.4/ * Get more oVirt Project updates on Twitter: https://twitter.com/ovirt * Check out the latest project news on the oVirt blog: http://www.ovirt.org/blog/ [1] http://www.ovirt.org/release/3.6.4/ [2] http://resources.ovirt.org/pub/ovirt-3.6-pre/iso/ [3] http://www.ovirt.org/Repository_mirrors#Current_mirrors -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

1 0

Re: [ovirt-users] "wildcard resolve to multiple address" during hosted-engine --deploy
by Yedidyah Bar David 16 Mar '16

16 Mar '16

(Adding the mailing list) On Wed, Mar 16, 2016 at 4:14 AM, Zach <zfnoctis(a)gmail.com> wrote: > Hi Didi, > > I chose to go with option #2, and I now am getting: > > [ ERROR ] Failed to execute stage 'Misc configuration': Failed to setup > networks {'ovirtmgmt': {'nic': 'em1', 'bootproto': 'dhcp', > 'blockingdhcp': True, 'defaultRoute': True}}. Error code: "29" message: > "Determining IP information for ovirtmgmt... failed; no link present. > Check cable?" Please post setup logs. > > Which is *completely* nonsensical, as em1 is showing up as working both > in CentOS, and iDrac - not to mention I am connected over ssh with that > very same network interface. Perhaps you do not have an IP address on that interface? You do need one. The engine will communicate with the host using this address. > Just to be on the safe-side, I will > mention that I disabled firewalld and Networkmanager as soon as I first > logged into this machine. which also makes wonder why these need to be > disabled, since they are included by default with CentOS/RHEL 7. > > This whole process has left me fairly frustrated and confused. Sorry for that. Bugs/RFEs/patches are always welcome :-) > Why does > a previous attempt somehow completely destroy any chance of installing > the system without a complete wipe of the disks? Because of the way the deploy script is currently implemented, it would be hard to completely undo changes on failure (which we do try hard in engine-setup). We have an open RFE for supplying a cleanup tool: https://bugzilla.redhat.com/show_bug.cgi?id=1001181 See also: http://www.ovirt.org/documentation/how-to/hosted-engine/#recoving-from-fail… The source package also has: https://gerrit.ovirt.org/gitweb?p=ovirt-hosted-engine-setup.git;a=blob;f=cl… It's currently down for some reason, not sure. A mirror is available at: https://github.com/oVirt/ovirt-hosted-engine-setup/blob/master/cleanup.sh All of these are far from perfect, and reinstalling the OS is way safer when trying to debug such issues. > Why is the > installation failing to even find a network interface? Is this par for > the course to get oVirt installed? Again, not sure what the exact problem was. Please post setup logs. > > Finally, are there any current guides on setting up oVirt 3.6 in a > hosted-engine configuration with nfs/gluster all on a single machine? Not that I am aware of. loopback-mounting nfs is considered unsafe due to locking issues, see: https://lwn.net/Articles/595652/ You can use iSCSI. Most people install it on more than one machine. For a single machine, usually virt-manager is enough. Of course you can use VMs with nested-kvm to virtualize more than one machine on a single one, if you mainly do this for testing/learning/etc. > It looks like everything is old or incomplete. But perhaps it is not > intended to be used yet. Proper support is currently partial. Search the net for e.g. 'ovirt hyperconvergence' for the current efforts. The plan is to require at least 3 physical machines, to have a replica-3 gluster storage and quorum. It should be possible today to deploy on a single machine with gluster, supplying three different paths for gluster all on the same machine. For best results, currently, you should have at least 3 machines: One for storage (or a dedicated storage appliance), two for hosted-engine hosts providing high-availability. Best regards, > > > On 03/14/2016 01:41 AM, Yedidyah Bar David wrote: >> On Mon, Mar 14, 2016 at 3:19 AM, Zach <zfnoctis(a)gmail.com> wrote: >>> I keep running into the following error when going through the >>> "hosted-engine --deploy" configuration. >>> >>> [ ERROR ] Failed to execute stage 'Setup validation': wildcard >>> resolved to multiple address >>> >>> So far, I haven't been able to figure out what I'm doing wrong. My best >>> guess is that there is some issue with the FQDN that I used, but I'm not >>> sure what I've done wrong. I've included the following line in >>> /etc/hosts for the FQDN. >>> >>> 192.168.0.50 ovirt.domain.local >>> >>> I've also attached the output log, as well as the full output of me >>> answering all the prompts. >>> >>> Any help would be appreciated, let me know if I need to include more >>> information. >> It seems like there are some left-overs in vdsm from previous attempts. >> If you want to further debug this, please: >> 1. Try to give exact flow, including what you tried, changed etc at each point >> 2. Attach all setup logs and all vdsm logs >> >> If you just want it all to work, please reinstall the machine from scratch >> and try again, and if you get into problems on first attempt, check/post >> setup and vdsm logs. >> >> Best, > -- Didi

1 0

Shutdown Problems on oVirt Node
by Roger Meier 16 Mar '16

16 Mar '16

Hi their I have currently a strange problem on a new oVirt 3.6 installation. At the moment a clean shutdown doesn't work, most of the time he reboots the system or hangs in the shutdown progress. I discovered this, when i tested our multiple UPS solution and send some test signals over ipmi to our server with ex. ipmipower -h 192.168.2.218 -u root -p password --soft . We also discovered that shutdown -h now , poweroff or init 0 had the same effect. On a clean CentOS installation, which is not included in our oVirt setup this works as expected, but on our ovirt-node this doesn't work. In the shutdown progress i see the following which tooks very long: > A stop job is running for Shared Storage Lease Manager (23s / 1min 47s) At the end i had then the following on my console screen: [ OK ] Reached target Shutdown Nothing more happens. no poweroff or something. I can wait more than three minutes and nothing happens. I also tried a clean re-install from the oVirt Administration WebUI but this doesn't have any effect on this issue. When i type "service sanlock stop" or "service vdsmd stop" in the server console and then do a poweroff , all works as expected. The shutdown is the also realy fast as expected. At the moment we think that the problem is on ovirt, vdsmd or on the sanlock settings for ovirt, because all settings on our site are on default settings. Currently Setup are two Intel Server (With RRM) with CentOS-7 (1511) and oVirt 3.6.3 and one Intel Server with OpenIndiana which provides Storage via NFS. Had someone a solution for this? is this perhaps a bug and shoul'd be reported? Greetings Roger Meier

4 4

Welcome: New ovirt.org website!
by Mikey Ariel 15 Mar '16

15 Mar '16

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Following yesterday's pre-launch email[1], I'm happy to announce that the new ovirt.org[2] website is now live in **public beta** and available for community review. All the information in this email is also available in the first blog post of our shiny new oVirt blog[3]. Read on for information about new features, known issues, and a call for reviews. The old MediaWiki site is still available in read-only[4], and will be taken offline on **March 1, 2016**. This is to ensure that you can compare pages and review migrated content. What's New ========== The new Website is full of improvements and enhancements, check out these highlights: * Source content is now formatted in Markdown instead of MediaWiki. This means that you can create and edit documentation, blog posts, and feature pages with the same Markdown syntax you know. * The Website is deployed with Middleman and stored on GitHub. This means that you can make changes to content with the same GitHub contribution workflow that you know (fork, clone, edit, commit, submit pull request). We even have an "Edit this page on GitHub" link at the bottom of every page! * New layout and design, from breadcrumbs to sidebards and an upgraded landing page. (This is still WIP, please see known issues.) * Automatic redirects from the old MediaWiki site. This means that if the wiki page exists in the new website, previously-released URLs will redirect to that page. If the page was removed, the Search page will open with the page title auto-filled in the search box. * Hierarchical content structure. This means that instead of flat Wiki-style files, the deployed Website reflects an organized source repo with content sorted into directories and sub-directories. * Official oVirt blog! Our new blog welcomes contributions. This means that if you solved a problem with oVirt, want to share your oVirt story, or describe a cool integration, you can submit a pull request with a blog post and we will provide editorial reviews and help publish your posts. * Standardized contribution process. The GitHub repo now includes a README.md[5] file that you can use to learn about how to add and edit content on the website. We welcome pull requests! Known Issues ============ Despite our best efforts, there are still a few kinks with the new website that you should be aware of: * Attempting to navigate to ovirt.org (without www.) leads to a redirect loop. We have a ticket open with OpenShift, our hosting service to fix this. * Only http is available. We also have a ticket with OpenShift to add SSL and enable https. * Home page and Download page are still being upgraded by our UX experts, expect some cool new changes soon! * Feature pages look-and-feel is still under construction. You can still edit and push feature pages as usual. What's Next =========== Even though the Website is live, the work is hardly over. We'd like to ask for your help in: * Reviewing content for anything obsolete or outdated (each page in the new website includes a header toolbar with metadata from the original wiki page for your convenience) * Submitting blog posts or any other content that you wish to share with the oVirt community * Reporting bugs and proposing enhancements, for example broken links or missing pages We hope you will enjoy the new oVirt Website, looking forward to your feedback and contributions! [1] http://lists.ovirt.org/pipermail/devel/2016-February/012372.html [2] http://www.ovirt.org/ [3] http://www.ovirt.org/blog/2016/02/welcome-to-new-ovirt-site/ [4] http://old.ovirt.org/Home [5] https://github.com/oVirt/ovirt-site/blob/master/README.md - -- Mikey Ariel Community Lead, oVirt www.ovirt.org "To be is to do" (Socrates) "To do is to be" (Jean-Paul Sartre) "Do be do be do" (Frank Sinatra) Mobile: +420-702-131-141 IRC: mariel / thatdocslady Twitter: @ThatDocsLady -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJWxztZAAoJEHYPPTOszxHoOF4H/2UeK9JTspw4dYU+pUu8fKqf pSrE9ha3k9KpPnGIAx6VTnbXolNr9tHFiT8gcds1C9CVoMEPrKUxns9CTz3kPYBH /mGYCwQ+ncUNBCn+54uiKmXssaAtpVLnuxh8f1z9BDUoFjoY7ASLTzwXu9XTuH9V C9gaR0iGcRgSmBPjfPuAVWuHgimM068x5Ig2BoMSzAeCM7pO6LwiRzt3xX15xlR4 TMkUWLHdnJ1uL1GH267tMofrMnk25veDPIzuzIaPFjwIuTFgtwnUQI82ULbxcet2 NJ+y/UgwQ9JUQheoQL/oOsnSs244kFl0Vl+GuKMDGZ1FwCfoZerejnhEK+1cK0U= =KQLK -----END PGP SIGNATURE-----

4 5

3.6.3 : Disable Networkmanager?
by Nicolas Ecarnot 15 Mar '16

15 Mar '16

Hello, Several docs are contradictory about NetworkManager on the engine. Do we have to disable it in 3.6.3? (we're using CentOS 7.2) Thank you. -- Nicolas ECARNOT

1 0

Unable to "yum update" latest ovirt-engine-3.6.3.4-1.el7.centos.noarch.rpm
by Lionel Caignec 15 Mar '16

15 Mar '16

Hi, i've a working ovirt engine installed on centos 7.2, i tried to yum update in order to get latest version but yum tell there is nothing to do. My repos ovirt* are all enabled. Here my version currently installed : ovirt-engine.noarch 3.6.1.3-1.el7.centos @ovirt-3.6 So i really don't understand what happen. Someone to help me? -- Lionel Caignec Centre Informatique National de l' Enseignement Supérieur 950 rue de Saint Priest 34097 MONTPELLIER Cedex 5 Tel : (33) 04 67 14 14 14 Fax : (33)04 67 52 37 63 http://www.cines.fr

2 2

Storage migration: Preallocation forced on destination
by Nicolás 15 Mar '16

15 Mar '16

Hi, We're migrating an existing storage (glusterfs) to a new one (iSCSI). All disks on glusterfs are thin provisioned, but when migrating to iSCSI the following warning is shown: The following disks will become preallocated, and may consume considerably more space on the target: local-disk Why is that? Is there a way to migrate disks so they are thin provisioned on iSCSI as well? Thanks.

3 8

"wildcard resolve to multiple address" during hosted-engine --deploy
by Grigoriy - 15 Mar '16

15 Mar '16

After starting the deployment, in step - == NETWORK CONFIGURATION == - Please indicate a nic to set ovirtmgmt bridge on: (enp1s0f1, enp1s0f0) [enp1s0f1]: Look what the adapter you choose ?, if you select unconnected adapter you will get an Python script error "wildcard resolve to multiple address".

2 1