Wednesday, 2019-07-03

*** gyee has quit IRC00:28
*** schwicht has quit IRC00:41
*** joshualyle has quit IRC01:11
*** kplant has quit IRC01:41
*** dasp has quit IRC02:46
*** dasp has joined #openstack-ansible03:03
*** djhankb has quit IRC03:38
*** udesale has joined #openstack-ansible03:56
*** partlycloudy has quit IRC04:28
*** partlycloudy has joined #openstack-ansible04:29
*** pcaruana has joined #openstack-ansible05:06
jannojrosser: so host="rbd:volumes" is just for display and has no other impact?05:34
*** udesale has quit IRC05:38
logan-janno: it has a big (positive) impact if you lose a cinder-volume host, because you no longer have to manually migrate volumes between cinder-volume instances. they'll all be sharing the same "hostname" so the volumes will not be mapped to a specific cinder-volume instance anymore.05:52
logan-with the old setup, if you had volumehost1 and volumehost2, both using ceph backends, they are basically just API interfaces to ceph. both have equal potential to manage volumes. but if volumehost1 goes down, you can no longer manage any of the volumes that were managed by volumehost1, even though volumehost2 could manage them just fine.05:55
logan-with the backend host setting, the volumes are owned by a fake/virtual host that both volumehost1 and volumehost2 serve requests for. no remapping is required if one of the hosts is lost.05:55
jrosserlogan-: we still need to address this renaming in R-S upgrade05:57
logan-jrosser: yeah :/05:57
*** luksky has joined #openstack-ansible06:27
*** miouge36 has quit IRC06:27
*** miouge36 has joined #openstack-ansible06:27
*** cshen has joined #openstack-ansible06:30
*** luksky has quit IRC06:48
*** luksky has joined #openstack-ansible07:06
*** rpittau|afk is now known as rpittau07:06
jannoalright, thank you. I was asking because I created to backends with two different pools, both backends are displayed in horizon, but all volumes are always created in the same pool07:09
*** tosky has joined #openstack-ansible07:20
*** luksky11 has joined #openstack-ansible07:43
*** luksky has quit IRC07:45
*** miloa has joined #openstack-ansible07:55
miloaMorning :)07:55
*** luksky11 has quit IRC07:55
*** rgogunskiy has quit IRC08:01
*** trident has quit IRC08:08
*** luksky11 has joined #openstack-ansible08:08
*** trident has joined #openstack-ansible08:09
*** luksky11 has quit IRC08:11
*** shyamb has joined #openstack-ansible08:21
*** jsquare has quit IRC08:25
*** jsquare has joined #openstack-ansible08:25
*** luksky11 has joined #openstack-ansible08:27
*** shyamb has quit IRC08:28
*** luksky11 has quit IRC08:33
*** ivve has joined #openstack-ansible08:34
*** shyamb has joined #openstack-ansible08:53
jrossermorning09:02
*** udesale has joined #openstack-ansible09:04
*** sum12 has joined #openstack-ansible09:10
*** luksky11 has joined #openstack-ansible09:12
openstackgerritFlorian Haas proposed openstack/openstack-ansible stable/stein: Ensure systemd-journal-remote.socket service is started  https://review.opendev.org/66884309:30
*** tosky has quit IRC09:39
*** tosky has joined #openstack-ansible09:40
*** dmsimard9 has joined #openstack-ansible10:08
*** dmsimard has quit IRC10:08
*** shyamb has quit IRC10:20
*** udesale has quit IRC10:28
*** udesale has joined #openstack-ansible10:29
*** shyamb has joined #openstack-ansible10:40
jamesdentonmornin10:49
*** udesale has quit IRC10:52
*** udesale has joined #openstack-ansible10:54
*** udesale has quit IRC10:58
*** udesale has joined #openstack-ansible10:58
*** cshen has quit IRC10:59
*** cshen has joined #openstack-ansible11:01
*** udesale has quit IRC11:19
jamesdentonAnyone notice that Cinder is not configured to log to /var/log/cinder in recent Master?11:21
*** kplant has joined #openstack-ansible11:22
jamesdentonand possibly Keystone?11:23
*** schwicht has joined #openstack-ansible11:41
*** ansmith has quit IRC11:52
jannojamesdenton: I just was looking for a cinder log but I wasn't able to find any.11:52
*** jsquare has quit IRC11:53
*** schwicht has quit IRC11:53
*** jsquare has joined #openstack-ansible11:53
jamesdentonwhat version are you on?11:53
kaiokmojamesdenton: janno, same here11:54
jannostein11:54
kaiokmoon rocky11:54
jamesdentonhmm. ok. Well, the journal has cinder-related logs if you need to check something11:55
jamesdentonbut in the meantime, may wanna wait for one of the cores to pop in and we can ask them11:55
kaiokmojamesdenton: take a look at rocky re-no https://docs.openstack.org/releasenotes/openstack-ansible/rocky.html#relnotes-18-0-0-stable-rocky11:56
jamesdentonOh, well alrighty then. I guess this is expected11:57
kaiokmologs from a couple services were moved to journal, such as cinder and keystone11:57
kaiokmoyeah11:57
jamesdentonthanks, kaiokmo11:57
jamesdentonjanno kaiokmo - 'journalctl -u cinder-api -f' fits the bill11:58
jamesdentonor whatever service11:58
jannoah, thx11:59
*** schwicht has joined #openstack-ansible12:15
*** shyamb has quit IRC12:16
jannoagain a question regarding backend_host: is there something special about the name rbd:volumes? is there any association between the part after : and the ceph pool(s)?12:21
jamesdentoni don't know, sorry.12:26
*** shyamb has joined #openstack-ansible12:27
kplantit might just be a friendly naming scheme? <driver>:<vol_name> ?12:30
kplanti mindlessly configured mine the same way :-/12:30
jannokplant: rather :<pool_name> than :<vol_name>12:33
jannokplant: at the moment rbd:volumes is hard-coded in cinder.conf.j212:34
kplantyeah, pool name12:36
logan-janno: no there's not an association between that and the pool name. it just needs to be consistent across all volume hosts serving that backend and all volumes on a particular backend12:36
kplantlogan-: i didn't mean i direct mapping, i meant a choice to name it that way12:36
kplanta direct mapping*12:37
jannologan-: ok, but when I let osa create two ceph backends. Do they need different backend_host entries?12:37
logan-janno: you'll see that cinder also appends the backend name to the host of a volume, so no12:38
logan-if you look at the 'host' of a volume, it is <backend host>@<volume type>#<backend name>12:39
*** ansmith has joined #openstack-ansible12:40
*** dmsimard9 is now known as dmsimard12:43
*** schwicht has quit IRC12:50
jannoI have created two backends. one is named 'slow' and the other is named 'RBD'. I see both backends when creating a volume in Horizon, but when I choose slow as backend the RBD one gets set and  the volume is created in the pool belonging to backend RBD, which is named volumes.12:54
jannoThat's my underlying problem.12:55
jannofull host value for each volume is rbd:volumes@RBD#rbddriver12:56
*** udesale has joined #openstack-ansible13:03
jannowell, does volume_backend_name need to be unique per backend?13:07
*** schwicht has joined #openstack-ansible13:08
*** nicolasbock has joined #openstack-ansible13:11
*** BjoernT has joined #openstack-ansible13:20
logan-yes13:23
*** shyamb has quit IRC13:23
janno'volume_backend_name: rbddriver' from https://docs.openstack.org/openstack-ansible/stein/de/user/ceph/full-deploy.html sounded too necessary.13:26
jannoThank you!13:27
*** vnogin has joined #openstack-ansible13:31
*** spatel has joined #openstack-ansible13:37
spatelmorning13:57
spatelhttps://bugs.launchpad.net/openstack-ansible/+bug/183522513:57
openstackLaunchpad bug 1835225 in openstack-ansible "rsyslog client not getting deployed with stein release " [Undecided,New]13:57
spatelwhy rsyslog_client not getting deploy13:57
spatelvery strange issue13:57
*** BjoernT_ has joined #openstack-ansible13:59
*** BjoernT has quit IRC14:02
BjoernT_wasnt that replaced in favor of the systemd journal client ?14:08
*** BjoernT_ is now known as BjoernT14:08
spatelBjoernT: really ?14:13
spateli am seeing this error in my logs14:14
*** ivve has quit IRC14:14
spatelsystemd-journal-upload: #033[1;31mUpload to http://172.28.8.5:19532/upload failed: Failed connect to 172.28.8.5:19532; Connection refused#033[0m14:15
spatelBjoernT: is this documented that we are replacing rsyslog to systemd journal?14:16
jrosserspatel: that is different, that is systemd log forwarding not rsyslog14:17
spatelSo we are continue supporting rsyslog_client with stein right?  (still trying to understand why ryslog client didn't get deploy)14:18
spateleverywhere /etc/rsyslog.d/  directory is empty14:19
jrosserwell lets deal with that error first14:19
BjoernTthe role is still there but only on or the other would make sense14:19
BjoernTsee releasenotes/notes/rsyslog-disable-ffc4ebf27cc77330.yaml14:20
BjoernTits deprecated14:20
jrosserthere is this https://review.opendev.org/#/c/668843/1 or https://review.opendev.org/#/c/659433/ as alternative ways to fix that systemd log forwarding14:20
BjoernTdeprecations:14:21
BjoernT  - With the implementation of `systemd-journal-remote` the14:21
BjoernT    `rsyslog_client` role is no longer run by default. To enable the legacy14:21
BjoernT    functionality, the variable `rsyslog_client_enabled` and14:21
BjoernT    `rsyslog_server_enabled` can be set to **true**.14:21
spatelBjoernT: huh... that make sense..14:22
spatelthat is why i wonder why my syslog server and clients are doing nothing14:22
spateljrosser: do you want me to put that patch by hand ?14:24
jrossereither should fix the journal log forwardingh14:24
jrosserlogan-: version is likley more elegant than mine but i've not had time to really look very hard at it14:25
spatelwhy did we think of not continue with rsyslog_client  and replace with journal ?14:26
BjoernTone service less to manage and journald is more efficient I would assume14:27
spatelBjoernT: we have centralized ELK, how do i tell journal to send all logs to ELK ?14:27
BjoernTonly if logstash feed the logs into elasticsearch14:28
BjoernTright now I would assume no14:28
BjoernTthe stein patch seems to be ok14:30
BjoernT● systemd-journal-upload.service - systemd-journal-upload service14:30
BjoernT   Loaded: loaded (/etc/systemd/system/systemd-journal-upload.service; enabled; vendor preset: disabled)14:30
BjoernT   Active: active (running) since Wed 2019-07-03 10:26:15 EDT; 3min 32s ago14:30
jrosserafaik the issue is in the log host where the socket isnt listening, even though the process runs14:31
jrosserall magical systemd-ness14:31
spateljrosser: i did restart all services on log host systemctl restart systemd-journa*14:32
spatelin container (not host itself)14:32
jrosserit's systemd-journal-remote.socket that matters here14:33
spatelbut still 19532 nothing listening14:33
spatellet me restart that specific14:33
jrosserthe patch does two things, enable the service, and starts it14:34
jrosserthe default is not enabled so restarting on its own wont help14:34
spateloh!!14:35
spateli thought patch just restart service..14:35
spatellet me hand edit patch and run rsyslog-install.yml on log host14:35
spatelthats all right?14:35
BjoernTthis patch is not for rsyslog, just           config_overrides:14:36
BjoernTinfra-journal-remote.ym14:37
* jrosser confused14:37
*** vnogin has quit IRC14:37
spatelBjoernT: yes i got that part, that it will fix journal issue, my end goal is to fix syslog_client which i am going to enable because i want to send logs to ELK14:40
spatelif journal doesn't support that then i have no choice14:41
spatelBjoernT: so all i need to add in user_variable.yum is rsyslog_client_enabled: ture  & rsyslog_server_enabled: true14:43
spateljrosser: that patch worked and now i can see log_host listening on 1953214:45
BjoernTI would look at https://github.com/mheese/journalbeat14:47
BjoernTnot to ship stuff twice over the network14:47
*** miloa has quit IRC14:48
spatelinteresting..14:48
spateli still like to go back to use syslog over journal because we have already running cloud with syslog and its known for years to troubleshoot etc..14:49
spatelI am sure journal is best but running out of time to learn new stuff in short time.14:50
spatelcan i disable journal completely so i don't duplicate stuff?14:50
BjoernTstopping the service systemd-journal-upload would do it, I could not find a override to disable largely infra-journal-remote.yml which gets automatically imported inside setup-infrastructure14:53
BjoernTwhich would enable it14:54
spatelhmm! i would put systemd-journal-upload stop in /etc/rc.local then to make it disable and stopped14:56
spatellet me enable rsyslog so i can troubleshoot some issue :(14:56
BjoernTyou can just mask it14:57
spatelYes that should work also..14:57
BjoernTrc.local is slowly disappearing and/or not really working since systemd14:57
spatelBjoernT: rsyslog_client_enabled: ture is this enough to add in user_variables ?14:58
spatelsame with server also14:58
spatelanything else?14:58
BjoernTthat would hopefully emulate the old behavior to forward to the existing rsyslog server which should be untouched at this point15:00
spatelperfect! which playbook i should need to run deploy it everywhere?15:01
spatelor i can do "openstack-ansible setup-openstack.yml --limit <infra_host>" ?15:02
spatelor i can do "openstack-ansible setup-openstack.yml --limit <infra_host> --tags rsyslog_client" ?15:03
spateli can tags to just touch rsyslog client right?15:03
BjoernTthe latter yes15:03
BjoernTyou need to run all openstack roles with a tag15:03
BjoernTacross all hosts15:03
spatelgot it15:03
BjoernTbut it depends if /etc/rsyslog.conf.d15:03
BjoernTis empty15:04
spateli will run on one container and will see15:04
BjoernTI have not checked if we wipe it on existing installs15:04
spatelI have /etc/rsyslog.conf.d  dir but is has no files15:04
spatelopenstack-ansible os-barbican-install.yml --tags rsyslog_client-config --limit ostack-infra-2-1_barbican_container-7684c7d515:06
spatelit did nothing...15:06
spatellet me try rsyslog_client-install tags15:07
spatelstill nothing15:07
-spatel- rsyslog_server_enabled: true15:08
-spatel- rsyslog_client_enabled: true15:08
spatelin user_variables.yml15:08
spateli run playbook without tags and it dropped one file /etc/rsyslog.d/50-default.conf15:12
spatelstill missing remote file.. i think i need to run server playbook15:13
*** cshen has quit IRC15:14
spatelBjoernT: still something missing i am not seeing 99-remote.conf file which is going to push logs out15:18
spatelabove changed only drop 50-default.conf file15:18
spatelBjoernT: if you interested - http://paste.openstack.org/show/753831/15:30
spatelis this broken ?15:30
*** gyee has joined #openstack-ansible15:31
*** udesale has quit IRC15:45
*** rpittau is now known as rpittau|afk16:14
*** markvoelker has joined #openstack-ansible17:02
*** openstackgerrit has quit IRC17:04
NobodyCamGood Morning OSA folks,17:14
NobodyCamOff the wall question, will OSA handle adding a second cinder backend to an existing deployment? and if so what playbooks would I need to run after updating the `storage_hosts:` section?17:17
BjoernT@spatel you can not run tasks as playbooks. You need to run setup-openstack with the rsyslog client tags17:24
spatellet me give it a try again..17:24
spateli did run specific playbook limit with container to try but that only put 50-default.conf file17:25
*** weifan has joined #openstack-ansible17:37
*** luksky11 has quit IRC17:46
*** jsquare has quit IRC17:49
*** jsquare has joined #openstack-ansible17:50
*** weifan has quit IRC17:57
*** weifan has joined #openstack-ansible17:57
*** weifan has quit IRC17:58
*** weifan has joined #openstack-ansible17:58
*** weifan has quit IRC17:58
*** weifan has joined #openstack-ansible17:58
*** weifan has quit IRC17:59
*** weifan has joined #openstack-ansible17:59
*** BjoernT has quit IRC17:59
*** weifan has quit IRC18:00
*** weifan has joined #openstack-ansible18:00
*** weifan has quit IRC18:01
*** weifan has joined #openstack-ansible18:01
*** weifan has quit IRC18:01
*** weifan has joined #openstack-ansible18:02
*** weifan has quit IRC18:02
*** weifan has joined #openstack-ansible18:02
*** weifan has quit IRC18:03
*** weifan has joined #openstack-ansible18:03
*** weifan has quit IRC18:04
*** weifan has joined #openstack-ansible18:04
*** weifan has quit IRC18:05
*** weifan has joined #openstack-ansible18:05
*** weifan has quit IRC18:05
*** weifan has joined #openstack-ansible18:09
*** BjoernT has joined #openstack-ansible18:22
*** kplant has quit IRC18:26
spatelfolks, I am talking to some folks over openstack-lbaas and look like i have strong feeling that os_octavia playbook is broken and has some bug18:27
spatelway it create lb-mgmt-net network and wire up with br-vlan it creating some strange loop or something which block my br-lbaas internet and i can't ping that interface18:28
johnsomI'm pretty sure the octavia role still has gates that test it, so I doubt the role has a networking bug.18:30
*** hwoarang has quit IRC18:31
spatelhmm should i stop deploying it in production then?18:31
spatelif its not fully tested then i don't wan to go ahead :(18:31
johnsomspatel I said it is still tested18:32
*** weifan has quit IRC18:33
spatelbefore deploying octavia my br-lbaas was working fine.. but as soon as deployed octavia it blocked my nic18:34
*** hwoarang has joined #openstack-ansible18:34
spatelnot sure how do i debug it..18:34
spateli can try something destroy octavia and see if that fix my bridge loop18:37
*** weifan has joined #openstack-ansible18:38
jrosserspatel: Octavia works in the AIO and passes the Octavia tempest tests as well, so I’m fairly sure it is working18:41
spatelyes in AIO it works, i did test that18:42
spatelin 3 node controller its not18:42
*** luksky11 has joined #openstack-ansible18:42
spatelAIO has all internal dummy interface and possible it not seeing issue which i am seeing..18:42
jrosserMaybe your config has created a loop? And STP is blocking somewhere?18:43
spateleven STP is block in all interface..18:44
spatelDid anyone running OSA with 3 node controller here?18:44
spatelwith octavia18:45
jrosserSo this means you have an error in your networking somewhere18:45
spatelnot sure where i should look, all i can see its very simple bridge network. everything was working and pinging before i start deploying OSA18:46
spatelI can ping br-vxlan, br-mgmt etc.. all good only br-lbaas is bricks (no ping no arp reply)18:47
spatelI am thinking i can destroy lb-mgmt-net network in neutron and see if that break my loop or something if any18:47
*** weifan has quit IRC18:49
*** KeithMnemonic has joined #openstack-ansible18:51
*** devx has quit IRC19:12
*** devx has joined #openstack-ansible19:14
*** markvoelker has quit IRC19:19
*** markvoelker has joined #openstack-ansible19:19
*** weifan has joined #openstack-ansible19:22
*** ansmith has quit IRC19:23
*** weifan has quit IRC19:26
*** kplant has joined #openstack-ansible19:44
*** hamzaachi has joined #openstack-ansible19:48
*** goldyfruit has quit IRC20:24
*** goldyfruit has joined #openstack-ansible20:24
*** trident has quit IRC20:43
*** weifan has joined #openstack-ansible20:45
*** trident has joined #openstack-ansible20:45
*** goldyfruit has quit IRC20:47
*** weifan has quit IRC20:49
*** goldyfruit has joined #openstack-ansible21:02
*** weifan has joined #openstack-ansible21:02
*** pcaruana has quit IRC21:16
*** schwicht has quit IRC21:31
*** ansmith has joined #openstack-ansible21:33
*** ansmith has quit IRC21:40
*** schwicht has joined #openstack-ansible21:59
*** spatel has quit IRC22:05
*** schwicht has quit IRC22:12
*** schwicht has joined #openstack-ansible22:14
*** tosky has quit IRC22:38
*** hamzaachi has quit IRC22:48
*** luksky11 has quit IRC22:48
*** schwicht has quit IRC22:54
*** weifan has quit IRC23:30
*** gyee has quit IRC23:39
*** nicolasbock has quit IRC23:41
*** gyee has joined #openstack-ansible23:54

Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!