[
https://issues.apache.org/jira/browse/AMBARI-25888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17698931#comment-17698931
]
Zhiguo Wu edited comment on AMBARI-25888 at 3/10/23 12:58 PM:
--------------------------------------------------------------
[~vivekraghuwanshi]
Ambari Server version should be 3.0.0.0-SNAPSHOT if you build from trunk
branch, we haven't updated it yet.
You can use this url for the repo which is already set as default:
[https://bigtop-snapshot.s3.amazonaws.com/centos-7/$basearch]
RPM packages under bigtop repo are a little different from s3, bigtop packages
follow {*}Linux Filesystem Hierarchy Standard{*}:
[https://refspecs.linuxfoundation.org/FHS_3.0/fhs/index.html|https://refspecs.linuxfoundation.org/FHS_3.0/fhs/index.html),]
But we add some functions to be compatible with Ambari, so you need to use RPMs
provided by Ambari Community
was (Author: JIRAUSER294567):
[~vivekraghuwanshi]
Ambari Server version should be 3.0.0.0-SNAPSHOT if you build from trunk
branch, we haven't updated it yet.
You can use this url for the repo which is already set as default:
[https://bigtop-snapshot.s3.amazonaws.com/centos-7/$basearch]
RPM packages under bigtop repo are a little different from s3, bigtop packages
follow *Linux Filesystem Hierarchy* Standard:
[https://refspecs.linuxfoundation.org/FHS_3.0/fhs/index.html|https://refspecs.linuxfoundation.org/FHS_3.0/fhs/index.html),]
But we add some functions to be compatible with Ambari, so you need to use RPMs
provided by Ambari Community
> component did not advertise a version. This may indicate a problem with the
> component packaging. However, the stack-select tool was able to report a
> single version installed (3.2.0). This is the version that will be report
> ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: AMBARI-25888
> URL: https://issues.apache.org/jira/browse/AMBARI-25888
> Project: Ambari
> Issue Type: Bug
> Environment: Centos 7.9
> Python 2.7
> Reporter: ViVek Raghuwanshi
> Priority: Major
>
> stderr:
> 2023-03-09 16:31:58,811 - The 'hadoop-hdfs-namenode' component did not
> advertise a version. This may indicate a problem with the component
> packaging. However, the stack-select tool was able to report a single version
> installed (3.2.0). This is the version that will be reported.
> 2023-03-09 16:32:03,973 - The 'hadoop-hdfs-namenode' component did not
> advertise a version. This may indicate a problem with the component
> packaging. However, the stack-select tool was able to report a single version
> installed (3.2.0). This is the version that will be reported.
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/stacks/BIGTOP/3.2.0/services/HDFS/package/scripts/namenode.py",
> line 419, in
> NameNode().execute()
> File
> "/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py",
> line 355, in execute
> method(env)
> File
> "/var/lib/ambari-agent/cache/stacks/BIGTOP/3.2.0/services/HDFS/package/scripts/namenode.py",
> line 71, in install
> self.install_packages(env)
> File
> "/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py",
> line 876, in install_packages
> name = self.format_package_name(package['name'])
> File
> "/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py",
> line 569, in format_package_name
> return self.get_package_from_available(name)
> File
> "/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py",
> line 536, in get_package_from_available
> raise Fail("No package found for \{0}(expected name: \{1})".format(name,
> name_with_version))
> resource_management.core.exceptions.Fail: No package found for
> hadoop_${stack_version}(expected name: hadoop_3_2_0)
> stdout:
> 2023-03-09 16:31:58,575 - Stack Feature Version Info: Cluster Stack=3.2.0,
> Command Stack=None, Command Version=None -> 3.2.0
> 2023-03-09 16:31:58,575 - Using hadoop conf dir: /etc/hadoop/conf
> 2023-03-09 16:31:58,577 - Group['hdfs'] {}
> 2023-03-09 16:31:58,578 - Group['hadoop'] {}
> 2023-03-09 16:31:58,578 - User['zookeeper'] \{'gid': 'hadoop',
> 'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None}
> 2023-03-09 16:31:58,579 - User['ams'] \{'gid': 'hadoop',
> 'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None}
> 2023-03-09 16:31:58,580 - User['ambari-qa'] \{'gid': 'hadoop',
> 'fetch_nonlocal_groups': True, 'groups': ['hadoop'], 'uid': None}
> 2023-03-09 16:31:58,581 - User['hdfs'] \{'gid': 'hadoop',
> 'fetch_nonlocal_groups': True, 'groups': ['hdfs', 'hadoop'], 'uid': None}
> 2023-03-09 16:31:58,581 - File['/var/lib/ambari-agent/tmp/changeUid.sh']
> \{'content': StaticFile('changeToSecureUid.sh'), 'mode': 0555}
> 2023-03-09 16:31:58,583 - Execute['/var/lib/ambari-agent/tmp/changeUid.sh
> ambari-qa
> /tmp/hadoop-ambari-qa,/tmp/hsperfdata_ambari-qa,/home/ambari-qa,/tmp/ambari-qa,/tmp/sqoop-ambari-qa
> 0'] \{'not_if': '(test $(id -u ambari-qa) -gt 1000) || (false)'}
> 2023-03-09 16:31:58,588 - Skipping
> Execute['/var/lib/ambari-agent/tmp/changeUid.sh ambari-qa
> /tmp/hadoop-ambari-qa,/tmp/hsperfdata_ambari-qa,/home/ambari-qa,/tmp/ambari-qa,/tmp/sqoop-ambari-qa
> 0'] due to not_if
> 2023-03-09 16:31:58,589 - Group['hdfs'] {}
> 2023-03-09 16:31:58,589 - User['hdfs'] \{'fetch_nonlocal_groups': True,
> 'groups': ['hdfs', 'hadoop', 'hdfs']}
> 2023-03-09 16:31:58,590 - FS Type: HDFS
> 2023-03-09 16:31:58,590 - Directory['/etc/hadoop'] \{'mode': 0755}
> 2023-03-09 16:31:58,606 - File['/etc/hadoop/conf/hadoop-env.sh'] \{'content':
> InlineTemplate(...), 'owner': 'hdfs', 'group': 'hadoop'}
> 2023-03-09 16:31:58,607 -
> Directory['/var/lib/ambari-agent/tmp/hadoop_java_io_tmpdir'] \{'owner':
> 'hdfs', 'group': 'hadoop', 'mode': 01777}
> 2023-03-09 16:31:58,619 - Repository for BIGTOP/3.2.0/BIGTOP-3.2.0 is not
> managed by Ambari
> 2023-03-09 16:31:58,619 - Repository[None] \{'action': ['create']}
> 2023-03-09 16:31:58,622 - Package['unzip'] \{'retry_on_repo_unavailability':
> False, 'retry_count': 5}
> 2023-03-09 16:31:58,713 - Skipping installation of existing package unzip
> 2023-03-09 16:31:58,714 - Package['curl'] \{'retry_on_repo_unavailability':
> False, 'retry_count': 5}
> 2023-03-09 16:31:58,723 - Skipping installation of existing package curl
> 2023-03-09 16:31:58,724 - Package['bigtop-select']
> \{'retry_on_repo_unavailability': False, 'retry_count': 5}
> 2023-03-09 16:31:58,733 - Skipping installation of existing package
> bigtop-select
> 2023-03-09 16:31:58,788 - call[('ambari-python-wrap',
> '/usr/lib/bigtop-select/distro-select', 'versions')] {}
> 2023-03-09 16:31:58,811 - call returned (0, '3.2.0')
> 2023-03-09 16:31:58,811 - The 'hadoop-hdfs-namenode' component did not
> advertise a version. This may indicate a problem with the component
> packaging. However, the stack-select tool was able to report a single version
> installed (3.2.0). This is the version that will be reported.
> 2023-03-09 16:31:58,980 - Using hadoop conf dir: /etc/hadoop/conf
> 2023-03-09 16:31:58,981 - Stack Feature Version Info: Cluster Stack=3.2.0,
> Command Stack=None, Command Version=None -> 3.2.0
> 2023-03-09 16:31:58,984 - Using hadoop conf dir: /etc/hadoop/conf
> 2023-03-09 16:31:58,991 - Command repositories: BIGTOP-3.2.0
> 2023-03-09 16:31:58,991 - Applicable repositories: BIGTOP-3.2.0
> 2023-03-09 16:31:58,991 - Looking for matching packages in the following
> repositories: BIGTOP-3.2.0
> 2023-03-09 16:32:03,950 - call[('ambari-python-wrap',
> '/usr/lib/bigtop-select/distro-select', 'versions')] {}
> 2023-03-09 16:32:03,973 - call returned (0, '3.2.0')
> 2023-03-09 16:32:03,973 - The 'hadoop-hdfs-namenode' component did not
> advertise a version. This may indicate a problem with the component
> packaging. However, the stack-select tool was able to report a single version
> installed (3.2.0). This is the version that will be reported.
> Command failed after 1 tries
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
