Perl 6 - the future is here, just unevenly distributed

IRC log for #fuel, 2015-11-05

| Channels | #fuel index | Today | | Search | Google Search | Plain-Text | summary

All times shown according to UTC.

Time Nick Message
00:03 zhangjn joined #fuel
00:22 rmoe joined #fuel
00:30 eliqiao joined #fuel
00:31 jerrygb joined #fuel
01:00 zhangjn joined #fuel
01:01 EinstCrazy joined #fuel
01:06 aleksandr_null joined #fuel
01:11 aleksandr_null joined #fuel
01:37 hezhiqiang joined #fuel
01:41 aleksandr_null joined #fuel
01:42 shimura_ken joined #fuel
01:46 tzn joined #fuel
01:46 aleksandr_null joined #fuel
02:23 tzn joined #fuel
02:28 tzn joined #fuel
02:30 _tzn joined #fuel
02:47 ilbot3 joined #fuel
02:47 Topic for #fuel is now Fuel 7.0 (Kilo) https://software.mirantis.com | Paste here http://paste.openstack.org/ | IRC logs http://irclog.perlgeek.de/fuel/
03:15 zhangjn_ joined #fuel
03:57 eliqiao joined #fuel
03:58 eliqiao left #fuel
04:14 eliqiao1 joined #fuel
04:20 fedexo joined #fuel
04:25 tzn joined #fuel
05:08 hezhiqiang joined #fuel
05:39 nihilifer joined #fuel
05:41 zhangjn joined #fuel
06:01 javeriak joined #fuel
06:03 gomarivera joined #fuel
06:13 martineg_ joined #fuel
06:27 tzn joined #fuel
06:29 tzn joined #fuel
06:30 fzhadaev joined #fuel
07:00 eliqiao1 left #fuel
07:06 javeriak_ joined #fuel
07:11 javeriak joined #fuel
07:15 gongysh joined #fuel
07:16 gongysh left #fuel
07:18 karume joined #fuel
07:23 arozdymakha joined #fuel
07:27 karume joined #fuel
07:36 Ravindra joined #fuel
07:42 devvesa joined #fuel
07:42 Ravindra joined #fuel
07:48 Ravindra joined #fuel
07:50 e0ne joined #fuel
08:00 zhangjn joined #fuel
08:00 [HeOS] joined #fuel
08:04 e0ne joined #fuel
08:07 karume joined #fuel
08:14 Liuqing joined #fuel
08:16 karume joined #fuel
08:19 mkwiek07 joined #fuel
08:27 karume joined #fuel
08:32 devvesa joined #fuel
08:34 hyperbaba joined #fuel
08:34 e0ne joined #fuel
08:37 Liuqing joined #fuel
08:43 fzhadaev joined #fuel
08:46 e0ne joined #fuel
08:50 Liuqing joined #fuel
08:50 EinstCrazy joined #fuel
08:56 ddmitriev joined #fuel
09:01 alrick joined #fuel
09:10 Ravindra joined #fuel
09:17 martineg_ joined #fuel
09:19 rojim joined #fuel
09:19 rojim halo
09:29 Ravindra joined #fuel
09:49 apuimedo joined #fuel
09:53 e0ne joined #fuel
10:12 tkhno joined #fuel
10:22 zerda joined #fuel
10:23 zhangjn joined #fuel
10:26 Liuqing joined #fuel
10:35 zhangjn_ joined #fuel
10:40 tzn joined #fuel
10:46 Liuqing joined #fuel
10:48 EinstCrazy joined #fuel
10:56 fzhadaev joined #fuel
10:58 magicboiz joined #fuel
10:58 jerrygb joined #fuel
11:00 sergmelikyan joined #fuel
11:21 Ravindra Hi,
11:21 Ravindra I have deployed a setup from fuel.
11:21 Ravindra While checking Health Check, I am getting below mentioned error message.
11:21 Ravindra "Create volume and boot instance from it"
11:21 Ravindra "Time limit exceeded while waiting for instance becoming 'available' to finish. Please refer to OpenStack logs for more details."
11:21 Ravindra Can anyone help me out please ?
11:24 hezhiqiang joined #fuel
11:34 magicboiz joined #fuel
11:39 javeriak joined #fuel
11:47 fzhadaev joined #fuel
11:59 devvesa joined #fuel
12:08 zhangjn joined #fuel
12:15 holser Ravindra: Did you use virtualbox?
12:15 holser or some kind of virtualization
12:25 NiclasEriksson joined #fuel
12:30 NiclasEriksson I'm using Mirantis 7 I've deployed a environment using vsphere and able to a node for controller, telemetry, MongoDB and another for Cinder and a third for Cinder Proxy to VMware Datastore. But i'm failing to deploy a node for "Compute VMware". It says: "The following compute-vmware nodes are not assigned to any vcenter cluster". Has anyone seen this and have a way to solve it?
12:39 zhangjn joined #fuel
12:40 zhangjn joined #fuel
12:43 tzn joined #fuel
12:48 sergmelikyan joined #fuel
12:59 subscope joined #fuel
13:03 dklenov izinovik: Igor, can you or someone from your team take a look at Niclas' question?
13:05 cartik joined #fuel
13:07 pma joined #fuel
13:07 pma Please refer to https://docs.mirantis.com/openstack/fuel/fuel-7.0/user-guide.html#vmware-integration
13:08 pma check it out for missing steps
13:11 javeriak hi everyone, if my deployment errors out with an additional plugin, is there a quicker way to check my fixes in a new rpm rather than creating a new environment and deploying again
13:11 jerrygb joined #fuel
13:17 cartik joined #fuel
13:19 cartik joined #fuel
13:22 xarses joined #fuel
13:29 sergmelikyan joined #fuel
13:34 NiclasEriksson I think I got it now.. Probably the wrong datacenter..  We had controller and vmware-compute VM in different
13:34 NiclasEriksson .. datacenters in vmware
13:35 NiclasEriksson I think they all need to be in the same datacenter but can be in different clusters, am I right?
13:36 NiclasEriksson I would like to seperate management and compute in different clusters
13:44 tzn joined #fuel
13:45 CheKoLyN joined #fuel
13:49 pma javeriak: try to #fuel plugins --update plugin-name-2.0-2.0.1-0.noarch.rpm
13:55 bpiotrowski 84
13:55 bpiotrowski oops
14:04 jerrygb joined #fuel
14:16 fzhadaev joined #fuel
14:18 javeriak joined #fuel
14:22 Wida joined #fuel
14:22 javeriak_ joined #fuel
14:23 Wida Hello! I try update openstack 6.1 to 7.0 and in step: "octane upgrade-db $ORIG_ID $SEED_ID" I have error:
14:23 Wida 2015-11-05 13:54:04 ERROR    octane.util.subprocess cinder-manage[at node-13] stderr: /usr/lib/python2.7/dist-packages/migrate/changeset/constraint.py:85: SAWarning: Table 'encryption' specifies columns 'volume_type_id' as primary_key=True, not matching locally specified columns 'encryption_id'; setting the current primary key columns to 'encryption_id'. This warning may become an exception in a future release
14:23 Wida 2015-11-05 13:54:04 ERROR    octane.util.subprocess cinder-manage[at node-13] stderr:   self._set_parent(table)
14:25 rgowrishankar joined #fuel
14:27 dklenov ogelbukh: can you please take a look at Wida's question?
14:45 tzn joined #fuel
14:46 omartsyniuk joined #fuel
14:47 jaypipes joined #fuel
15:02 ogelbukh Wida: this is not an actual error
15:02 ogelbukh Wida: it's just warning issued by cinder db-sync script about deprecation of certain elements of DB schema
15:05 Wida ogelbukh: you mean I should skipped this message and move on?
15:06 ogelbukh Wida: that's correct
15:06 ogelbukh I will add a doc bug and update docs accordingly
15:09 neophy joined #fuel
15:09 Wida ogelbukh: thx, I move on and have new error in step "octane upgrade-controlplane $ORIG_ID $SEED_ID"
15:09 Wida [root@fuel fuel-octane]# octane upgrade-controlplane $ORIG_ID $SEED_ID
15:09 Wida 2015-11-05 15:07:58 ERROR    octane          Unknown command ['upgrade-controlplane', '3', '4']
15:11 ogelbukh Wida: it's just `upgrade-control $ORIG_ID $SEED_ID`
15:11 ogelbukh Wida: which manual do you follow?
15:12 w_verdugo joined #fuel
15:12 Wida https://docs.mirantis.com/openstack/fuel/fuel-7.0/operations.html#upgrade-environment-experimental
15:13 Wida step 7
15:13 apuimedo joined #fuel
15:15 ogelbukh Wida: understood, thank you
15:16 Wida ogelbukh: I should use command `upgrade-control $ORIG_ID $SEED_ID` instead " upgrade-controlplane $ORIG_ID $SEED_ID" ?
15:16 ogelbukh Wida: that's a typo, if you see below, you'll find correct command
15:17 ogelbukh Wida: correct
15:18 Verilium Hmm, not quite sure where I might have gone wrong...  The instances I create have external access, but DNS resolution doesn't seem to be working.
15:18 Verilium In fuel, settings, "guest os dns servers' point to a valid/working name server.
15:18 javeriak_ hey, hoping someone around can answer my question, if my deployment errors out with an additional plugin, is there a quicker way to check my fixes in a new rpm rather than creating a new environment and deploying again
15:19 mwhahaha javeriak_: you can always hack them locally and run by hand
15:20 javeriak_ mwhahaha that doesnt seem to work, this is the relevant path right /var/www/nailgun/plugins/<new-plugin> ? and an already created enviroment doesnt pick up task changes
15:21 mwhahaha so it depends on what the problem is
15:22 mwhahaha if it's a puppet or script failure of yours, I think the plugins get put in /etc/puppet/modules/<plugin name> so you could fix that
15:22 mwhahaha if it's a task ordering thing you would have to reinstall the new plugin or manually sync the tasks via rel sync and redeploy
15:22 mwhahaha you should be able to just reset the environment and redeploy rather than building a new env
15:23 javeriak_ is that /etc/puppet path relevant to the fuel node or targets?
15:24 mwhahaha so it's on the master and then gets synced to the target nodes during the deployment. so if you want to test on the target node you can hack it on that node and manually run the puppet apply task (if that's what is failing)
15:24 javeriak_ also btw, when it says "Puppet run failed. Check puppet logs for details" , which ones should i be looking at? the only puppet logs under /var/log/puppet are empty
15:24 mwhahaha on the master /var/log/docker-logs/remote/<node>/puppet.log i think
15:24 mwhahaha on the local nodes it's /var/log/puppet.log i think
15:25 sergmelikyan joined #fuel
15:26 javeriak_ right,  thanks mwhahaha
15:27 blahRus joined #fuel
15:28 sergmelikyan joined #fuel
15:29 apuimedo joined #fuel
15:39 pal_bth_ joined #fuel
15:45 tzn joined #fuel
15:57 angdraug joined #fuel
16:04 sergmelikyan joined #fuel
16:11 Verilium ...aaaaand, nevermind, I see I have to add name servers to the subnet I've created.  My bad.
16:12 javeriak_ guys im getting a "Debug: hiera(): Cannot find datafile /etc/hiera/astute.yaml" when trying to run puppet apply on a target node
16:15 jerrygb joined #fuel
16:17 mwhahaha javeriak_: you're puppet is it a pre-deployment task?
16:17 mwhahaha that gets created as part of the hiera deployment task i believe
16:17 javeriak_ yes it is
16:17 mwhahaha so you might need to move your task to be after the hiera task or just ignore that warning
16:18 mwhahaha or is it a failure?
16:18 javeriak_ its a failure, it cant fine Puppet (err): $metadata_hash["metadata"] is :undef, not a hash or array at
16:18 javeriak_ when does hiera execute? during deploy?
16:18 mwhahaha yea but early on
16:18 javeriak_ oh okay
16:19 mwhahaha it's like one of the first or second things that gets run
16:21 mwhahaha requires: [hiera]
16:30 jaypipes joined #fuel
16:30 fedexo joined #fuel
16:31 javeriak joined #fuel
16:31 jerrygb joined #fuel
16:34 tzn joined #fuel
16:42 asaprykin joined #fuel
16:50 severion joined #fuel
16:51 tuvenen_ joined #fuel
16:53 smakar_ joined #fuel
16:54 fBigBro_ joined #fuel
16:56 ktychkova_ joined #fuel
16:59 preilly_ joined #fuel
16:59 evgenyl_ joined #fuel
16:59 ukinau joined #fuel
17:00 izinovik- joined #fuel
17:05 Guest88471 joined #fuel
17:07 dilyin joined #fuel
17:07 kdavyd joined #fuel
17:20 rlljorge joined #fuel
17:21 rlljorge https://docs.mirantis.com/openstack/fuel/fuel-7.0/operations.html#upgrade-environment-experimental is security apply this in production ?
17:31 sergmelikyan joined #fuel
17:34 subscope joined #fuel
17:41 e0ne joined #fuel
17:54 e0ne joined #fuel
18:02 angdraug rlljorge: it does say "experimental" in the title :)
18:03 angdraug even if it didn't, it's a potentially disruptive operation, so all usual disclaimers about backing up everything and trying it out in staging first would still apply
18:04 e0ne joined #fuel
18:04 rlljorge angdraug: any way to upgrade ?
18:05 Wida joined #fuel
18:05 sergmelikyan joined #fuel
18:05 angdraug this IS the way to upgrade, I just can't promise that it's 100% safe
18:08 rlljorge angdraug:  Okay, we'll keep version 6.1, some day we will have a safe way to upgrade?
18:09 angdraug openstack is not notepad, I don't think there will every be a safe way to ugprade
18:09 angdraug migrating databases and restarting control plane services is inevitable
18:10 angdraug and all that introduces a risk of data loss
18:10 angdraug some day it may become able to upgrade without downtime, but never without risk
18:11 angdraug so my recommendation is to mitigate risk by having backup/restore and a staging environment
18:12 rlljorge angdraug: ok tks
18:16 javeriak joined #fuel
18:24 tzn joined #fuel
18:34 [HeOS] joined #fuel
18:58 jerrygb joined #fuel
19:05 tzn joined #fuel
19:07 ddmitriev joined #fuel
19:19 jfluhmann joined #fuel
19:38 blahRus1 joined #fuel
19:50 jfluhmann joined #fuel
19:52 sbfox joined #fuel
19:53 jerrygb joined #fuel
20:00 jobewan joined #fuel
20:26 jfluhmann joined #fuel
20:44 artem_panchenko joined #fuel
21:41 _tzn joined #fuel
22:03 HeOS joined #fuel
22:10 smakar joined #fuel
22:33 dpyzhov joined #fuel
22:51 kdavyd_ joined #fuel
23:07 tzn joined #fuel
23:16 tzn joined #fuel
23:33 jerrygb joined #fuel
23:45 jobewan joined #fuel
23:49 jerrygb_ joined #fuel
23:55 maximov joined #fuel

| Channels | #fuel index | Today | | Search | Google Search | Plain-Text | summary