[Rdo-list] Glance does not save properties of images
by Daniel Speichert
Hello,
On the stable release of Havana installed through RDO, when I create images, their properties (disk_format, container_format, is_public) are lost even when set (they must be set, otherwise glance-api wouldn't accept the request).
However, they are not saved to the database. When I modify database manually, they are visible correctly, but it is still not possible to modify them through Glance.
Do you have any idea if that might be some configuration error or maybe a bug in RDO packaging?
Any help will be very much appreciated.
Best Regards,
Daniel Speichert
10 years, 10 months
[Rdo-list] libvirtd default configuration
by Yogev Rabl
Hi,
While trying to debug a problem we've noticed that the libvirt doen't write logs.
Please noticed that, and chnage the configuration of the libvirtd.conf.
thanks,
Yogev
10 years, 10 months
[Rdo-list] MariaDB installation fails
by Yogev Rabl
Hi,
I'm installing a semi distributed topology of RDO on Fedora 20.
The topology is:
- server 1: Cloud Controller
- server 2: Cinder.
- server 3: Glance.
- server 4: Nova-compute.
The packstack installation fails with the error:
2014-02-04 12:34:54::ERROR::run_setup::912::root:: Traceback (most recent call last):
File "/usr/lib/python2.7/site-packages/packstack/installer/run_setup.py", line 907, in main
_main(confFile)
File "/usr/lib/python2.7/site-packages/packstack/installer/run_setup.py", line 573, in _main
runSequences()
File "/usr/lib/python2.7/site-packages/packstack/installer/run_setup.py", line 552, in runSequences
controller.runAllSequences()
File "/usr/lib/python2.7/site-packages/packstack/installer/setup_controller.py", line 84, in runAllSequences
sequence.run(self.CONF)
File "/usr/lib/python2.7/site-packages/packstack/installer/core/sequences.py", line 105, in run
step.run(config=config)
File "/usr/lib/python2.7/site-packages/packstack/installer/core/sequences.py", line 52, in run
raise SequenceError(str(ex))
SequenceError: Error appeared during Puppet run: _mysql.pp
Error: Could not start Service[mysqld]: Execution of '/sbin/service mariadb start' returned 1: ESC[0m
You will find full trace in log /var/tmp/packstack/20140204-122810-RehBuC/manifests/_mysql.pp.log
The the manifest log shows that some stages failed due to'Skipping because of failed dependencies'.
Is there a known workaround?
thanks,
Yogev
10 years, 10 months
Re: [Rdo-list] RDO test day Feb. 4-5 - milestone II.
by Lars Kellogg-Stedman
On Mon, Feb 03, 2014 at 12:55:58PM -0500, Tzach Shefi wrote:
> Installing on Fedora 20, semi dist' got below error.
> Packstack with answer file started working ok than:
> [...]
> Cannot retrieve metalink for repository: fedora/20/x86_64. Please
> verify its path and try again
(I'm moving this to rdo-list.)
This seems like an error contacting a Fedora mirror. There are
occasional hiccups in the mirror network...maybe just try it again and
see if it works?
If you encounter the error a second time, are you able to install
packages manually using "yum install"?
--
Lars Kellogg-Stedman <lars(a)redhat.com> | larsks @ irc
Cloud Engineering / OpenStack | " " @ twitter
10 years, 10 months
Re: [Rdo-list] python-backports is arch-specific?
by Kashyap Chamarthy
[Adding the list. /me inadvertantly dropped it, sorry.]
On Tue, Feb 04, 2014 at 01:54:10AM +0530, Kashyap Chamarthy wrote:
> CC'ing Ian Weller, from Fedora packagedb, he appears to be the owner of
> it:
>
> $ pkgdb-cli acl python-backports
> Fedora Package Database -- python-backports
> Namespace for backported Python features
> 0 bugs open (new, assigned, needinfo)
> devel Owner: ianweller
> [. . .]
>
> --
> /kashyap
>
> On Mon, Feb 03, 2014 at 01:39:26PM -0600, Matt Riedemann wrote:
> > Hey, I'm mainly asking for RHEL 6.5 but also using Fedora 19 and
> > when updating to the latest python-backports-ssl_match_hostname it
> > requires python-backports to avoid a file conflict.
> >
> > However, I noticed that while python-backports-ssl_match_hostname is
> > noarch, python-backports is arch-specific. Looking at the source
> > for backports, it's not really clear to me why that is - can someone
> > explain if it's intentional or a packaging oversight?
> >
> > --
> >
> > Thanks,
> >
> > Matt Riedemann
> >
> > _______________________________________________
> > Rdo-list mailing list
> > Rdo-list(a)redhat.com
> > https://www.redhat.com/mailman/listinfo/rdo-list
10 years, 10 months
[Rdo-list] python-backports is arch-specific?
by Matt Riedemann
Hey, I'm mainly asking for RHEL 6.5 but also using Fedora 19 and when
updating to the latest python-backports-ssl_match_hostname it requires
python-backports to avoid a file conflict.
However, I noticed that while python-backports-ssl_match_hostname is
noarch, python-backports is arch-specific. Looking at the source for
backports, it's not really clear to me why that is - can someone explain
if it's intentional or a packaging oversight?
--
Thanks,
Matt Riedemann
10 years, 10 months
[Rdo-list] lack of iptables rules for neutron glance cinder
by Shake Chen
Hi
Now I try to deplay Havana OVS+GRE in centos6.5. let neutron, glance and
cinder in single server.
# rpm -qa | grep openstack-packstack
openstack-packstack-2013.2.1-0.29.dev956.el6.noarch
Horizon in control node. 172.18.1.12 is control node IP
After finish install , I can not login the Dashboard.
1: login to Neutron node, add iptables rule, let control node can access
Neutron
-A INPUT -s 172.18.1.12/32 -p tcp -m multiport --dports 9696,67,68 -m
comment --comment "001 neutron incoming 172.18.1.12" -j
ACCEPT
restart httpd and ok ,successful login.
2： after login Dashboard, I found the glance and cinder have same problem.
so I have do the same job, ssh to glance node and cinder node , add the
iptables rules , restart iptables, the working.
--
Shake Chen
10 years, 10 months
