Perl 6 - the future is here, just unevenly distributed

IRC log for #fuel, 2016-06-22

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

All times shown according to UTC.

Time Nick Message
01:02 xarses joined #fuel
01:02 Zer0Byte__ hi someone there
01:09 v1k0d3n joined #fuel
01:10 raunak joined #fuel
01:14 Zer0Byte__ any idea
01:15 Zer0Byte__ why when i deploy fuel 9.0
01:15 Zer0Byte__ i got this error
01:15 Zer0Byte__ on the controller
01:15 Zer0Byte__ Validation of Mysql_grant[murano@TMC-CONTROLLER-1/murano.*] failed: name must match user and table parameters at /etc/puppet/modules/openstacklib/manifests/db/mysql/host_access.pp:40
01:20 raunak joined #fuel
01:48 ilbot3 joined #fuel
01:48 Topic for #fuel is now Fuel 8.0 (Liberty) https://www.fuel-infra.org/ | Paste here http://paste.openstack.org/ | IRC logs http://irclog.perlgeek.de/fuel/
02:00 justif joined #fuel
02:23 mwhahaha https://github.com/puppetlabs/puppetlabs-mysql/blob/master/lib/puppet/type/mysql_grant.rb#L36 seems like an upstream bug in puppet-murano or something
02:24 mwhahaha _degorenko|afk: -^
03:20 raunak joined #fuel
03:46 raunak joined #fuel
03:50 elopez joined #fuel
03:53 championofcyrodi joined #fuel
04:20 tobiash joined #fuel
04:29 raunak joined #fuel
04:55 Julien-zte joined #fuel
05:00 ub joined #fuel
05:45 javeriak joined #fuel
05:49 javeriak_ joined #fuel
06:06 cartik joined #fuel
06:07 cartik Hi, in fuel bootstrap node is showing down while its up
06:07 cartik im able to ssh to the node
06:07 cartik i tried restarting the mcollective docker container in the master and also tried restarting the mcollective in the node
06:08 cartik still the node is not online
06:23 javeriak joined #fuel
06:33 cartik how do i restart nailgun for a node in bootstrap mode
06:46 iberezovskiy joined #fuel
06:52 dmellado_ joined #fuel
06:54 charz joined #fuel
06:55 intr1nsic_ joined #fuel
07:31 DavidRama joined #fuel
07:33 DavidRama joined #fuel
08:04 noshankus joined #fuel
08:41 piotrk joined #fuel
08:42 piotrk Hi all
08:42 bapalm joined #fuel
08:43 piotrk I have a quick question: I deployed OpenStack using fuel and when I tried to add new compute I mistyped hostname for new node and now all of my nodes are in error state
08:45 yassine__ joined #fuel
08:45 piotrk Is it safe to try to add this node again? should I be worried that fuel will reinstall my entire OpenStack env?
08:54 TiDjY35_ joined #fuel
08:55 piotrk I have a quick question: I deployed OpenStack using fuel and when I tried to add new compute I mistyped hostname for new node and now all of my nodes are in error state
08:55 piotrk Is it safe to try to add this node again? should I be worried that fuel will reinstall my entire OpenStack env?
09:09 LGee you can rename a node with fuel
09:10 LGee not sure if that helps
09:49 piotrk @LGee I will try that thanks
09:49 HeOS joined #fuel
09:54 bapalm joined #fuel
10:29 mescanef joined #fuel
10:41 DaveJ__ joined #fuel
11:00 hkominos joined #fuel
11:34 ub joined #fuel
11:40 ub2 joined #fuel
11:50 Seafire joined #fuel
11:53 Seafire Hello, everybody! I'm having some trouble finding where I can add packages which are going to be fetched when creating a local mirror using fuel-mirror (I'm working with Fuel 9), could someone please point me in the right direction? Thanks
12:00 mescanef joined #fuel
12:54 yantarou joined #fuel
13:06 piotrk I have a quick question: I deployed OpenStack using fuel and when I tried to add new compute I mistyped hostname for new node and now all of my nodes are in error state
13:06 piotrk Is it safe to try to add this node again? should I be worried that fuel will reinstall my entire OpenStack env?
13:06 piotrk http://paste.openstack.org/show/521162/
13:07 piotrk I got this error
13:07 piotrk thanks for any information
13:07 permalac joined #fuel
13:13 piotrk I also create question on launchpad.net https://answers.launchpad.net/fuel/+question/295559
13:31 ub joined #fuel
13:38 sallum joined #fuel
13:39 skamithi2 joined #fuel
13:40 skamithi2 joined #fuel
13:41 pmcg left #fuel
13:42 lquince joined #fuel
13:42 mwhahaha piotrk: it won't reinstall, it'll just run what is necessary
13:42 lquince Hi
13:43 lquince I have a strange problem that I understand but cannot fix it..
13:44 mwhahaha Seafire: there's a config file for fuel-mirror that you can add the package to, i don't remember it off the top of my head. I think i've previously mentioned it if you wanted to look through the irc logs
13:44 lquince Deployed an Environment on 8.0 when it was first released, 2 Controllers, 3 Mongo's, 4 Ceph OSD's, 5 Compute nodes.
13:44 Seafire Ok, I'll look at the logs thanks
13:45 lquince Now when I come to deploy additional Compute Node the Nova Service is never registered for the node when it get started..
13:45 mwhahaha lquince: any messages in the nova logs?
13:46 mwhahaha also you really should have 3 controllers not 2
13:46 lquince I have found the problem to be the version of nova-compute and nova-conductor are different.
13:46 lquince This is the controller
13:46 lquince root@bc07s12-a7:~# dpkg -l |grep nova
13:46 lquince ii  nova-api                             2:12.0.0-1~u14.04+mos43                all          OpenStack Compute - compute API frontend
13:46 lquince ii  nova-cert                            2:12.0.0-1~u14.04+mos43                all          OpenStack Compute - certificate manager
13:46 lquince ii  nova-common                          2:12.0.0-1~u14.04+mos43                all          OpenStack Compute - common files
13:46 lquince ii  nova-compute                         2:12.0.0-1~u14.04+mos43                all          OpenStack Compute - compute node
13:46 lquince ii  nova-compute-kvm                     2:12.0.0-1~u14.04+mos43                all          OpenStack Compute - compute node (KVM)
13:46 lquince ii  nova-conductor                       2:12.0.0-1~u14.04+mos43                all          OpenStack Compute - conductor service
13:46 lquince ii  nova-consoleauth                     2:12.0.0-1~u14.04+mos43                all          OpenStack Compute - Console Authenticator
13:47 lquince ii  nova-consoleproxy                    2:12.0.0-1~u14.04+mos43                all          OpenStack Compute - NoVNC proxy
13:47 lquince ii  nova-objectstore                     2:12.0.0-1~u14.04+mos43                all          OpenStack Compute - object store
13:47 lquince ii  nova-scheduler                       2:12.0.0-1~u14.04+mos43                all          OpenStack Compute - virtual machine scheduler
13:47 lquince ii  python-nova                          2:12.0.0-1~u14.04+mos43                all          OpenStack Compute - libraries
13:47 lquince ii  python-novaclient                    2:2.30.2-1~u14.04+mos3                 all          client library for OpenStack Compute API
13:47 lquince This is the new node
13:47 lquince root@bc07s12-a7:~# dpkg -l |grep nova
13:47 lquince ii  nova-api                             2:12.0.0-1~u14.04+mos43                all          OpenStack Compute - compute API frontend
13:47 lquince ii  nova-cert                            2:12.0.0-1~u14.04+mos43                all          OpenStack Compute - certificate manager
13:47 lquince ii  nova-common                          2:12.0.0-1~u14.04+mos43                all          OpenStack Compute - common files
13:47 lquince ii  nova-compute                         2:12.0.0-1~u14.04+mos43                all          OpenStack Compute - compute node
13:47 lquince ii  nova-compute-kvm                     2:12.0.0-1~u14.04+mos43                all          OpenStack Compute - compute node (KVM)
13:47 lquince ii  nova-conductor                       2:12.0.0-1~u14.04+mos43                all          OpenStack Compute - conductor service
13:47 lquince ii  nova-consoleauth                     2:12.0.0-1~u14.04+mos43                all          OpenStack Compute - Console Authenticator
13:47 lquince ii  nova-consoleproxy                    2:12.0.0-1~u14.04+mos43                all          OpenStack Compute - NoVNC proxy
13:47 lquince ii  nova-objectstore                     2:12.0.0-1~u14.04+mos43                all          OpenStack Compute - object store
13:47 lquince ii  nova-scheduler                       2:12.0.0-1~u14.04+mos43                all          OpenStack Compute - virtual machine scheduler
13:47 lquince ii  python-nova                          2:12.0.0-1~u14.04+mos43                all          OpenStack Compute - libraries
13:47 lquince ii  python-novaclient                    2:2.30.2-1~u14.04+mos3                 all          client library for OpenStack Compute API
13:47 lquince Sorry this is the new node
13:48 lquince root@node31-a8:~# dpkg -l |grep nova
13:48 lquince ii  nova-common                         2:12.0.2-1~u14.04+mos21                all          OpenStack Compute - common files
13:48 lquince ii  nova-compute                        2:12.0.2-1~u14.04+mos21                all          OpenStack Compute - compute node
13:48 lquince ii  nova-compute-kvm                    2:12.0.2-1~u14.04+mos21                all          OpenStack Compute - compute node (KVM)
13:48 lquince ii  python-nova                         2:12.0.2-1~u14.04+mos21                all          OpenStack Compute - libraries
13:48 lquince ii  python-novaclient                   2:2.30.2-1~u14.04+mos5                 all          client library for OpenStack Compute API
13:48 mwhahaha shouldn't matter as they are still the same series
13:48 lquince What is the process to align these? (I note your comment about the controllers, one died but until i correct this if I deploy a new one to replace it deploys with the wrong version)
13:49 mwhahaha you should just be able to update the package and restart the service
13:50 lquince apt-get install  nova-conductor
13:50 lquince Reading package lists... Done
13:50 lquince Building dependency tree
13:50 lquince Reading state information... Done
13:50 lquince nova-conductor is already the newest version.
13:50 lquince Thats what I thought
13:50 mwhahaha apt-get update; apt-get install nova-conductor
13:51 lquince Reading package lists... Done
13:51 lquince W: GPG error: http://mirror.fuel-infra.org mos8.0-holdback Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY BCE5CC461FA22B08
13:51 lquince W: GPG error: http://mirror.fuel-infra.org mos8.0-security Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY BCE5CC461FA22B08
13:51 lquince W: GPG error: http://mirror.fuel-infra.org mos8.0-updates Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY BCE5CC461FA22B08
13:51 lquince root@bc07s12-a7:~# apt-get install  nova-conductor
13:52 lquince Reading package lists... Done
13:52 lquince Building dependency tree
13:52 lquince Reading state information... Done
13:52 lquince nova-conductor is already the newest version.
13:52 lquince The following packages were automatically installed and are no longer required:
13:52 lquince cloud-guest-utils eatmydata python-oauth python3-pycurl
13:52 lquince python3-software-properties software-properties-common unattended-upgrades
13:52 lquince Use 'apt-get autoremove' to remove them.
13:52 lquince 0 upgraded, 0 newly installed, 0 to remove and 109 not upgraded.
13:52 lquince thought that and tried that too
13:53 azemlyanov joined #fuel
13:53 mwhahaha hmm the lack of a pub key might be a problem
13:53 lquince nova-log
13:53 lquince 2016-06-22 13:18:25WARNINGnova.virt.libvirt.driver [req-b6af79ef-024f-4647-a5d9-fbf295b39f83 - - - - -] Cannot update service status on host "node31-a8.enc.iq.int" since it is not registered.
13:53 lquince 2016-06-22 13:18:25INFOnova.virt.libvirt.driver [-] Connection event '1' reason 'None'
13:53 lquince 2016-06-22 13:18:25INFOnova.service [-] Starting compute node (version 12.0.2)
13:54 lquince Have the same pub key issue on the new node as well
13:54 lquince Reading package lists... Done
13:54 lquince W: GPG error: http://mirror.fuel-infra.org mos8.0-holdback Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY BCE5CC461FA22B08
13:54 lquince W: GPG error: http://mirror.fuel-infra.org mos8.0-security Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY BCE5CC461FA22B08
13:54 lquince W: GPG error: http://mirror.fuel-infra.org mos8.0-updates Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY BCE5CC461FA22B08
13:54 lquince root@node31-a8:
13:55 mwhahaha do apt-cache policy nova-compute
13:55 lquince On the new node?
13:55 lquince root@node31-a8:/etc/apt/sources.list.d# apt-cache policy nova-compute
13:55 lquince nova-compute:
13:55 lquince Installed: 2:12.0.2-1~u14.04+mos21
13:55 lquince Candidate: 2:12.0.2-1~u14.04+mos21
13:55 lquince Version table:
13:56 lquince *** 2:12.0.2-1~u14.04+mos21 0
13:56 lquince 1050 http://mirror.fuel-infra.org/mos-repos/ubuntu/8.0/ mos8.0-updates/main amd64 Packages
13:56 lquince 100 /var/lib/dpkg/status
13:56 lquince 2:12.0.0-1~u14.04+mos43 0
13:56 lquince 1050 http://10.79.255.250:8080/liberty-8.0/ubuntu/x86_64/ mos8.0/main amd64 Packages
13:56 lquince 1:2014.1.5-0ubuntu1.4 0
13:56 lquince 500 http://archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages
13:56 lquince 1:2014.1.3-0ubuntu1.1 0
13:56 lquince 500 http://archive.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages
13:56 lquince 1:2014.1-0ubuntu1 0
13:56 lquince 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
13:56 lquince root@bc07s12-a7:~# apt-cache policy nova-compute
13:56 lquince nova-compute:
13:56 lquince Installed: 2:12.0.0-1~u14.04+mos43
13:56 lquince Candidate: 2:12.0.0-1~u14.04+mos43
13:56 lquince Version table:
13:56 lquince 2:12.0.2-1~u14.04+mos21 0
13:56 lquince 500 http://mirror.fuel-infra.org/mos-repos/ubuntu/8.0/ mos8.0-updates/main amd64 Packages
13:56 lquince *** 2:12.0.0-1~u14.04+mos43 0
13:56 lquince 1050 http://10.79.255.250:8080/liberty-8.0/ubuntu/x86_64/ mos8.0/main amd64 Packages
13:56 lquince 100 /var/lib/dpkg/status
13:56 lquince 1:2014.1.5-0ubuntu1.4 0
13:56 lquince 500 http://archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages
13:56 lquince 1:2014.1.3-0ubuntu1.1 0
13:56 lquince 500 http://archive.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages
13:56 lquince 1:2014.1-0ubuntu1 0
13:56 lquince 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
13:57 mwhahaha so on your old system the local mirror take priority over the remote mirror
13:57 mwhahaha but that's not true on the new system
13:57 mwhahaha not sure how that would have changed over time
13:57 lquince me neither as these have been deploy via the web gui..
13:57 Seafire mwhahaha: I found the config file in the irc logs,  /usr/share/fuel-mirror/ubuntu.yaml...modified and added a package..now should I run the fuel-mirror create or is there an "update" command which only fetches the new package?
13:58 mwhahaha Seafire: fuel-mirror will just update the local mirror after the first run
13:58 mwhahaha lquince: also not sure why updates are reporting the old version since the new version is there
13:58 Seafire perfect, thank you
14:00 Bomfunk joined #fuel
14:05 LGee ugh, maybe put those on a pastebin the next time
14:06 lquince mwhahaha: could it be because of package dependency's?
14:08 mwhahaha no
14:08 mwhahaha you'd just need to adjust the repo priorities
14:09 lquince Ok but why would they change via fuel?
14:09 mwhahaha i have no idea
14:09 mwhahaha might have been part of a bug fix or something, did you apply and updates to the master?
14:11 lquince Not yet
14:12 lquince If i do a yum update there is 12 packages to update
14:14 lquince I could align the priorities in the WEB GUI and redeploy
14:15 mwhahaha i thought the repos were locked after deploy
14:16 mwhahaha anyway i find it odd that it's not registering due to the version mismatch as it's a minor version change
14:17 mwhahaha It also seems that it's a bug that the liberty updates have the older version so i'll look into that today and file a bug
14:18 lquince just checked both nodes in the /etc/apt/preferences.d and they both match..
14:18 lquince could it be because I did not create a mirror at the beginning?
14:21 mwhahaha yea
14:21 mwhahaha when you create a mirror it updates the priority so the new nodes take the local over the remote
14:27 lquince So whats strange tho is my Pin-Priority on the controller does not match the result from apt-cache policy ?
14:28 lquince Is it set to 1050 and the result is 500
14:29 mwhahaha yea i'm not sure how the pins get calculated for apt-cache and if there's some sort of magical clean command you need to run for it to update it
14:30 mwhahaha kinda like yum clean metadata :D
14:31 mwhahaha i thought apt-get update should do that
14:32 lquince I would normally just run apt-get upgrade, but its a live system so kinda don't want to break the whole thing
14:34 mwhahaha you can do a version specification
14:34 mwhahaha alternatively update the local mirror
14:35 mwhahaha i was reading the versions backwards, so your local mirror is out of date but takes a higher priority over the remote
14:38 lquince Ok in my case I am trying to set the local as the higher priority for now and see if that works..
14:39 mwhahaha the problem is the local is the 12.0.0 version and the remote is 12.0.2
14:42 lquince I see that, but if i change the priority in the environment to favour the local (fuel node) then they should be the same version if I delete and redeploy the node.
14:43 mwhahaha sure
14:58 lquince mwhahaha: So I set the priority to 2000 in the Environment settings, now the node shows Candidate: 2:12.0.0-1~u14.04+mos43
14:58 lquince as the install candidate.
14:58 mwhahaha k
15:08 lquince Well that worked, now had the additional node up and running..
15:10 bapalm joined #fuel
15:11 chardegen joined #fuel
15:22 xarses joined #fuel
15:28 piotrk mwhahaha: taking into account your nick, I am a little affraid clicking deploy ;) hoping that it wont erase my prod OpenStack
15:29 mwhahaha it won't
15:30 v1k0d3n joined #fuel
15:30 mwhahaha in the older versions an error would mark all nodes as in error state, it was fixed in 9 i think
15:30 mwhahaha but what happens is it'll run the tasks that are necessary and it doesn't reinstall from scratch
15:34 piotrk thanks for the info...we will be upgrading soon
15:44 wiza left #fuel
15:46 kur1j joined #fuel
15:58 javeriak joined #fuel
15:58 kur1j this might be stupid question but do I have to install Manila by hand on my OS environment? I don't see an obvious way of doing it through the Fuel UI, or did I miss it?
16:06 mwhahaha unless there's a plugin somewhere, you'd have to install it manually
16:07 Zer0Byte__ joined #fuel
16:07 raunak joined #fuel
16:13 javeriak_ joined #fuel
16:16 kur1j So under "Create a new OpenStack environment" "Install Murano" is considered "DEPRECATED" but it doesn't say that anywhere else and it doesn't appear to be deprecated in the OS community. did I miss something?
16:16 mwhahaha the plan was to move it to a plugin
16:16 mwhahaha so it's deprecated in fuel
16:16 kur1j ah
16:23 lquince would anyone know how i can remove bootp host definitions from fuel.. I have a host that I have replaced the hd, deleted in fuel but always still trys to boot from the drive even tho it needs provisioning.
16:23 mwhahaha lquince: cobbler on the fuel master
16:23 mwhahaha you can use the 'cobbler' command to manage it
16:23 mwhahaha you'll want to remove the old system
16:24 DavidRama left #fuel
16:25 lquince cheers
16:28 skamithi1 joined #fuel
16:48 skamithi2 joined #fuel
16:59 javeriak joined #fuel
17:02 Jabadia joined #fuel
17:07 DavidRama joined #fuel
17:09 javeriak_ joined #fuel
17:14 kur1j_ joined #fuel
17:15 kur1j_ Is there not any Ambari-2.3 images? http://sahara-files.mirantis.com/images/upstream/mitaka/
17:22 mwhahaha doesn't look like it
17:26 Jabadia joined #fuel
18:07 Verilium joined #fuel
18:09 Verilium Hmm, https://www.fuel-infra.org/ shows 9.0 as latest stable.  Is it?  Shoudn't be 8.0...?
18:14 mwhahaha no we released 9.0 with mitaka upstream
18:14 mwhahaha we're working on essentially a 9.0.1 which fixes some of the issues with 9.0
18:16 Verilium Hmm, so, the mirantis release doesn't follow at the same time as the community release anymore?
18:16 Verilium (basically, don't bother with this 9.0 and wait for 9.0.1) :P
18:18 mwhahaha since fuel is in the big tent we release the community version with the  upstream versions
18:18 mwhahaha but the mirantis one has usually trailed the upstream openstack releases by a bit
18:19 mwhahaha you can run one of the nightly 9.0 community versions as we've reached a hard code freeze so those are pretty close to what the mirantis one will be
18:19 Verilium Ahhh, I see, ok.  That's the part I wasn't sure about, that the community version follows the upstream.
18:19 Verilium Which, afaik, would be a difference compared to previous versions.
18:19 mwhahaha yea
18:20 Verilium Nice, ok, good to know.
18:20 Verilium Thanks, as usual. :)
18:44 Verilium mwhahaha:  Also, I suppose, there should (probably?) be an upgrade path that will be available to go from 9.0 to 9.0.1?
18:44 elopez joined #fuel
18:44 mwhahaha not sure
18:44 Verilium ...ok, or I just wait a week or so.
18:46 elopez_ joined #fuel
18:48 mwhahaha yea i'm not sure if there's a community -> mirantis migration path either
18:52 Verilium Yeah.  More wondering for community 9.0 -> community 9.0.1 in this particular case.
18:53 mwhahaha that's more likely just going to be an apt-get update; apt-get upgrade
18:53 mwhahaha and a yum update on the master with a service restart
18:54 mwhahaha since we're not likely to add any new breaking changes to data structures in the new few weeks
19:06 * Verilium nods.
19:06 skamithi1 joined #fuel
19:07 skamithi2 joined #fuel
19:13 DavidRama left #fuel
19:17 fritchie joined #fuel
19:24 javeriak joined #fuel
19:33 javeriak_ joined #fuel
19:40 javeriak joined #fuel
19:43 thumpba joined #fuel
19:57 skamithi1 joined #fuel
20:07 LEEQ joined #fuel
20:10 LEEQ Hi, Wondered if anyone has come across this? We had one of the 3 controllers HW fail, which I have removed from FUEL and all the services in Openstack and removed the Ceph Mon to.. No when I add the controller back in via FUEL it depolys unbuntu to the new hardware ok then proceeds to reconfigure install Openstack on one of the good controllers, but then fails on what seem like reconfiguring the
20:10 LEEQ network.. In the puppet log the following is logged then puppet fails on a dependancy. : (Puppet::Type::Neutron_network::ProviderNeutron) Unable to complete neutron request due to non-fatal error: "Execution of '/usr/bin/neutron net-create --format=shell --tenant_id=c92fffc3fe5244d88b4601e45d6f774d --provider:network_type=vlan --provider:physical_network=physnet2 --provider:segmentation_id=3500
20:10 LEEQ admin_internal_net' returned 1: Unable to create the network. The VLAN 3500 on physical network physnet2 is in use.". Retrying for 9 sec.
20:11 LEEQ This is correct though as the network is already in place and operational..
20:39 sbfox joined #fuel
21:15 HeOS joined #fuel
21:32 xarses LEEQ: did you manage to re-deploy the controller with the original node-id number that the previous controller had?
21:32 xarses also, which version is this?
22:16 LEEQ xaeses: Its version 8.0 but I think ive found the issue, the network names and subnets had been changed in Openstack so I just tried changing the name of the network back to "admin_internal_net" which meant it went a lot further, still failed but on the subnet where it was trying to change the CIDR.. so I have just added the subnet with the correct name and CIDR into openstack and trying again..
22:16 LEEQ No the replacment controller has a different node-id, but node that is still failing is the correct id.
22:56 krypto joined #fuel
23:01 krypto hi is adding new controller supported in fuel 6.1 ,i am getting error with mysql "Could not evaluate: Primitive 'p_mysql' was not found in CIB!"

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