Ask Your Question

Diogo Vieira's profile - activity

2018-10-10 10:16:31 -0600 received badge  Notable Question (source)
2014-07-15 02:24:57 -0600 received badge  Famous Question (source)
2014-07-14 00:03:16 -0600 received badge  Famous Question (source)
2014-07-14 00:03:16 -0600 received badge  Notable Question (source)
2014-07-14 00:03:16 -0600 received badge  Popular Question (source)
2014-06-12 15:59:07 -0600 received badge  Notable Question (source)
2014-05-15 12:39:26 -0600 received badge  Popular Question (source)
2014-05-07 23:04:56 -0600 received badge  Student (source)
2014-05-07 04:34:23 -0600 received badge  Popular Question (source)
2014-05-05 06:38:24 -0600 asked a question Packstack aborting installation because the ring refuses to rebalance

I have a 4 node cluster (1 Proxy Node and 3 Storage Nodes) set up by packstack. I now want to add a 4th Storage Node but every time I try to re-run packstack with the new answer file (added the storage node) it fails and aborts the installation with the following error:

ERROR : Error appeared during Puppet run: 10.10.6.27_ring_swift.pp
Error: /Stage[main]/Swift::Ringbuilder/Swift::Ringbuilder::Rebalance[object]/Exec[rebalance_object]: Failed to call refresh: swift-ring-builder /etc/swift/object.builder rebalance returned 1 instead of one of [0]

Because the ring refuses to rebalance (from the log file):

Notice: /Stage[main]/Swift::Ringbuilder/Swift::Ringbuilder::Rebalance[account]/Exec[rebalance_account]/returns: Cowardly refusing to save rebalance as it did not change at least 1%.

The truth is that this is not really an error and I believe packstack shouldn't stop the installation because of this. How should I proceed to install this correctly? What should be the correct way to handle this? Is there any way for me to say to packstack to ignore this error?

2014-04-23 11:58:13 -0600 asked a question Adding a storage node device to Swift generates errors

After installing a 4 node Swift cluster (10.10.6.27 as a proxy node and 10.10.6.28,10.10.6.29and 10.10.6.30 as Storage Nodes) with Packstack I followed http://docs.openstack.org/trunk/install-guide/install/yum/content/installing-and-configuring-storage-nodes.html (this guide) to add another storage device (on a new node - 10.10.6.34). Unfortunately, I keep getting these multiple errors when I run tail -f /var/log/messages (BTW is this really the best way to debug problems on a node?):

Apr 23 16:18:13 host-10-10-6-28 rsyncd[3291]: name lookup failed for 10.10.6.29: Name or service not known
Apr 23 16:18:13 host-10-10-6-28 rsyncd[3291]: connect from UNKNOWN (10.10.6.29)
Apr 23 16:18:14 host-10-10-6-28 rsyncd[3291]: rsync to object/device1/objects/136720 from UNKNOWN (10.10.6.29)
Apr 23 16:18:14 host-10-10-6-28 rsyncd[3291]: receiving file list
Apr 23 16:18:14 host-10-10-6-28 rsyncd[3291]: rsync: recv_generator: mkdir "/device1/objects/136720/84b/85843027182d33309feccf85b13eb84b" (in object) failed: Permission denied (13)
Apr 23 16:18:14 host-10-10-6-28 rsyncd[3291]: *** Skipping any contents from this failed directory ***
Apr 23 16:18:14 host-10-10-6-28 rsyncd[3291]: sent 234 bytes  received 234 bytes  total size 16
Apr 23 16:18:14 host-10-10-6-28 xinetd[493]: EXIT: rsync status=0 pid=3291 duration=1(sec)
Apr 23 16:18:17 host-10-10-6-28 journal: container-replicator Beginning replication run
Apr 23 16:18:17 host-10-10-6-28 journal: container-replicator ERROR reading HTTP response from {'replication_port': 6001, 'zone': 4, 'weight': 2.0, 'ip': '10.10.6.34', 'region': 1, 'port': 6001, 'replication_ip': '10.10.6.34', 'meta': u'', 'device': 'device4', 'id': 3}: Connection refused
Apr 23 16:18:17 host-10-10-6-28 journal: container-replicator Replication run OVER
Apr 23 16:18:17 host-10-10-6-28 journal: container-replicator Attempted to replicate 1 dbs in 0.01321 seconds (75.70615/s)
Apr 23 16:18:17 host-10-10-6-28 journal: container-replicator Removed 0 dbs
Apr 23 16:18:17 host-10-10-6-28 journal: container-replicator 2 successes, 1 failures
Apr 23 16:18:17 host-10-10-6-28 journal: container-replicator no_change:2 ts_repl:0 diff:0 rsync:0 diff_capped:0 hashmatch:0 empty:0
Apr 23 16:18:22 host-10-10-6-28 journal: account-replicator Beginning replication run
Apr 23 16:18:22 host-10-10-6-28 journal: account-replicator ERROR reading HTTP response from {'replication_port': 6002, 'zone': 4, 'weight': 2.0, 'ip': '10.10.6.34', 'region': 1, 'port': 6002, 'replication_ip': '10.10.6.34', 'meta': u'', 'device': 'device4', 'id': 3}: Connection refused
Apr 23 16:18:22 host-10-10-6-28 journal: account-replicator Replication run OVER
Apr 23 16:18:22 host-10-10-6-28 journal: account-replicator Attempted to replicate 1 dbs in 0.01319 seconds (75.80878/s)
Apr 23 16:18:22 host-10-10-6-28 journal: account-replicator Removed 0 dbs
Apr 23 16:18:22 host-10-10-6-28 journal: account-replicator 2 successes, 1 failures
Apr 23 16:18:22 host-10-10-6-28 journal: account-replicator no_change:2 ts_repl:0 diff:0 rsync:0 diff_capped:0 hashmatch:0 empty:0
Apr 23 16:18:27 host-10-10-6-28 dhclient[439]: DHCPREQUEST on eth0 to 10.10 ...
(more)
2014-04-23 10:18:14 -0600 received badge  Enthusiast
2014-04-02 10:52:39 -0600 commented answer Why doesn't my instance recognise more space in the disk after a cinder expansion?

I added the cinder.conf (as you can see it's pretty simple and I believe it's everything default; most of it is commented and maybe I could have left it out). Do you think other files are relevant?

2014-04-02 10:21:45 -0600 commented answer Why doesn't my instance recognise more space in the disk after a cinder expansion?

Unfortunately that was not the problem. I made an instance shutoff, detached the volume, expanded it and tried to reattach to a new instance (because I didn't know I could not attach a volume to an instance in shutoff state). The new instance didn't recognise the 10GB but instead still reports the old size of 2GB. BTW all the cinder logs appear to be empty.

2014-04-02 00:36:58 -0600 received badge  Famous Question (source)
2014-04-01 09:25:59 -0600 received badge  Scholar (source)
2014-04-01 09:25:57 -0600 commented answer Why doesn't my instance recognise more space in the disk after a cinder expansion?

Ok, thank you for your help. I'll have to resize some other volumes so I'll follow the resize procedure to see if that was the problem. Accepting your answer since it was most probably not having the disk detached that was the problem.

2014-04-01 09:17:48 -0600 commented answer Why doesn't my instance recognise more space in the disk after a cinder expansion?

Unfortunately it didn't help.

2014-04-01 09:15:49 -0600 received badge  Supporter (source)
2014-04-01 09:06:43 -0600 commented answer Why doesn't my instance recognise more space in the disk after a cinder expansion?

Oh ok, so that might be it. What should I do now? Use my snapshot volume instead of the first one?

2014-04-01 08:42:49 -0600 commented answer Why doesn't my instance recognise more space in the disk after a cinder expansion?

I believe I didn't detach the disk, no. I meant I just had the instance shutdown. Shouldn't this be sufficient?

2014-04-01 05:04:23 -0600 received badge  Notable Question (source)
2014-04-01 03:55:34 -0600 commented question Why doesn't my instance recognise more space in the disk after a cinder expansion?

No because fdisk tells me that the disk is 2GB. The problem is not the partition that was not resized but rather the instance doesn't recognises the expanded disk.

2014-04-01 03:53:22 -0600 commented answer Why doesn't my instance recognise more space in the disk after a cinder expansion?

I'm not sure if the instance was running or not but I think it wasn't. The disk has already been attached and detached several times because I tried to run it on several instances and every one recognises it as a 2GB disk. And I also rebooted the instance too. Do you have any idea of the tools I might use to recognise the larger disk?

2014-04-01 03:41:55 -0600 received badge  Popular Question (source)
2014-03-31 13:16:35 -0600 received badge  Editor (source)
2014-03-31 13:16:03 -0600 asked a question Why doesn't my instance recognise more space in the disk after a cinder expansion?

I had an instance with a 2GB cinder volume that I expanded to 10GB but it still reports the volume as having 2GB. Interestingly, making a snapshot of the instance and booting from the new volume it reports the disk as having 10GB. Can someone help me?

Updated with the cinder config:

####################
# cinder.conf sample #
####################

[DEFAULT]

#
# Options defined in cinder.exception
#

# make exception message format errors fatal (boolean value)
#fatal_exception_format_errors=false


#
# Options defined in cinder.policy
#

# JSON file representing policy (string value)
#policy_file=policy.json

# Rule checked when requested rule is not found (string value)
#policy_default_rule=default


#
# Options defined in cinder.quota
#

# number of volumes allowed per project (integer value)
#quota_volumes=10

# number of volume snapshots allowed per project (integer
# value)
#quota_snapshots=10

# number of volume gigabytes (snapshots are also included)
# allowed per project (integer value)
#quota_gigabytes=1000

# number of seconds until a reservation expires (integer
# value)
#reservation_expire=86400

# count of reservations until usage is refreshed (integer
# value)
#until_refresh=0

# number of seconds between subsequent usage refreshes
# (integer value)
#max_age=0

# default driver to use for quota checks (string value)
#quota_driver=cinder.quota.DbQuotaDriver

# whether to use default quota class for default quota
# (boolean value)
#use_default_quota_class=true


#
# Options defined in cinder.service
#

# seconds between nodes reporting state to datastore (integer
# value)
#report_interval=10

# seconds between running periodic tasks (integer value)
#periodic_interval=60

# range of seconds to randomly delay when starting the
# periodic task scheduler to reduce stampeding. (Disable by
# setting to 0) (integer value)
#periodic_fuzzy_delay=60

# IP address for OpenStack Volume API to listen (string value)
#osapi_volume_listen=0.0.0.0
osapi_volume_listen=0.0.0.0

# port for os volume api to listen (integer value)
#osapi_volume_listen_port=8776


#
# Options defined in cinder.test
#

# File name of clean sqlite db (string value)
#sqlite_clean_db=clean.sqlite

# should we use everything for testing (boolean value)
#fake_tests=true


#
# Options defined in cinder.wsgi
#

# Number of backlog requests to configure the socket with
# (integer value)
#backlog=4096

# Sets the value of TCP_KEEPIDLE in seconds for each server
# socket. Not supported on OS X. (integer value)
#tcp_keepidle=600

# CA certificate file to use to verify connecting clients
# (string value)
#ssl_ca_file=<None>

# Certificate file to use when starting the server securely
# (string value)
#ssl_cert_file=<None>

# Private key file to use when starting the server securely
# (string value)
#ssl_key_file=<None>


#
# Options defined in cinder.api.common
#

# the maximum number of items returned in a single response
# from a collection resource (integer value)
#osapi_max_limit=1000

# Base URL that will be presented to users in links to the
# OpenStack Volume API (string value)
#osapi_volume_base_URL=<None>


#
# Options defined in cinder.api.middleware.auth
#

# Treat X-Forwarded-For as the canonical remote address. Only
# enable this if you have a sanitizing proxy. (boolean value)
#use_forwarded_for=false


#
# Options defined in cinder.api.middleware.sizelimit
#

# Max size for body of a request (integer value)
#osapi_max_request_body_size=114688


#
# Options defined in cinder.backup.drivers.ceph
#

# Ceph config file to use. (string value)
#backup_ceph_conf=/etc/ceph/ceph.conf

# the Ceph user to connect with (string value)
#backup_ceph_user=cinder

# the chunk ...
(more)
2014-03-31 13:15:37 -0600 asked a question Why doesn't my instance doesn't recognise more space on disk?

I had an instance with a 2GB cinder volume that I expanded to 10GB but it still reports the volume as having 2GB. Interestingly, making a snapshot of the instance and booting from the new volume it reports the disk as having 10GB. Can someone help me?