Tendrl/commons

Issues

• Failed to import an IPv6 cluster

  #1090 opened 5 years ago by telnoratti
  0

• Incorrect number of hosts down reported

  #1076 opened 6 years ago by GowthamShanmugam
  2

• Un-manage should not fail when any one or few storage nodes are down

  #1078 opened 6 years ago by GowthamShanmugam
  1

• Import flow failure related log messages should be more specific about what went wrong

  #1080 opened 6 years ago by GowthamShanmugam
  1

• Import Cluster fails on "node X doesn't have network details populated" with Ansible 2.8

  #1084 opened 6 years ago by GowthamShanmugam
  11

• Upstream test cases are failing

  #1089 opened 6 years ago by GowthamShanmugam
  1

• Brick path replace symbol in collectd configuration file

  #1070 opened 6 years ago by GowthamShanmugam
  2

• In upstream code import is failing when no volumes present in the cluster

  #1074 opened 6 years ago by GowthamShanmugam
  1

• Updating "tendrl/integration/monitoring" from monitoring-integration sync

  #1082 opened 6 years ago by GowthamShanmugam
  0

• Profiling job should be moved to beginning of the import flow.

  #1065 opened 6 years ago by anmolsachan
  0

• Removing provisioner tag from collectd plugin configuration

  #1066 opened 6 years ago by GowthamShanmugam
  1

• Change the md5 algo to sha512

  #1058 opened 6 years ago by shtripat
  1

• tendrl-commons package should depend on specific minimal version of ansible

  #1054 opened 6 years ago by dahorak
  2

• Don't install tendrl-gluster-integration during import flow

  #1073 opened 6 years ago by mbukatov
  0

• Update cluster details when all nodes are goes down

  #988 opened 6 years ago by GowthamShanmugam
  1

• Job sync thread will fail after /queue directory becomes empty

  #993 opened 6 years ago by GowthamShanmugam
  3

• Node up alert requires integration_id from tendrl_context

  #995 opened 6 years ago by GowthamShanmugam
  1

• Repeated Import (and Unmanage) fails: Timing out import job, Cluster data still not fully updated

  #1052 opened 6 years ago by GowthamShanmugam
  1

• Carbon logs needs to be tuned - Carbon fills up /var/log/carbon/ in large setup's

  #1057 opened 6 years ago by anmolsachan
  1

• Fix pep8 errors

  #1069 opened 6 years ago by anmolsachan
  0

• tendrl-commons doesn't specify minimal ansible version it requires

  #1067 opened 6 years ago by GowthamShanmugam
  1

• Profiling should be a separate job after the import flow completes.

  #1062 opened 6 years ago by anmolsachan
  3

• Cluster is marked as managed after import cluster job fails

  #1000 opened 6 years ago by GowthamShanmugam
  1

• Node down alert are raised when some nodes are not managed by tendrl

  #1002 opened 6 years ago by GowthamShanmugam
  1

• Job fails for a while and then marked as finished successfully

  #1015 opened 6 years ago by GowthamShanmugam
  1

• Import cluster fail without any proper log message when invalid repo is given

  #1029 opened 6 years ago by GowthamShanmugam
  1

• import flow fails for large cluster

  #1032 opened 6 years ago by GowthamShanmugam
  1

• job should not process failed jobs from etcd /queue directory

  #1034 opened 6 years ago by GowthamShanmugam
  1

• Monitoring-integration need integration_id in geo-replication_session object to push count in graphite

  #1041 opened 6 years ago by GowthamShanmugam
  1

• Set the cluster status as expand_pending if expansion failed

  #1039 opened 6 years ago by shtripat
  1

• Alert Service: glustershd is disconnected in cluster is not cleared

  #1048 opened 6 years ago by GowthamShanmugam
  1

• Tendrl Dashboard showing wrong info and alert details.

  #979 opened 6 years ago by anmolsachan
  0

• Tendrl services reports too long error lines in system log

  #986 opened 6 years ago by anmolsachan
  0

• Format of data returned by AnsibleRunner.run() method is not consistent

  #997 opened 6 years ago by anmolsachan
  0

• Requirement of improvement in logging failures in Import and Unmanage cluster tasks

  #1009 opened 6 years ago by anmolsachan
  0

• Child Jobs in Import and Unmanage not marked failed after parent job timeout.

  #1019 opened 6 years ago by anmolsachan
  0

• Unit Test take long time to finish - Should be optimized

  #1027 opened 7 years ago by anmolsachan
  0

• Test prompts for root permission during run

  #1028 opened 7 years ago by anmolsachan
  0

• Unmanage and import cluster flow fails

  #983 opened 7 years ago by GowthamShanmugam
  1

• missing space in error message "Setting up cluster aliasnot yet complete."

  #990 opened 7 years ago by dahorak
  0

• unmanaged task always fails after import failure

  #977 opened 7 years ago by GowthamShanmugam
  1

• Allow import for a cluster with same name again if failed earlier

  #973 opened 7 years ago by shtripat
  1

• Import not working. Job remains in "new" state

  #967 opened 7 years ago by anmolsachan
  2

• Add default job status key

  #959 opened 7 years ago by r0h4n
  0

• unmanage fails without descriptive error message

  #963 opened 7 years ago by GowthamShanmugam
  0

• During unmanage flow sometimes stop_monitoring_service atom timeout

  #965 opened 7 years ago by GowthamShanmugam
  0

• Import cluster job fails for a while but then finishes successfully

  #953 opened 7 years ago by GowthamShanmugam
  1

• After new cluster detected if we restart node-agent then Import cluster fails with TypeError

  #955 opened 7 years ago by GowthamShanmugam
  1

• Load_all function sometimes behave wrong

  #960 opened 7 years ago by GowthamShanmugam
  1

• Sometimes import cluster fails with another job in progress

  #951 opened 7 years ago by GowthamShanmugam
  1